| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
* 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
|
|
|
|
|
|
| |
To use keystone and postgres the network needs to be online.
Change-Id: Iaa0ed242b9cadca2bc8519cbc00e6cc9ea4745b4
|
|
|
|
|
|
|
|
| |
And fix some existing as well. Generate a separate postgres.conf file
so that we don't have to reference keystone on the postgres setup
systemd unit and Ansible script.
Change-Id: I0bb4428b7e88a508a37d1d43ddcd266369b05cd2
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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
|
|
Change-Id: Iae387e39c4a62ef608496d31c748493fa88ce3e1
|