
Since https://review.openstack.org/#/c/514707/ added the net_ip_map to hieradata, we can look up the per-network bind IPs via hiera interpolation instead of heat map_replace. In some cases the ServiceNetMap lookup is used for other things, but anywhere we make use of the "magic" translation via NetIpMap is changed the same way. This will enable more of the configuration data to be exposed per role vs per node in a future patch (to simplify our ansible workflow). Co-authored-by: Bogdan Dobrelya <bdobreli@redhat.com> Change-Id: Ie3da9fedbfce87e85f74d8780e7ad1ceadda79c8
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
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:
- | 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 |
|
||||||||
rabbitmq |
|
|
|
|
|
|
|
|
|
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 |
|