d0f1b1e241
Images for containerized underclouds can be parametrized differently as for overcloud deployments. For example, undercloud may fetch images from a promotion pipeline, while overcloud may consume those from the local registry hosted undercloud. Align the containerized undercloud case with the recent changes docker registry host, namespace and tag defaults. Consumed these from the common defaults, yet allowing to diverge. Fix conditions for undercloud-deploy to always prepare undercloud images for containerized underclouds. If built locally with kolla, the undercloud_docker_* parameters should point to a local registry. If fetched from remote registry, the same logic applies. Altering `undercloud_docker_*` allows to cover such cases. Add the missing `undercloud_docker_registry_tag` parameter. Allow omitting `undercloud_docker_registry_port`, when a registry host value does not require a port, like 'docker.io' host. Closes-bug: #1733800 Change-Id: Ic3d448c8215f44a957711e666a34e78482d8100d Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
16 lines
763 B
YAML
16 lines
763 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Containerized underclouds are allowed to have a custom
|
|
`undercloud_docker_registry_tag`. `undercloud_docker_registry_port`
|
|
may be omitted, if `undercloud_docker_registry_host` does not
|
|
expect a custom port, like 'docker.io'.
|
|
|
|
The docker registry host, port and tag for containerized undercloud
|
|
services default to the values provided for overcloud deployments.
|
|
You may want to alter it, if building images locally with Kolla, or
|
|
fetching from remote registries not fitting overcloud deployment cases.
|
|
As overcloud deployments may consume images form the undercloud local
|
|
registry, it is possible to have `undercloud_docker_*` and
|
|
`docker_*` params diverged for containerized underclouds vs overclouds.
|