| 2020-09-23 12:12:49 |
Takashi Kajinami |
description |
Since Rocky, container image prepare task is always executed during undercloud/overcloud deployment, which inspects container images in source registry and generates a list of container images used.
However this step is unnecessary when all container images are described in a static deployment templates and makes unnecessary requirement that we should prepare required tags in local container registry, to be compatible with container image prepare task.
It would be useful to allow disabling container image prepare tasks, so that operators can depend on only static list of container images, based on the content in their local registry. |
Since Rocky, container image prepare task is always executed during undercloud/overcloud deployment, which inspects container images in source registry and generates a list of container images used.
However this step is unnecessary when all container images are described in a static deployment templates and makes unnecessary requirement that we should prepare required tags in local container registry, to be compatible with container image prepare task.
It would be useful to allow disabling container image prepare tasks, so that operators can depend on only static list of container images, based on the content in their local registry.
This also helps operators avoid unexpected update of container images. Currently container images prepare tasks is executed all deployment actions, and this might generate updated list of container images during deployment, even though operators didn't intend to update any containers. |
|
