aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJenkins <jenkins@review.openstack.org>2016-03-21 00:21:24 +0000
committerGerrit Code Review <review@openstack.org>2016-03-21 00:21:24 +0000
commit783d17412d5d0b41735cfac3a5c2971c084ce3d2 (patch)
treed6b9f3af60c07110879e14f0fcb062db2cad35e0
parent6e9c51898e83f5e4e324654a8958d7142d21ab7c (diff)
parent50c52081deda33a4403be9b58a83e2fd7113adb8 (diff)
downloadkolla-783d17412d5d0b41735cfac3a5c2971c084ce3d2.tar.gz
kolla-783d17412d5d0b41735cfac3a5c2971c084ce3d2.zip
Merge "Explain how to use kolla-ansible pull"
-rw-r--r--doc/quickstart.rst12
1 files changed, 9 insertions, 3 deletions
diff --git a/doc/quickstart.rst b/doc/quickstart.rst
index 9595ac34a..ea7271340 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
---------------