8a7201cd05
In puppet-manila, the driver_handlers_share_servers parameter have been deprecated for some backends[1] because these backends can only accept true or false and accpepting arbitrary value results in manila service failing to start. This change deprecate the corresponding parameters in template files so that we can remove usage of these deprecated parameters. [1] 4c365c9064845e73a1da0f868ebba5a00c6a5c7a Change-Id: I7cd02aa0f107e74ec35be3d1928d7aa661885d40
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: https://opendev.org/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 | scn010 | scn013 | non-ha | ovh-ha |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| keystone |
|
|
|
|
|
|
|
|
|
|
|
|
| glance |
|
swift |
|
|
|
|
|
|
|
|
||
| cinder |
|
iscsi | ||||||||||
| heat |
|
|
||||||||||
| ironic |
|
|||||||||||
| mysql |
|
|
|
|
|
|
|
|
|
|
|
|
| neutron |
|
|
|
|
|
|
|
|
|
|
||
| neutron-bgpvpn |
|
|||||||||||
| ovn |
|
|||||||||||
| neutron-l2gw |
|
|||||||||||
| om-rpc | rabbit | rabbit |
|
rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | ||
| om-notify | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | ||
| redis |
|
|
||||||||||
| haproxy |
|
|
|
|
|
|
|
|
|
|
||
| memcached |
|
|
|
|
|
|
|
|
|
|
||
| pacemaker |
|
|
|
|
|
|
|
|
|
|
||
| nova |
|
|
|
|
ironic |
|
|
|
|
|
||
| placement |
|
|
|
|
|
|
|
|
|
|
||
| ntp |
|
|
|
|
|
|
|
|
|
|
|
|
| snmp |
|
|
|
|
|
|
|
|
|
|
|
|
| timezone |
|
|
|
|
|
|
|
|
|
|
|
|
| mistral |
|
|||||||||||
| swift |
|
|||||||||||
| aodh |
|
|
||||||||||
| ceilometer |
|
|
||||||||||
| gnocchi |
|
|
||||||||||
| barbican |
|
|||||||||||
| zaqar |
|
|||||||||||
| cephrgw |
|
|||||||||||
| cephmds |
|
|||||||||||
| manila |
|
|||||||||||
| collectd |
|
|||||||||||
| designate |
|
|||||||||||
| octavia |
|
|
||||||||||
| rear |
|
|||||||||||
| Extra Firewall |
|