9f1b58e8ac
This is a first iteration of implementing libvirt and nova compute as composable services. Note: some parameters are still in puppet/compute.yaml -- we'll move them later in a next iteration. Implements: blueprint composable-services-within-roles Depends-On: I0b765f8cb08633005c1fc5a5a2a8e5658ff44302 Change-Id: I752198cdf231ef13062ba96c3877e5defd618c3a |
||
---|---|---|
.. | ||
database | ||
pacemaker | ||
time | ||
cinder-api.yaml | ||
cinder-base.yaml | ||
cinder-scheduler.yaml | ||
cinder-volume.yaml | ||
glance-api.yaml | ||
glance-registry.yaml | ||
haproxy.yaml | ||
heat-api-cfn.yaml | ||
heat-api-cloudwatch.yaml | ||
heat-api.yaml | ||
heat-base.yaml | ||
heat-engine.yaml | ||
ironic-api.yaml | ||
ironic-base.yaml | ||
ironic-conductor.yaml | ||
keepalived.yaml | ||
keystone.yaml | ||
memcached.yaml | ||
neutron-base.yaml | ||
neutron-dhcp.yaml | ||
neutron-l3.yaml | ||
neutron-metadata.yaml | ||
neutron-ovs-agent.yaml | ||
neutron-plugin-ml2.yaml | ||
neutron-plugin-nuage.yaml | ||
neutron-plugin-opencontrail.yaml | ||
neutron-plugin-plumgrid.yaml | ||
neutron-server.yaml | ||
nova-api.yaml | ||
nova-base.yaml | ||
nova-compute.yaml | ||
nova-conductor.yaml | ||
nova-consoleauth.yaml | ||
nova-libvirt.yaml | ||
nova-scheduler.yaml | ||
nova-vncproxy.yaml | ||
rabbitmq.yaml | ||
README.rst | ||
sahara-api.yaml | ||
sahara-base.yaml | ||
sahara-engine.yaml | ||
services.yaml | ||
snmp.yaml | ||
swift-proxy.yaml | ||
swift-storage.yaml |
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)
Note: Not all roles currently support all steps:
- ObjectStorage role only supports steps 2, 3 and 4