starlingx/docs
Code Issues Proposed changes

Update "Deploy, Restore and Manage Subclouds of Previous Release" page for USM changes

Browse Source 
Bug: 2077561

Change-Id: Ia364e3628e3b6329bf0cdde6bc86fe794caac4a1
Signed-off-by: Suzana Fernandes <Suzana.Fernandes@windriver.com>
This commit is contained in:
Suzana Fernandes 2024-08-20 18:50:07 +00:00 committed by Suzana Barude Fernandes
parent 9e6c774117
commit 6163200029
1 changed files with 3 additions and 49 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

52
doc/source/dist_cloud/kubernetes/deploy-restore-and-manage-subclouds-of-previous-release-5e986615cb4b.rst
View File

@ -136,19 +136,11 @@ previous (N-1) release, ensure that the following prerequisites are met:
- The N-1 load (pre-patched ISO) must be imported to the system controller - The N-1 load (pre-patched ISO) must be imported to the system controller
using the ``--inactive`` option. This load must be upgradable to the using the the following command:
current active release.
.. warning::
A subcloud running the N-1 release cannot be patched using patch
orchestration. To deploy a subcloud with the latest patch of N-1
release, the N-1 release ISO containing the latest patch must be
imported using the following command:
.. code-block:: none .. code-block:: none
~(keystone_admin)]$ system –os-region-name SystemController load-import --inactive <bootimage>.iso <bootimage>.sig ~(keystone_admin)]$ software --os-region-name SystemController upload <bootimage>.iso <bootimage>.sig
- The central registry (or source registry configured for the subclouds) must - The central registry (or source registry configured for the subclouds) must
contain platform and applications container images of both N and N-1 contain platform and applications container images of both N and N-1
@ -200,44 +192,6 @@ previous (N-1) release, ensure that the following prerequisites are met:
:start-after: images-id-begin :start-after: images-id-begin
:end-before: images-id-end :end-before: images-id-end
Import an Inactive Load
-----------------------
An inactive load can be imported using the ``--inactive`` option with the
``load-import`` command to allow the import of the previous release load on the
system controller.
.. note::
Ensure that the imported ISO is at the same patch level as the system
controller. To check the system controller patch level of N and/or N-1
release, use the :command:`sw-patch query` command.
.. rubric:: |proc|
#. Transfer the pre-patched ISO of the previous release and its signature file
to the system controller.
#. Run the following command.
.. code-block:: none
~(keystone_admin)]$ system --os-region-name SystemController load-import --inactive --local <bootimage>.iso <bootimage>.sig
.. only:: starlingx
.. note::
``load-import --inactive`` is not rejected when importing a
non-upgradable load. The inactive load must be a pre-patched ISO with
|prod| |v_r6| or above.
.. only:: partner
.. include:: /_includes/deploy-restore-and-manage-subclouds-of-previous-release-5e986615cb4b.rest
:start-after: note-begin
:end-before: note-end
Upload Deploy/Prestage files Upload Deploy/Prestage files
---------------------------- ----------------------------
@ -433,7 +387,7 @@ or both of the following steps:
.. code-block:: none .. code-block:: none
~(keystone_admin)]$ system –os-region-name SystemController load-import --active --local <bootimage.iso> <bootimage.sig> ~(keystone_admin)]$ software --os-region-name SystemController upload <bootimage>.iso <bootimage>.sig
#. |optional| Upload the N release images list by using the following command: #. |optional| Upload the N release images list by using the following command: