openstack/tripleo-heat-templates
Code Issues Proposed changes

HA: ClusterFullTag naming convention by default

Browse Source 
The old naming convention ClusterCommonTag [1] has been
superseded by the more generic ClusterFullTag [2], which
allow any part of a container image to change during a
minor update, without causing HA service disruption in
the control plane.

Enable that new convention by default for this cycle.

[1] Id369154d147cd5cf0a6f997bf806084fc7580e01
[2] I124c1e4dbcc7a8ed38079411f41a8f31c8f62284

Change-Id: I9bc0e4991783567a4e9e7dc9d5c22e1f957da5be
This commit is contained in:
Damien Ciabrini 2020-10-28 16:04:17 +01:00
parent f9e860a4d2
commit 50f062da7f
2 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
environments/docker-ha.yaml
View File

@ -22,4 +22,4 @@ resource_registry:
parameter_defaults:
ContainerCli: podman
ClusterCommonTag: true
ClusterFullTag: true

10
releasenotes/notes/pacemaker-enable-cluster-full-tag-f868a6f0b1f16018.yaml Normal file
View File

@ -0,0 +1,10 @@
---
features:
- |
New Heat parameter ClusterFullTag controls how we configure
pacemaker container image names for the HA services. Compared to
the previous parameter ClusterCommonTag, this new naming
convention allows any part of the container image name to change
during a minor update, without service disruption. e.g.,
registryA/namespaceA/imgA:tagA to registryB/namespaceB/imgB:tagB
This new paramter ClusterFullTag is enabled by default.