f37c06cd9d
Currently, the idiomatic "download image and retag to pcmklatest"
happens at step 2 during upgrade. This doesn't work if the stack
is already containerized before the upgrade, because pacemaker
is still running at step 2.
Reshuffle the steps at which the various upgrade tasks are run,
while keeping the ordering guarantees of the upgrade flow:
. Deletion of non-containerized resources happens at step 1,
to allow calling pcs while pacemaker is running.
. Pacemaker is stopped at step 2.
. Docker images for containerized resources are upgraded at
step 3, after the cluster is guaranteed to be stopped.
. Pacemaker is restarted at step 4 as before, once we know
that all resources have been upgraded, yum packages updated
and any potential docker restart has been executed.
Also change the way we detect containerized resources, so that
the predicate still remains valid past step 2 when pacemaker
has been stopped and has deleted its containerized resources.
Change-Id: I85e11dd93c7fd2c42e71b467f46b0044d4516524
|
||
|---|---|---|
| ci | ||
| common | ||
| deployed-server | ||
| docker | ||
| environments | ||
| extraconfig | ||
| firstboot | ||
| network | ||
| plan-samples | ||
| puppet | ||
| releasenotes | ||
| roles | ||
| sample-env-generator | ||
| scripts | ||
| tools | ||
| tripleo_heat_templates | ||
| validation-scripts | ||
| zuul.d | ||
| .gitignore | ||
| .gitreview | ||
| .testr.conf | ||
| LICENSE | ||
| README.rst | ||
| all-nodes-validation.yaml | ||
| babel.cfg | ||
| bindep.txt | ||
| bootstrap-config.yaml | ||
| capabilities-map.yaml | ||
| config-download-software.yaml | ||
| config-download-structured.yaml | ||
| default_passwords.yaml | ||
| hosts-config.yaml | ||
| j2_excludes.yaml | ||
| net-config-bond.j2.yaml | ||
| net-config-bridge.j2.yaml | ||
| net-config-linux-bridge.j2.yaml | ||
| net-config-noop.j2.yaml | ||
| net-config-static-bridge-with-external-dhcp.j2.yaml | ||
| net-config-static-bridge.j2.yaml | ||
| net-config-static.j2.yaml | ||
| net-config-undercloud.j2.yaml | ||
| network_data.yaml | ||
| network_data_ganesha.yaml | ||
| overcloud-resource-registry-puppet.j2.yaml | ||
| overcloud.j2.yaml | ||
| plan-environment.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 (2.0)
- Documentation: https://docs.openstack.org/tripleo-docs/latest/
- Source: http://git.openstack.org/cgit/openstack/tripleo-heat-templates
- Bugs: https://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
- roles: example roles that can be used with the tripleoclient to generate
a roles_data.yaml for a deployment See the roles/README.rst for additional details.
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:
| - | scn000 | scn001 | scn002 | scn003 | scn004 | scn006 | scn007 | scn009 | non-ha | ovh-ha |
|---|---|---|---|---|---|---|---|---|---|---|
| openshift |
|
|||||||||
| keystone |
|
|
|
|
|
|
|
|
|
|
| glance |
|
swift |
|
|
|
|
|
|
||
| cinder |
|
iscsi | ||||||||
| heat |
|
|
||||||||
| ironic |
|
|||||||||
| mysql |
|
|
|
|
|
|
|
|
|
|
| neutron |
|
|
|
|
|
|
|
|
||
| neutron-bgpvpn |
|
|||||||||
| ovn |
|
|||||||||
| neutron-l2gw |
|
|||||||||
| rabbitmq |
|
|
|
|
|
|
|
|
||
| mongodb | ||||||||||
| redis |
|
|
||||||||
| haproxy |
|
|
|
|
|
|
|
|
||
| memcached |
|
|
|
|
|
|
|
|
||
| pacemaker |
|
|
|
|
|
|
|
|
||
| nova |
|
|
|
|
ironic |
|
|
|
||
| ntp |
|
|
|
|
|
|
|
|
|
|
| snmp |
|
|
|
|
|
|
|
|
|
|
| timezone |
|
|
|
|
|
|
|
|
|
|
| sahara |
|
|||||||||
| mistral |
|
|||||||||
| swift |
|
|||||||||
| aodh |
|
|
||||||||
| ceilometer |
|
|
||||||||
| gnocchi |
|
|
||||||||
| panko |
|
|
||||||||
| barbican |
|
|||||||||
| zaqar |
|
|||||||||
| ec2api |
|
|||||||||
| cephrgw |
|
|||||||||
| tacker |
|
|||||||||
| congress |
|
|||||||||
| cephmds |
|
|||||||||
| manila |
|
|||||||||
| collectd |
|
|||||||||
| fluentd |
|
|||||||||
| sensu-client |
|