RETIRED, Heat templates for deploying OpenStack
c9596b72a1
When using get-occ-config.sh during overcloud upgrades, the script could potentially be started before the stack has been upgraded. In that scenario, the script will return null for the request metadata url for the deployed-server resource since the stack has not yet been updated and it's still using the previous Heat signaling. This patch updates the script to just continue checking the resource metadata if the request url is null. Eventually, once the resource has been updated, the script will continue and properly populate the os-collect-config configuration. Change-Id: I9db54d8ad278715f42b768edf8f0fd21998b2098 |
||
---|---|---|
ci | ||
deployed-server | ||
docker | ||
environments | ||
extraconfig | ||
firstboot | ||
network | ||
puppet | ||
scripts | ||
tools | ||
validation-scripts | ||
.gitignore | ||
.gitreview | ||
all-nodes-validation.yaml | ||
babel.cfg | ||
bootstrap-config.yaml | ||
capabilities-map.yaml | ||
default_passwords.yaml | ||
Gemfile | ||
hosts-config.yaml | ||
j2_excludes.yaml | ||
LICENSE | ||
MANIFEST.in | ||
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 | ||
overcloud-resource-registry-puppet.j2.yaml | ||
overcloud.j2.yaml | ||
Rakefile | ||
README.rst | ||
requirements.txt | ||
roles_data.yaml | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
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 |
|
||||
swift |
|
|
|||
aodh |
|
||||
ceilometer |
|
||||
gnocchi |
|
||||
barbican |
|
||||
zaqar |
|
||||
cephrgw |
|
|