Blueprint: [see URL]
Break down monolithic controller heat template into discrete set of templates which can be deployed and managed independently.
How to test a composable service:
The first item that needs to checked it's to verify that the actual service it's enabled by default in the resource registry. For example, by verifying in the following file “overcloud-resource-registry-puppet.yaml” that OS::TripleO::Services::Horizon: it's not pointing to OS::Heat::None.
Case pointing to OS::Heat::None.
In this case the service should be enabled by using an environment file inside the 'environments' folder.
Case pointing to a valid heat template.
For example “puppet/services/horizon.yaml”, in which case this composable service will be deployed by default.
Note: It's important to check that this resource registry it's not overridden when deploying HA environments, in which case the heat template might be overridden in this environment file “environments/puppet-pacemaker.yaml”
*** Bug 1302865 has been marked as a duplicate of this bug. ***
*** Bug 1275143 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
*** Bug 1292328 has been marked as a duplicate of this bug. ***
*** Bug 1292330 has been marked as a duplicate of this bug. ***