From 6052c4329caac4068283468793e084c02827bf39 Mon Sep 17 00:00:00 2001 From: Bogdan Dobrelya Date: Mon, 4 Jun 2018 11:50:37 +0200 Subject: [PATCH] Clarify commands for local registry push/prepare Co-authored-by: Steve Baker Change-Id: Ie5fbf68d3c456572d83c44414600b46b3b1ce999 Signed-off-by: Bogdan Dobrelya --- doc/source/install/containers_deployment/overcloud.rst | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/doc/source/install/containers_deployment/overcloud.rst b/doc/source/install/containers_deployment/overcloud.rst index fd6cee59..9b9710e5 100644 --- a/doc/source/install/containers_deployment/overcloud.rst +++ b/doc/source/install/containers_deployment/overcloud.rst @@ -100,6 +100,15 @@ pull and push destinations:: --output-env-file ~/docker_registry.yaml \ --output-images-file overcloud_containers.yaml +.. note:: Use the IP address of your undercloud, which you previously set with + the `local_ip` parameter in your `undercloud.conf` file. For these example + commands, the address is assumed to be `192.168.24.1:8787`. + +This creates an `~/docker_registry.yaml` environment file, which contains image +locations on the undercloud. You include this file with your deployment. +This also creates a file called `overcloud_containers.yaml` with your +container image information you should use to push images into the local registry. + .. admonition:: Stable Branch :class: stable