summaryrefslogtreecommitdiff
path: root/openstack/usr/lib/systemd/system/openstack-neutron-db-setup.service
Commit message (Collapse)AuthorAgeFilesLines
* openstack: finishing tidy up systemd unit filesTiago Gomes2015-05-011-1/+1
| | | | | | | | | * Add db-setup to the 'Afters' for ceilometer * Improve order of units in 'Afters' * Remove deprecated syslog.target * Add missing Wants=network-online.target Change-Id: I4936126b78946dbdfe77213cc5202b39ea6a50cb
* openstack: remove setup units from Wants sectionTiago Gomes2015-05-011-1/+1
| | | | | | | | This way it is possible to avoid running the setup script in subsequent boots, either by disabling the setup service using systemctl, or removing the respective configuration file from /etc/openstack/. Change-Id: I9945e40eaebbc160bb21ca46f10a8b6121f66267
* Depend on openstack-keystone-setupTiago Gomes2015-04-241-2/+2
| | | | | | | | | | Depending on openstack-keystone is wrong, as the admin user, admin tenant, admin role, service tenant and endpoint, are only created after starting and enabling the openstack-keystone service. Not having those created will cause keystone commands executed by some Ansible scripts to fail. Change-Id: I54288f3de2814dbb6639a894d55d7395f052a428
* Move postgres-server configuration out of keystone-setupTiago Gomes2015-04-241-2/+2
| | | | | | | | | Otherwise postgres-server and keystone-setup services will initially fail, as keystone-setup needs a postgres-server running to succeed, but the postgres-server can only run after some configuration, which was previously being done by keystone-setup. Change-Id: I2d649d494cb54119e3b9bd3d9f6deb46bfb2dd12
* nova and neutron: Start db-setup services after config-setup servicesFrancisco Redondo Marchena2015-04-211-1/+1
| | | | | | | | | openstack-{nova,neutron}-db-setup.services need to run after openstack-{nova,neutron}-config-setup.services because the latter create the nova and neutron system users used in the formers. Change-Id: I4152b8dc16fe2181de83f5732b58d3f1072811e9
* OpenStack: Split neutron config up into MANAGER, CONTROLLER and AGENTRichard Maw2015-04-171-0/+13
This adds NEUTRON_ENABLE_{MANAGER,CONTROLLER,AGENT} to determine which parts should be run on a node, so a network node has MANAGER enabled, but doesn't need CONTROLLER or AGENT, since those will be run on the controller and compute nodes respectively. This works by the configuration extension selectively enabling systemd units, with config-setup always being run, and db-setup run on the controller node. Rather than having the enable logic in 3 distinct setup services, their dependencies have been augmented to run after appropriate setup services if they are enabled, and to not run if their configuration hasn't been created. Change-Id: I7625074c94acfb49fc68660440609b0fe9c0052d