Move ordering constraints from httpd to openstack-core
With the move of keystone under wsgi and httpd, all openstack services received an
ordering constraint on the 'httpd' service (which now exposes keystone and horizon).
Since this is not only a layering violation, but it also removes the ability to
restart keystone (httpd) without having to restart all dependent services, we introduce
a dummy 'openstack-core' service which all other services depend on and we make also
keystone (httpd) depend on it.
Reviewed: https:/ /review. openstack. org/286446 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=c5049d8ffbf 9579a6e726c0031 411ddb57e1a625
Committed: https:/
Submitter: Jenkins
Branch: master
commit c5049d8ffbf9579 a6e726c0031411d db57e1a625
Author: Michele Baldessari <email address hidden>
Date: Fri Feb 26 07:41:42 2016 +0000
Move ordering constraints from httpd to openstack-core
With the move of keystone under wsgi and httpd, all openstack services received an
ordering constraint on the 'httpd' service (which now exposes keystone and horizon).
Since this is not only a layering violation, but it also removes the ability to
restart keystone (httpd) without having to restart all dependent services, we introduce
a dummy 'openstack-core' service which all other services depend on and we make also
keystone (httpd) depend on it.
The previous constraint ordering graph can be found here: acksyn. org/files/ tripleo/ wsgi-2016- 02-24-cib. pdf
http://
Whereas after this change we have the following ordering graph: acksyn. org/files/ tripleo/ wsgi-openstack- core.pdf
http://
Once this is agreed upon, we can start working on fixing the upgrade path
from Liberty.
This fixes RHBZ#1290121
Closes bug: 1537885
Change-Id: Ie26908ac9bfc0b 84b6b65ae3bda71 1236b03d9d4