baserock/baserock/definitions.git - gitlab.com: baserock/definitions.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	openstack: add network-online dependency to some systemd units	Tiago Gomes	2015-05-01	1	-1/+2
\| \| \| \| \| \|	To use keystone and postgres the network needs to be online. Change-Id: Iaa0ed242b9cadca2bc8519cbc00e6cc9ea4745b4
*	openstack: add missing RemainAfterExit=yes	Tiago Gomes	2015-05-01	1	-0/+1
\| \| \| \|	Change-Id: I88e3e3e0f2b94b1ee84c706a29a439a09f370e8e
*	openstack: add missing ConditionPathExists	Tiago Gomes	2015-05-01	1	-1/+1
\| \| \| \| \| \| \| \|	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
*	openstack: remove setup units from Wants section	Tiago Gomes	2015-05-01	1	-1/+0
\| \| \| \| \| \| \| \|	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-setup	Tiago Gomes	2015-04-24	1	-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-setup	Tiago Gomes	2015-04-24	1	-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 services	Francisco Redondo Marchena	2015-04-21	1	-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 nova into control and compute	Richard Maw	2015-04-17	1	-0/+12
	This adds NOVA_ENABLE_{CONTROLLER,COMPUTE}. Both are enabled by deafult, but if CONTROLLER is enabled but COMPUTE isn't, then the conductor service is enabled. Change-Id: I523a7270d4afdcd1e2a30eaac42ea499581fe971