a166ec6bca
HA services get their container image name from a pacemaker resource configuration. This image name is shared between all cluster nodes. To achieve image update without service disruption, a pacemaker resource is configured to use an intermediate image name "<registry>/<namespace>/<servicename>:pcmklatest" pointing to the real image name configured in Heat. This tag can then be updated independently on every node during the minor update. In order to support the same rolling update when the <namespace> changes in the container image, we need a similar floating approach for the prefix part of the container image. Introduce a new Heat parameter ClusterCommonTag that, when enabled, sets the intermediate image name to "cluster-common-tag/<servicename>:pcmklatest". By default, this parameter is disabled and the original naming scheme is conserved. Note: by introducing this new naming scheme, we stop seeing a meaningful image name prefix when doing a "pcs status", but since we already can't tell what image ID the :pcmklatest tag points to, we don't lose much information really. Related-Bug: #1854730 Change-Id: Id369154d147cd5cf0a6f997bf806084fc7580e01
13 lines
689 B
YAML
13 lines
689 B
YAML
---
|
|
features:
|
|
- HA services use a special container image name derived from the one
|
|
configured in Heat parameter plus a fixed tag part, i.e.
|
|
'<registry>/<namespace>/<servicename>:pcmklatest'. To implement rolling
|
|
update without service disruption, this 'pcmklatest' tag is adjusted
|
|
automatically during minor update every time a new image is pulled.
|
|
A new Heat parameter ClusterCommonTag can now control the prefix part
|
|
of the container image name. When set to true, the container name
|
|
for HA services will look like
|
|
'container-common-tag/<servicename>:pcmklatest'. This allows rolling
|
|
update of HA services even when the <namespace> changes in Heat.
|