60d75f19e5
By settings these hiera keys we will actually do a deep comparison of all pacemaker resources and update them accordingly. This means that rerunning a deploy against an existing overcloud will actually detect if a pacemaker resource needs updating and will update the definition and restart of said resource. The code will wait for the resource to be up (aka the cluster to settle after an update). Depends-On: I62d5662327333e17e1c32a029695b3d3a904ca10 Change-Id: I0b9ed429e6b1bd4a62b4462bf6312782f29b7d6b
Team and repository tags
tripleo-heat-templates
Heat templates to deploy OpenStack using OpenStack.
- Free software: Apache License (2.0)
- Documentation: https://docs.openstack.org/tripleo-docs/latest/
- Source: http://git.openstack.org/cgit/openstack/tripleo-heat-templates
- Bugs: https://bugs.launchpad.net/tripleo
* Release notes: https://docs.openstack.org/releasenotes/tripleo-heat-templates/ Features --------
The ability to deploy a multi-node, role based OpenStack deployment using OpenStack Heat. Notable features include:
- Choice of deployment/configuration tooling: puppet, (soon) docker
- Role based deployment: roles for the controller, compute, ceph, swift, and cinder storage
- physical network configuration: support for isolated networks, bonding, and standard ctlplane networking
Directories
A description of the directory layout in TripleO Heat Templates.
- environments: contains heat environment files that can be used with -e
on the command like to enable features, etc.
- extraconfig: templates used to enable 'extra' functionality. Includes
functionality for distro specific registration and upgrades.
- firstboot: example first_boot scripts that can be used when initially
creating instances.
- network: heat templates to help create isolated networks and ports
- puppet: templates mostly driven by configuration with puppet. To use these
templates you can use the overcloud-resource-registry-puppet.yaml.
- validation-scripts: validation scripts useful to all deployment
configurations
- roles: example roles that can be used with the tripleoclient to generate
a roles_data.yaml for a deployment See the roles/README.rst for additional details.
Service testing matrix
The configuration for the CI scenarios will be defined in tripleo-heat-templates/ci/ and should be executed according to the following table:
| - | scn000 | scn001 | scn002 | scn003 | scn004 | scn006 | scn007 | scn009 | non-ha | ovh-ha |
|---|---|---|---|---|---|---|---|---|---|---|
| openshift |
|
|||||||||
| keystone |
|
|
|
|
|
|
|
|
|
|
| glance |
|
swift |
|
|
|
|
|
|
||
| cinder |
|
iscsi | ||||||||
| heat |
|
|
||||||||
| ironic |
|
|||||||||
| mysql |
|
|
|
|
|
|
|
|
|
|
| neutron |
|
|
|
|
|
|
|
|
||
| neutron-bgpvpn |
|
|||||||||
| ovn |
|
|||||||||
| neutron-l2gw |
|
|||||||||
| om-rpc | rabbit | rabbit |
|
rabbit | rabbit | rabbit | rabbit | rabbit | ||
| om-notify | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | ||
| mongodb | ||||||||||
| redis |
|
|
||||||||
| haproxy |
|
|
|
|
|
|
|
|
||
| memcached |
|
|
|
|
|
|
|
|
||
| pacemaker |
|
|
|
|
|
|
|
|
||
| nova |
|
|
|
|
ironic |
|
|
|
||
| ntp |
|
|
|
|
|
|
|
|
|
|
| snmp |
|
|
|
|
|
|
|
|
|
|
| timezone |
|
|
|
|
|
|
|
|
|
|
| sahara |
|
|||||||||
| mistral |
|
|||||||||
| swift |
|
|||||||||
| aodh |
|
|
||||||||
| ceilometer |
|
|
||||||||
| gnocchi |
|
|
||||||||
| panko |
|
|
||||||||
| barbican |
|
|||||||||
| zaqar |
|
|||||||||
| ec2api |
|
|||||||||
| cephrgw |
|
|||||||||
| tacker |
|
|||||||||
| congress |
|
|||||||||
| cephmds |
|
|||||||||
| manila |
|
|||||||||
| collectd |
|
|||||||||
| fluentd |
|
|||||||||
| sensu-client |
|
|||||||||
| designate |
|