951d66abe4
We need Docker service mapping defined and set to OS::Heat::None so that we can reuse multinode-container-upgrade.yaml service list both for initial deployment and for the upgrade. The upgrade will not be broken by this as its env files are being passed later on the command line, and they'll take priority and effectively enable the Docker service on upgrade. Another change we need for mixed upgrade is to add the TripleoPackages service, which will take care of updating RPMs on the bare metal and prevent docker installation from failing with outdated puppet-tripleo ("Could not find class ::tripleo::profile::base::docker"). Related-Bug: #1685795 Closes-Bug: #1689772 Change-Id: Idb6917f22d0e9f74f8853972c6a08bffb01be410 |
||
---|---|---|
ci | ||
deployed-server | ||
docker | ||
environments | ||
extraconfig | ||
firstboot | ||
network | ||
puppet | ||
releasenotes | ||
scripts | ||
tools | ||
validation-scripts | ||
.gitignore | ||
.gitreview | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
all-nodes-validation.yaml | ||
babel.cfg | ||
bindep.txt | ||
bootstrap-config.yaml | ||
capabilities-map.yaml | ||
default_passwords.yaml | ||
hosts-config.yaml | ||
j2_excludes.yaml | ||
net-config-bond.yaml | ||
net-config-bridge.yaml | ||
net-config-linux-bridge.yaml | ||
net-config-noop.yaml | ||
net-config-static-bridge-with-external-dhcp.yaml | ||
net-config-static-bridge.yaml | ||
net-config-static.yaml | ||
net-config-undercloud.yaml | ||
network_data.yaml | ||
overcloud-resource-registry-puppet.j2.yaml | ||
overcloud.j2.yaml | ||
plan-environment.yaml | ||
requirements.txt | ||
roles_data.yaml | ||
roles_data_undercloud.yaml | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
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 |
|
|
|
swift + rbd |
|
cinder |
|
|
|
||
heat |
|
|
|
|
|
mysql |
|
|
|
|
|
neutron |
|
|
|
|
|
neutron-bgpvpn |
|
||||
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 |
|
||||
collectd |
|
||||
fluentd |
|
||||
sensu-client |
|