RETIRED, Heat templates for deploying OpenStack
4138b26ef3
This is necessary for when HAProxy is terminating TLS for manila, else we will have keystone discovery errors. This is the same we do for several other services, as manila uses the same middleware. Change-Id: Ice78b0abceb6a956bb8c1dc6212ee1b56b62b43f |
||
|---|---|---|
| deployed-server | ||
| docker | ||
| environments | ||
| extraconfig | ||
| firstboot | ||
| network | ||
| puppet | ||
| tools | ||
| validation-scripts | ||
| .gitignore | ||
| .gitreview | ||
| all-nodes-validation.yaml | ||
| babel.cfg | ||
| bootstrap-config.yaml | ||
| capabilities-map.yaml | ||
| default_passwords.yaml | ||
| Gemfile | ||
| 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.yaml | ||
| overcloud.j2.yaml | ||
| Rakefile | ||
| README.rst | ||
| requirements.txt | ||
| roles_data.yaml | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
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