From 8a0e02cd0726e13dc6fda166cb592da6252be0de Mon Sep 17 00:00:00 2001 From: Ngairangbam Mili Date: Tue, 17 Oct 2023 10:55:49 +0000 Subject: [PATCH] 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 --- ...ng-redfish-platform-management-service.rst | 25 +++++++++++++------ ...-subcloud-using-dcmanager-df756866163f.rst | 9 +++++++ 2 files changed, 27 insertions(+), 7 deletions(-) diff --git a/doc/source/dist_cloud/kubernetes/installing-a-subcloud-using-redfish-platform-management-service.rst b/doc/source/dist_cloud/kubernetes/installing-a-subcloud-using-redfish-platform-management-service.rst index ccb4f9394..fd4735886 100644 --- a/doc/source/dist_cloud/kubernetes/installing-a-subcloud-using-redfish-platform-management-service.rst +++ b/doc/source/dist_cloud/kubernetes/installing-a-subcloud-using-redfish-platform-management-service.rst @@ -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. diff --git a/doc/source/dist_cloud/kubernetes/prestage-a-subcloud-using-dcmanager-df756866163f.rst b/doc/source/dist_cloud/kubernetes/prestage-a-subcloud-using-dcmanager-df756866163f.rst index 2366ff1f4..58dae4c9f 100644 --- a/doc/source/dist_cloud/kubernetes/prestage-a-subcloud-using-dcmanager-df756866163f.rst +++ b/doc/source/dist_cloud/kubernetes/prestage-a-subcloud-using-dcmanager-df756866163f.rst @@ -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