3c5345fc75
While the heat templates specify a default value of 3, it rarely seems to have an effect as the tripleoclient is setting this according to the controller scale. This was fine before composable roles, but it is now invalid. While the client needs to be modified to no longer set this according to controller scale, the template should default to a sentinel value that will allow the puppet code to determine the proper value by the number of hosts that have the neutron dhcp agent deployed on them. Depends-On: I5533e42c5ba9f72cc70d80489a07e30ee2341198 Partial-bug: #1632721 Change-Id: I06628764c4769d91bbc42efe1c722702d6574d02
Team and repository tags
tripleo-heat-templates
Heat templates to deploy OpenStack using OpenStack.
- Free software: Apache license
- Documentation: http://docs.openstack.org/developer/tripleo-docs
- Source: http://git.openstack.org/cgit/openstack/tripleo-heat-templates
- Bugs: http://bugs.launchpad.net/tripleo
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
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:
| - | scenario001 | scenario002 | scenario003 | scenario004 | multinode-nonha |
|---|---|---|---|---|---|
| keystone |
|
|
|
|
|
| glance |
|
|
|
|
|
| cinder |
|
|
|
||
| heat |
|
|
|
|
|
| mysql |
|
|
|
|
|
| neutron |
|
|
|
|
|
| rabbitmq |
|
|
|
|
|
| mongodb |
|
|
|||
| redis |
|
||||
| haproxy |
|
|
|
|
|
| keepalived |
|
|
|
|
|
| memcached |
|
|
|
|
|
| pacemaker |
|
|
|
|
|
| nova |
|
|
|
|
|
| ntp |
|
|
|
|
|
| snmp |
|
|
|
|
|
| timezone |
|
|
|
|
|
| sahara |
|
||||
| mistral |
|
||||
| swift |
|
|
|||
| aodh |
|
||||
| ceilometer |
|
||||
| gnocchi |
|
||||
| panko |
|
||||
| barbican |
|
||||
| zaqar |
|
||||
| ec2api |
|
||||
| cephrgw |
|
|
|||
| tacker |
|
||||
| congress |
|
||||
| cephmds |
|
||||
| manila |
|