
- Updated the first topic naame and minor changes. - Added a general warning for registry information/credentials. Signed-off-by: Elaine Fonaro <elaine.fonaro@windriver.com> Change-Id: Ibf42c8b24e430d26baf5bb8253485dcfcaa77c52 Signed-off-by: Elaine Fonaro <elaine.fonaro@windriver.com>
42 lines
1.4 KiB
ReStructuredText
42 lines
1.4 KiB
ReStructuredText
|
|
.. qdu1595389242059
|
|
.. _updating-docker-registry-credentials-on-a-subcloud:
|
|
|
|
===========================================================================
|
|
Update Credentials Used by Subcloud for Install Registry (registry.central)
|
|
===========================================================================
|
|
|
|
On a subcloud that uses the System Controller's Docker registry
|
|
(registry.central) as its install registry, you should use the
|
|
System Controller's sysinv service credentials for accessing registry.central.
|
|
This makes access to registry.central independent of changes to the Distributed
|
|
Cloud's Keystone admin user password.
|
|
|
|
.. warning::
|
|
|
|
If the following registry information/credentials are changed, a new subcloud
|
|
backup must be taken to avoid having a backup that contains old registry
|
|
credentials.
|
|
|
|
Use the following procedure to update credentials used by the Subcloud to access
|
|
its install registry (registry.central) to the ``sysinv`` service credentials of
|
|
the System Controller.
|
|
|
|
.. rubric:: |proc|
|
|
|
|
.. _updating-docker-registry-credentials-on-a-subcloud-steps-ywx-wyt-kmb:
|
|
|
|
#. On the System Controller, get the password for the ``sysinv`` services.
|
|
|
|
.. code-block:: none
|
|
|
|
$ keyring get sysinv services
|
|
|
|
#. On each subcloud, run the following script to update the Docker registry
|
|
credentials to ``sysinv``:
|
|
|
|
.. code-block:: none
|
|
|
|
$ update_docker_registry_auth.sh sysinv <sysinv_password>
|
|
|