From 50c52081deda33a4403be9b58a83e2fd7113adb8 Mon Sep 17 00:00:00 2001
From: Steven Dake <stdake@cisco.com>
Date: Thu, 25 Feb 2016 16:42:55 -0700
Subject: [PATCH] Explain how to use kolla-ansible pull

During multi-node, it is possible for master target node images to
be older then the Ansible master playboks if the repository is
updated.  Add documentation to explain this situation.

Change-Id: I2ccf57004147873e89f23fbb996d01f550e90c3f
---
 doc/quickstart.rst | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/doc/quickstart.rst b/doc/quickstart.rst
index 9595ac34a9..ea72713409 100644
--- a/doc/quickstart.rst
+++ b/doc/quickstart.rst
@@ -542,9 +542,15 @@ On each node where OpenStack is deployed run:
 The Operator will have to copy via scp or some other means the cleanup
 scripts to the various nodes where the failed containers are located.
 
-The kolla community has separate commands planned for Mitaka for
-reconfiguring the services and upgrading them.  These should be used when
-they are available instead of the deploy operation.
+Any time the tags of a release change, it is possible that the container
+implementation from older versions won't match the Ansible playbooks in
+a new version.  If running multinode from a registry, each node's Docker
+image cache must be refreshed with the latest images before a new deployment
+can occur.  To refresh the docker cache from the local Docker registry:
+
+::
+
+    kolla-ansible pull
 
 Debugging Kolla
 ---------------