openstack
/
tripleo-docs
Code Issues Proposed changes

Split off Ceph related container images 

This change describes the required parameters we need to skip
the ceph related containers during container image prepare.

Depends-On: I7e337596b653cf635f07a36606e9f673044402a3
Change-Id: I53d0fdee72a2de2143226a2e1f7fe3c75701f16a
This commit is contained in:
Francesco Pantano 2022-01-14 13:18:26 +01:00
parent 279afa6b97
commit e524e3e0e4
No known key found for this signature in database
GPG Key ID: 0458D4D1F41BD75C
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
deploy-guide/source/deployment/container_image_prepare.rst
View File

@ -219,6 +219,17 @@ The values in the `set` map are used when evaluating the file
`/usr/share/openstack-tripleo-common/container-images/tripleo_containers.yaml.j2`
as a Jinja2 template. This file contains the list of every container image and
how it relates to TripleO services and heat parameters.
If Ceph is not part of the overcloud deployment, it's possible to skip pulling
the related containers by setting the `ceph_images` parameter to false as shown
in the example below::
ContainerImagePrepare:
- push_destination: 192.168.24.1:8787
set:
ceph_images: false
By doing this, the Ceph container images are not pulled from the remote registry
during the deployment.
Authenticated Registries
........................