be05b9bc37
Rerunning the overcloud deploy command with no changes restarts a truckload of containers (first seen this via https://bugzilla.redhat.com/show_bug.cgi?id=1612960). So we really have three separate issues here. Below is the list of all the containers that may restart needlessly (at least what I have observed in my tests): A) cron category: ceilometer_agent_notification cinder_api cinder_api_cron cinder_scheduler heat_api heat_api_cfn heat_api_cron heat_engine keystone keystone_cron logrotate_crond nova_api nova_api_cron nova_conductor nova_consoleauth nova_metadata nova_scheduler nova_vnc_proxy openstack-cinder-volume-docker-0 panko_api These end up being restarted because in the config volume for the container there is a cron file and cron files are generated with a timestamp inside: $ cat /var/lib/config-data/puppet-generated/keystone/var/spool/cron/keystone ... # HEADER: This file was autogenerated at 2018-08-07 11:44:57 +0000 by puppet. ... The timestamp is unfortunately hard coded into puppet in both the cron provider and the parsedfile provider: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/cron/crontab.rb#L127 https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/parsedfile.rb#L104 We fix this by repiping tar into 'tar xO' and grepping away any line that starts with # HEADER. B) swift category: swift_account_auditor swift_account_reaper swift_account_replicator swift_account_server swift_container_auditor swift_container_replicator swift_container_server swift_container_updater swift_object_auditor swift_object_expirer swift_object_replicator swift_object_server swift_object_updater swift_proxy swift_rsync So the swift containers restart because when recalculating the md5 over the /var/lib/config-data/puppet-generated/swift folder we also include: B.1) /etc/swift/backups/... which is a folder which over time collects backup of the ringfiles B.2) /etc/swift/*.gz it seems that the *.gz files seem to change over time We just add a parameter to the tar command to exclude those files as we do not need to trigger a restart if those files change. --exclude='*/etc/swift/backups/*' --exclude='*/etc/swift/*.gz' C) libvirt category: nova_compute nova_libvirt nova_migration_target nova_virtlogd This one seems to be due to the fact that the /etc/libvirt/passwd.db file contains a timestamp and even when we disable a user and passwd.db does not exist, it gets created: [root@compute-1 nova_libvirt]# git diff cb2441bb1caf7572ccfd870561dcc29d7819ba04..0c7441f30926b111603ce4d4b60c6000fe49d290 . passwd.db changes do not need to trigger a restart of the container se we can safely exclude this file from any md5 calculation. Part C) was: Co-Authored-By: Martin Schupper <mschuppe@redhat.com> We only partial-bug this one because we want a cleaner fix where exceptions to the files being checksummed will be specified in the tht service files. Partial-Bug: #1786065 Tested as follows: ./overcloud_deploy.sh tripleo-ansible-inventory --static-yaml-inventory inv.yaml ansible -f1 -i inv.yaml -m shell --become -a "docker ps --format=\"{{ '{{' }}.Names{{ '}}' }}: {{ '{{' }}.CreatedAt{{ '}}' }}\" | sort" overcloud > before ./overcloud_deploy.sh ansible -f1 -i inv.yaml -m shell --become -a "docker ps --format=\"{{ '{{' }}.Names{{ '}}' }}: {{ '{{' }}.CreatedAt{{ '}}' }}\" | sort" overcloud > after diff -u before after | wc -l 0 Change-Id: I10f5cacd9fee94d804ebcdffd0125676f5a209c4 (cherry picked from commit |
||
|---|---|---|
| ci | ||
| common | ||
| deployed-server | ||
| docker | ||
| docker_config_scripts | ||
| 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 |
|