5 A TripleO nested stack Heat template that encapsulates generic configuration
6 data to configure a specific service. This generally includes everything
7 needed to configure the service excluding the local bind ports which
8 are still managed in the per-node role templates directly (controller.yaml,
9 compute.yaml, etc.). All other (global) service settings go into
10 the puppet/service templates.
15 Each service may define its own input parameters and defaults.
16 Operators will use the parameter_defaults section of any Heat
17 environment to set per service parameters.
22 Each service may define a config_settings output variable which returns
23 Hiera settings to be configured.
28 Each service may define an output variable which returns a puppet manifest
29 snippet that will run at each of the following steps. Earlier manifests
30 are re-asserted when applying latter ones.
32 * config_settings: Custom hiera settings for this service.
34 * step_config: A puppet manifest that is used to step through the deployment
35 sequence. Each sequence is given a "step" (via hiera('step') that provides
36 information for when puppet classes should activate themselves.
38 Steps correlate to the following:
40 1) Load Balancer configuration
42 2) Core Services (Database/Rabbit/NTP/etc.)
44 3) Early Openstack Service setup (Ringbuilder, etc.)
46 4) General OpenStack Services
48 5) Service activation (Pacemaker)
50 6) Fencing (Pacemaker)
52 Note: Not all roles currently support all steps:
54 * ObjectStorage role only supports steps 2, 3 and 4