b99733d08a
Allows the installation and configuration of Manila. Supports the generic driver only. This has a dependency on the puppet-tripleo classes for manila where the puppet specific config now lives. The review at https://review.openstack.org/#/c/315658/ has been merge into this one, as of v68, so manila lands as a composable service. This was brought up on the mailing list at [1] [1] http://lists.openstack.org/pipermail/openstack-dev/2016-May/096126.html Co-Authored-By: Marios Andreou <marios@redhat.com> Implements: blueprint composable-services-within-roles Depends-On: I444916d60a67bf730bf4089323dba1c1429e2e71 Depends-On: I9eda4b3364e5c59342761a1ec71b0eb567c69cf1 Depends-On: I571b65a5402c1028418476a573ebeb9450ed00c9 Change-Id: I7acebac4354fca1f8d7ff6c343c1346bf29b81c6 |
||
|---|---|---|
| .. | ||
| database | ||
| pacemaker | ||
| time | ||
| README.rst | ||
| ceilometer-agent-central.yaml | ||
| ceilometer-agent-compute.yaml | ||
| ceilometer-agent-notification.yaml | ||
| ceilometer-api.yaml | ||
| ceilometer-base.yaml | ||
| ceilometer-collector.yaml | ||
| ceilometer-expirer.yaml | ||
| ceph-base.yaml | ||
| ceph-client.yaml | ||
| ceph-external.yaml | ||
| ceph-mon.yaml | ||
| ceph-osd.yaml | ||
| cinder-api.yaml | ||
| cinder-base.yaml | ||
| cinder-scheduler.yaml | ||
| cinder-volume.yaml | ||
| glance-api.yaml | ||
| glance-registry.yaml | ||
| gnocchi-api.yaml | ||
| gnocchi-base.yaml | ||
| gnocchi-metricd.yaml | ||
| gnocchi-statsd.yaml | ||
| haproxy.yaml | ||
| heat-api-cfn.yaml | ||
| heat-api-cloudwatch.yaml | ||
| heat-api.yaml | ||
| heat-base.yaml | ||
| heat-engine.yaml | ||
| horizon.yaml | ||
| ironic-api.yaml | ||
| ironic-base.yaml | ||
| ironic-conductor.yaml | ||
| keepalived.yaml | ||
| kernel.yaml | ||
| keystone.yaml | ||
| manila-api.yaml | ||
| manila-base.yaml | ||
| manila-scheduler.yaml | ||
| manila-share.yaml | ||
| memcached.yaml | ||
| neutron-base.yaml | ||
| neutron-compute-plugin-midonet.yaml | ||
| neutron-compute-plugin-nuage.yaml | ||
| neutron-compute-plugin-opencontrail.yaml | ||
| neutron-compute-plugin-plumgrid.yaml | ||
| neutron-dhcp.yaml | ||
| neutron-l3.yaml | ||
| neutron-metadata.yaml | ||
| neutron-midonet.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 | ||
| pacemaker.yaml | ||
| rabbitmq.yaml | ||
| sahara-api.yaml | ||
| sahara-base.yaml | ||
| sahara-engine.yaml | ||
| services.yaml | ||
| snmp.yaml | ||
| swift-proxy.yaml | ||
| swift-ringbuilder.yaml | ||
| swift-storage.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)
Note: Not all roles currently support all steps:
- ObjectStorage role only supports steps 2, 3 and 4