5a9ea978a6
For handling the X-Forwarded-Proto, heat uses the http_proxy_to_wsgi middleware from oslo.middleware. It used to work by default, but now configuration is required to enable that. We require it since we are effectively behind a proxy (HAProxy). Change-Id: I256f27ec6a3f66316ff6aa3f78b2f1ec1472f097 |
||
---|---|---|
.. | ||
pacemaker | ||
README.rst | ||
glance-api.yaml | ||
glance-registry.yaml | ||
heat-api-cfn.yaml | ||
heat-api-cloudwatch.yaml | ||
heat-api.yaml | ||
heat-base.yaml | ||
heat-engine.yaml | ||
keystone.yaml | ||
loadbalancer.yaml | ||
memcached.yaml | ||
neutron-base.yaml | ||
neutron-dhcp.yaml | ||
neutron-l3.yaml | ||
neutron-metadata.yaml | ||
rabbitmq.yaml | ||
services.yaml |
README.rst
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.
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:
- Load Balancer configuration
- Core Services (Database/Rabbit/NTP/etc.)
- Early Openstack Service setup (Ringbuilder, etc.)
- General OpenStack Services
- Service activation (Pacemaker)
- Fencing (Pacemaker)