df1e016ad7
Currently we start all OpenStack services in step6, but puppet already does this, and sometimes services require configuration to account for the new version after the yum update before they will start. So instead of reimplementing that configuration management in ansible, just defer starting the services until puppet has run which will happen right after the ansible upgrade steps complete. Note there are some DB sync operations etc that we may also be able to remove and let puppet do those steps, but I've left those in for now, as we know there are some actions during that phase e.g nova cells setup, which aren't yet handled by puppet. Change-Id: Idc8e253167a4bc74b086830cfabf28d4aab97d28 |
||
---|---|---|
ci | ||
deployed-server | ||
docker | ||
environments | ||
extraconfig | ||
firstboot | ||
network | ||
puppet | ||
releasenotes/source | ||
scripts | ||
tools | ||
validation-scripts | ||
.gitignore | ||
.gitreview | ||
Gemfile | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
Rakefile | ||
all-nodes-validation.yaml | ||
babel.cfg | ||
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 | ||
overcloud-resource-registry-puppet.j2.yaml | ||
overcloud.j2.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 |
|
|
|
|
|
cinder |
|
|
|
||
heat |
|
|
|
|
|
mysql |
|
|
|
|
|
neutron |
|
|
|
|
|
rabbitmq |
|
|
|
|
|
mongodb |
|
|
|||
redis |
|
||||
haproxy |
|
|
|
|
|
keepalived |
|
|
|
|
|
memcached |
|
|
|
|
|
pacemaker |
|
|
|
|
|
nova |
|
|
|
|
|
ntp |
|
|
|
|
|
snmp |
|
|
|
|
|
timezone |
|
|
|
|
|
sahara |
|
||||
mistral |
|
||||
swift |
|
|
|||
aodh |
|
||||
ceilometer |
|
||||
gnocchi |
|
||||
panko |
|
||||
barbican |
|
||||
zaqar |
|
||||
cephrgw |
|
|