openstack/kolla-ansible
Code Issues Proposed changes

Explain how to use kolla-ansible pull

Browse Source 
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
This commit is contained in:
Steven Dake 2016-02-25 16:42:55 -07:00
parent db0de9b7af
commit 50c52081de
1 changed files with 9 additions and 3 deletions

12
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 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. scripts to the various nodes where the failed containers are located.
The kolla community has separate commands planned for Mitaka for Any time the tags of a release change, it is possible that the container
reconfiguring the services and upgrading them. These should be used when implementation from older versions won't match the Ansible playbooks in
they are available instead of the deploy operation. 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 Debugging Kolla
--------------- ---------------