Subcloud remote install with patched iso (r8, ds8)
REVIEW EXPECTED TO BE COMPLETED BY 3RD NOV '23. Added notes about the need of iso imported via load-import --active to be at the same patch level as the system controller for the prestaged and non-prestaged subcloud remote installation. Change-Id: I778977df3779bbb08aebe59713fe4681bf91f163 Signed-off-by: Ngairangbam Mili <ngairangbam.mili@windriver.com>
This commit is contained in:
parent
3b4c0f675e
commit
8a0e02cd07
@ -58,17 +58,28 @@ subcloud, the subcloud installation has these phases:
|
||||
|
||||
.. note::
|
||||
|
||||
This is required only once and does not have to be done for every
|
||||
subcloud install.
|
||||
- This is required only once and does not have to be done for every
|
||||
subcloud install.
|
||||
|
||||
:command:`dcmanager` recognizes bootimage names ending in <.iso> and
|
||||
<.sig>
|
||||
:command:`dcmanager` recognizes bootimage names ending in ``.iso`` and
|
||||
``.sig``.
|
||||
|
||||
For example,
|
||||
For example,
|
||||
|
||||
.. parsed-literal::
|
||||
.. parsed-literal::
|
||||
|
||||
~(keystone_admin)]$ system --os-region-name SystemController load-import --active |installer-image-name|.iso |installer-image-name|.sig
|
||||
~(keystone_admin)]$ system --os-region-name SystemController load-import --active |installer-image-name|.iso |installer-image-name|.sig
|
||||
|
||||
- The ISO imported via ``load-import --active`` must be at the same
|
||||
patch level as the system controller. This ensures that the subcloud
|
||||
boot image aligns with the patch level of the load to be installed on
|
||||
the subcloud.
|
||||
|
||||
.. warning::
|
||||
|
||||
If the patch level of load-imported ISO does not match the system controller
|
||||
patch level, the subcloud patch state may not align with the system
|
||||
controller patch state.
|
||||
|
||||
- Run the :command:`load-import` command on controller-0 to import
|
||||
the new release.
|
||||
|
@ -75,6 +75,15 @@ There are two types of subcloud prestage:
|
||||
image pulls and archive file generation. If the total size of prestage
|
||||
images is N GB, available Docker space should be N*2 GB.
|
||||
|
||||
.. note::
|
||||
|
||||
For the prestaged remote subcloud installations, the ISO imported via
|
||||
``load-import --inactive`` must be at the same patch level as the system
|
||||
controller. If the system controller is patched after prestaging of
|
||||
subclouds, you need to repeat the prestaging of each subcloud. This
|
||||
ensures that the subcloud boot image aligns with the patch level of the
|
||||
load that needs to be installed on the subcloud.
|
||||
|
||||
.. warning::
|
||||
|
||||
If the available docker space is inadequate, some application pods can get
|
||||
|
Loading…
x
Reference in New Issue
Block a user