command points to new registry version, needs to fix documentation to avoid version dependency/update

[Rahul Sharma]

This is more of a documentation bug. I am referring to this documentation guide:
http://docs.openstack.org/developer/kolla/multinode.html

I am concerned about this paragraph:
The Kolla community recommends using registry 2.3 or later. To deploy registry 2.3 do the following:
docker run -d -p 4000:5000 --restart=always --name registry registry:2

I guess, docker keeps on updating the registry:2 tag to whatever is the latest stable version. Right now, registry:2 points to version 2.4 and in future, will point to 2.5.

The paragraph in documentation says "To deploy registry 2.3 do the following:", but this actually installs registry version 2.4. This paragraph needs to be fixed so that even with docker registry version upgrades, there is no contradicting statement here.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/340618

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/340618
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=fbfab6a9916d9ae3eedeff9063e48d045aa7e292
Submitter: Jenkins
Branch: master

commit fbfab6a9916d9ae3eedeff9063e48d045aa7e292
Author: Rahul Sharma <email address hidden>
Date: Mon Jul 11 19:31:05 2016 -0400

    corrected documentation for registry version

    The documentation was saying of installing registry 2.3 but
    the tag used is registry:2. This tag gets updated to the recent
    versions of registry, and hence, this fix was required.
    Closes-Bug: 1598231

    Change-Id: I3c37c3564678467402223a48c69a1ae7ccbaeebb

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/kolla 3.0.0.0b2 development milestone.