| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
To use keystone and postgres the network needs to be online.
Change-Id: Iaa0ed242b9cadca2bc8519cbc00e6cc9ea4745b4
|
| |
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
| |
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
|
|
|
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
|
