RETIRED, Heat templates for deploying OpenStack
670399a2ca
When the firewall is enabled with ipv6, the default rules set is
taken as not ipv6 firewall was present for Newton. This make
communication impossible until puppet is run again.
This ensures that no rules are loaded when the firewall is enabled.
This mimic this patch[1]
[1]
|
||
|---|---|---|
| ci | ||
| deployed-server | ||
| docker | ||
| environments | ||
| extraconfig | ||
| firstboot | ||
| network | ||
| puppet | ||
| releasenotes | ||
| scripts | ||
| tools | ||
| validation-scripts | ||
| .gitignore | ||
| .gitreview | ||
| all-nodes-validation.yaml | ||
| babel.cfg | ||
| bindep.txt | ||
| bootstrap-config.yaml | ||
| capabilities-map.yaml | ||
| default_passwords.yaml | ||
| 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 | ||
| net-config-undercloud.yaml | ||
| overcloud-resource-registry-puppet.j2.yaml | ||
| overcloud.j2.yaml | ||
| plan-environment.yaml | ||
| README.rst | ||
| requirements.txt | ||
| roles_data_undercloud.yaml | ||
| 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 |
|
|
|
swift + rbd |
|
| cinder |
|
|
|
||
| heat |
|
|
|
|
|
| mysql |
|
|
|
|
|
| neutron |
|
|
|
|
|
| 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 |
|