summaryrefslogtreecommitdiff
path: root/openstack/usr/lib/systemd/system/openstack-neutron-db-setup.service
Commit message (Collapse)AuthorAgeFilesLines
* Start db-setup services after config-setup servicesFrancisco Redondo Marchena2015-04-201-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