![Michele Baldessari](/assets/img/avatar_default.png)
Via Ic08468854ce92e81cd84bd6c86a6b672b5a9d49b we fixed the problem of docker being restarted when puppet triggers a change while pacemaker is up and running. That approach, while more correct than what existed previously, is still suboptimal because we are stopping all docker containers even though we don't have to. Let's detect if applying the profile::base::docker manifest would introduce any changes and also detect if the docker rpm is going to be updated. If one of the two conditions is true we need to stop containers. This way rerunning the update workflow on a node should be much less disruptive. Tested this and correctly observed that the first run did correctly stopped the docker containers whereas subsequent runs did not stop containers. Change-Id: I9176da730b0156d06e2a1ef5f2fcc061e2a6abf6 Related-Bug: #1747851
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:
- | 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 |
|