Installing a subcloud update

Update documentation regarding installing a subcloud.

Story: 2009811
Task: 50152o

Change-Id: I1447abea270161c90af30018903c795cfdcb8860
Signed-off-by: Elisamara Aoki Goncalves <elisamaraaoki.goncalves@windriver.com>
This commit is contained in:
Elisamara Aoki Goncalves
2024-09-13 18:19:56 +00:00
parent 8af10d5203
commit da40d281b1
2 changed files with 10 additions and 14 deletions

View File

@@ -386,13 +386,11 @@ subcloud ansible log files: ``/var/log/dcmanager/ansible``, and named as
"DNS.1: registry.local DNS.2: registry.central IP.1: floating_management IP.2: floating_OAM" "DNS.1: registry.local DNS.2: registry.central IP.1: floating_management IP.2: floating_OAM"
If required, run the following command on the Central Cloud prior to If required, refer to the
bootstrapping the subcloud to install the new certificate for the Central :ref:`migrate-platform-certificates-to-use-cert-manager-c0b1727e4e5d`
Cloud with the updated |SAN| list: procedure to update the Docker Registry certificate for the Central Cloud.
The procedure will include the with required Domain Names and IPs in the
.. code-block:: none the certificate's |SAN| list.
~(keystone_admin)]$ system certificate-install -m docker_registry path_to_cert
If you prefer to install container images from the default external If you prefer to install container images from the default external
registries, make the following substitutions for the **docker_registries** registries, make the following substitutions for the **docker_registries**

View File

@@ -282,13 +282,11 @@ subcloud, the subcloud installation process has two phases:
list ``"DNS.1: registry.local DNS.2: registry.central IP.1: <floating list ``"DNS.1: registry.local DNS.2: registry.central IP.1: <floating
management\> IP.2: <floating OAM\>"``. management\> IP.2: <floating OAM\>"``.
If required, run the following command on the Central Cloud prior to If required, refer to the
bootstrapping the subcloud to install the new certificate for the Central :ref:`migrate-platform-certificates-to-use-cert-manager-c0b1727e4e5d`
Cloud with the updated |SAN| list: procedure to update the Docker Registry certificate for the Central Cloud.
The procedure will include the with required Domain Names and IPs in the
.. code-block:: none the certificate's |SAN| list.
~(keystone_admin)]$ system certificate-install -m docker_registry path_to_cert
#. Post installation, run the following command to add a subcloud on the system #. Post installation, run the following command to add a subcloud on the system
controller. controller.