starlingx/docs
Code Issues Proposed changes

Merge "Fix dcmanager log file location Formatting Fixes. The updates are done."

Browse Source
This commit is contained in:
Zuul 2022-03-16 11:45:52 +00:00 committed by Gerrit Code Review
commit fbe14afd2a
1 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/source/dist_cloud/kubernetes/installing-a-subcloud-without-redfish-platform-management-service.rst
View File

@ -77,7 +77,7 @@ subcloud, the subcloud installation process has two phases:
For subclouds, the initial IP Interface should be the planned |OAM| IP
Interface for the subcloud.
Use the update-iso.sh script from |dnload-loc|. The script is used as
Use the ``update-iso.sh`` script from |dnload-loc|. The script is used as
follows:
.. code-block:: none
@ -154,7 +154,7 @@ subcloud, the subcloud installation process has two phases:
|OAM| IP Address.
#. At the System Controller, create a
/home/sysadmin/subcloud1-bootstrap-values.yaml overrides file for the
``/home/sysadmin/subcloud1-bootstrap-values.yaml`` overrides file for the
subcloud.
For example:
@ -277,7 +277,7 @@ subcloud, the subcloud installation process has two phases:
deployment by monitoring the following log files on the active controller
in the Central Cloud.
/var/log/dcmanager/<subcloud\_name>\_bootstrap\_<date\_stamp>.log
``/var/log/dcmanager/ansible/<subcloud\_name>\_bootstrap\_<date\_stamp>.log``
For example:
@ -300,8 +300,9 @@ subcloud, the subcloud installation process has two phases:
.. _installing-a-subcloud-without-redfish-platform-management-service-ul-ixy-lpv-kmb:
- Provision the newly installed and bootstrapped subcloud. For detailed
|prod| deployment procedures for the desired deployment
configuration of the subcloud, see the post-bootstrap steps of |inst-doc|.
|prod| deployment procedures for the desired deployment configuration of
the subcloud, see the post-bootstrap steps of :ref:`Installation Guides
<index-install-e083ca818006>`.
- Check and update docker registry credentials on the subcloud:
@ -314,9 +315,9 @@ subcloud, the subcloud installation process has two phases:
{SECRET_UUID} | awk '{print $2}''
openstack secret get ${SECRET_REF} --payload -f value
The secret payload should be, ":command:`username: sysinv`
password:<password>". If the secret payload is, "username: admin
password:<password>", see, :ref:`Updating Docker Registry Credentials on a
The secret payload should be :command:`username: sysinv password:<password>`.
If the secret payload is :command:`username: admin password:<password>`,
see, :ref:`Updating Docker Registry Credentials on a
Subcloud <updating-docker-registry-credentials-on-a-subcloud>` for more
information.