ef14f86f5d
This is a squash of 2 backports to fix Galera deployment on Liberty. 1) Enable galera replication for Mariadb 10.1 The generated galera config has to include additional settings for galera to be active on MariaDB 10.1. wsrep_on must be explicitely set to ON. On MariaDB 5.5, this was implicitely set as soon as wsrep_provider was specified. a valid wsrep_cluster_address must be configured in addition to wsrep_on, otherwise recovery command mysqld_safe --wsrep-recover cannot retrieve replication state, and cluster cannot be bootstrapped. These explicit settings are backward compatible with MariaDB 5.5 since the two variables exist in both versions of MariaDB. Closes-Bug: 1563751 (cherry-picked from commit |
||
|---|---|---|
| deprecated | ||
| docker | ||
| environments | ||
| extraconfig | ||
| firstboot | ||
| network | ||
| os-apply-config | ||
| puppet | ||
| tools | ||
| tripleo_heat_merge | ||
| validation-scripts | ||
| .gitignore | ||
| .gitreview | ||
| Gemfile | ||
| LICENSE | ||
| MANIFEST.in | ||
| Makefile | ||
| README.rst | ||
| Rakefile | ||
| all-nodes-validation.yaml | ||
| babel.cfg | ||
| bootstrap-config.yaml | ||
| net-config-bond.yaml | ||
| net-config-bridge.yaml | ||
| net-config-linux-bridge.yaml | ||
| net-config-noop.yaml | ||
| net-config-static-bridge.yaml | ||
| overcloud-resource-registry-puppet.yaml | ||
| overcloud-resource-registry.yaml | ||
| overcloud-without-mergepy.yaml | ||
| overcloud.yaml | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| test_merge.bash | ||
| tox.ini | ||
README.rst
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, os-apply-config, and (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.
- deprecated: contains templates that have been deprecated
- 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.
- os-apply-config: templates mostly driven by configuration w/
os-collect-config and bash based elements (which use the Heat os-apply-config group). These will soon be deprecated and are no longer part of the upstream CI testing efforts.
- validation-scripts: validation scripts useful to all deployment
configurations