From e524e3e0e41df2a093643d78952902e754a5be19 Mon Sep 17 00:00:00 2001
From: Francesco Pantano <fpantano@redhat.com>
Date: Fri, 14 Jan 2022 13:18:26 +0100
Subject: [PATCH] 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
---
 .../source/deployment/container_image_prepare.rst     | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/deploy-guide/source/deployment/container_image_prepare.rst b/deploy-guide/source/deployment/container_image_prepare.rst
index a00d04c7..39aba3ef 100644
--- a/deploy-guide/source/deployment/container_image_prepare.rst
+++ b/deploy-guide/source/deployment/container_image_prepare.rst
@@ -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
 ........................