Michele Baldessari dd9b008c11 Make the minor update for docker idempotent ... 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		2018-02-26 17:41:02 +01:00
..
extraconfig	Adding new config parameters for Cisco UCSM ML2 driver	2018-02-13 16:26:12 +00:00
manifests	Reinstate common overcloud manifest for all roles	2018-01-11 18:42:45 +00:00
services	Make the minor update for docker idempotent	2018-02-26 17:41:02 +01:00
all-nodes-config.j2.yaml	ffu: Allow FASTFORWARDUPGRADE as a StackUpdateType	2018-02-13 10:53:55 -05:00
deploy-artifacts.sh	Merge "Fix rpms being installed via DeployArtifactURLs"	2017-06-23 17:05:14 +00:00
deploy-artifacts.yaml	Change template names to queens	2017-11-23 10:15:32 +01:00
role.role.j2.yaml	Fix invalid Ceph and BlockStorage role template	2018-02-22 11:08:36 +01:00
upgrade_config.yaml	Change template names to queens	2017-11-23 10:15:32 +01:00