openstack
/
tripleo-docs
Code Issues Proposed changes

Default to docker.io instead of trunk.registry.rdoproject.org 

trunk.registry.rdoproject.org is not meant for production or stable
use. It is a staging ground where containers are tested for promotion
purposes before being pushed to docker.io.

Change-Id: Ie834ee076d9922ed67a8043dfab6ae04e07acd77
This commit is contained in:
David Moreau Simard 2018-02-09 14:28:12 -05:00
parent f371451cde
commit c020911152
No known key found for this signature in database
GPG Key ID: 33A07694CBB71ECC
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/source/install/containers_deployment/overcloud.rst
View File

@ -47,7 +47,7 @@ following command will return the tag from the RDO docker registry using the
stable tag ``current-tripleo-rdo``::
openstack overcloud container image tag discover \
--image trunk.registry.rdoproject.org/master/centos-binary-base:current-tripleo-rdo \
--image docker.io/tripleomaster/centos-binary-base:current-tripleo-rdo \
--tag-from-label rdo_version
.. note:: The tag is actually a Delorean hash. You can find out the versions
@ -56,7 +56,7 @@ stable tag ``current-tripleo-rdo``::
is in fact using this `Delorean repository`_.
The option ``--image
trunk.registry.rdoproject.org/master/centos-binary-base:current-tripleo-rdo``
docker.io/tripleomaster/centos-binary-base:current-tripleo-rdo``
will typically be replaced with a value specific to the environment. You may
wish to use stable tag ``tripleo-passed-ci`` for a more stable set of
containers.
@ -71,11 +71,11 @@ a heat environment file `~/docker_registry.yaml` to deploy an overcloud
with container images from RDO docker registry::
openstack overcloud container image prepare \
--namespace trunk.registry.rdoproject.org/master \
--namespace docker.io/tripleomaster \
--tag <tag> \
--output-env-file ~/docker_registry.yaml
The option ``--namespace trunk.registry.rdoproject.org/master``
The option ``--namespace docker.io/tripleomaster``
will typically be replaced with a value specific to the
environment. Run with ``--help`` to see the other options available for
controlling what is generated.
@ -103,7 +103,7 @@ up the ``overcloud_containers.yaml`` configuration file containing the
pull and push destinations::
openstack overcloud container image prepare \
--namespace trunk.registry.rdoproject.org/master \
--namespace docker.io/tripleomaster \
--tag <tag> \
--push-destination 192.168.24.1:8787 \
--output-env-file ~/docker_registry.yaml \