tripleo-heat-templates/puppet/services/README.rst
Giulio Fidente 7aeb416528 Add global_config_settings to services' output
The new global_config_settings output is meant to contain
additional hieradata distributed by the services to all role types.

Change-Id: I1beff8f7b12a4178e6081de6134cd8e67794d710
2016-08-26 11:11:47 +02:00

57 lines
1.7 KiB
ReStructuredText

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