c740b54214
The merge-new-params-nic-config-script.py previosly had the 'Controller' role as the default for --role-name. It is not obvious that this parameter must be changed when merging nic config templates. Remove the default and make the argument required. Improves UX since user error is less likely. Making the mistake of using a Role with too many networks is'nt as forgiving since we now only pass parameters for the role.networks. Related-Bug: #1800811 Change-Id: Iff9e364db66ad09a30ac10a7814a3c01d50caf58
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://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 | scn010 | 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 | rabbit | ||
| om-notify | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | ||
| 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 |
|
||||||||||
| octavia |
|