
With this change we make sure that the 'RABBITMQ_NODENAME' is the fqdn and that we use it when connecting to the node itself via rabbitmqctl. We also make sure we set the CA to the one defined in the InternalTLSCAFile template parameter. Testing protocol is described in the parent change ("I4f853de3b532b3b5e71d29aa621a2925c3885393") Related-Bug: #1946374 Depends-On: Ib0236f9c086d520d0a27e3aa8b41927bc7b50c26 Change-Id: I621557a037fbedc5c110f905dbe19290cc92b772
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 |
|
|
|
|
|
|
|
|
|
|
|
|
swift |
|
|||||||||||
aodh |
|
|
||||||||||
ceilometer |
|
|
||||||||||
gnocchi |
|
|
||||||||||
barbican |
|
|||||||||||
cephrgw |
|
|||||||||||
cephmds |
|
|||||||||||
manila |
|
|||||||||||
collectd |
|
|||||||||||
designate |
|
|||||||||||
octavia |
|
|
||||||||||
rear |
|
|||||||||||
Extra Firewall |
|