starlingx/docs
Code Issues Proposed changes
d466920c10
docs/doc/source/dist_cloud/kubernetes/uploading-and-applying-updates-to-systemcontroller-using-the-cli.rst
Elisamara Aoki Goncalves f3f94b273a Patch Orchestration Phase Operations (dsR8) 
Story: 2010584
Task: 48998

Change-Id: I48c2960362e3fd04f0175e74e2611b68e6b846f3
Signed-off-by: Elisamara Aoki Goncalves <elisamaraaoki.goncalves@windriver.com>
2023-11-13 13:27:42 +00:00

3.7 KiB
Raw Blame History

Upload and Apply Updates to SystemController Using the CLI

You can upload and apply updates to the SystemController in order to update the central update repository, from the CLI using the standard update procedures for . For , you must include an additional parameter.

If you prefer, you can use the Horizon Web interface. For more information, see uploading-and-applying-updates-to-systemcontroller-using-horizon, however the specific procedure for incrementally uploading and applying one or more patches for the SystemController is provided below.

For standard updating procedures, see the : software-updates-and-upgrades-software-updates guide.

For SystemController of (and the central update repository), you must include the additional parameter --os-region-name with the value SystemController when using sw-patch commands.

Note

When adding a new subcloud, you only need to create and apply an update strategy to apply all updates that were previously applied in the system controller to the new subcloud.

Note

The following existing sw-patch commands are not supported in the System Controller region:

  • sw-patch query-hosts
  • sw-patch host-install
  • sw-patch host-install-async
  • sw-patch host-install-local
  • sw-patch drop-host

  1. Log in as the sysadmin user.

  2. Copy all patches to be uploaded and applied to /home/sysadmin/patches/.

  3. Upload all patches placed in /home/sysadmin/patches/ to the storage area.

    ~(keystone_admin)]$ sw-patch upload-dir /home/sysadmin/patches --os-region-name SystemController

    Note

    You may receive a warning about the update already being imported. This is expected and occurs if the update was uploaded locally to the system controller. The warning will only occur for patches that were applied to controller-0 (system controller) before it was first unlocked.

  4. Confirm that the newly uploaded patches have a status of available.

    ~(keystone_admin)]$ sw-patch query --os-region-name SystemController

  5. Apply all available updates in a single operation.

    ~(keystone_admin)]$ sw-patch apply --all --os-region-name SystemController

  6. Confirm that the updates have been applied.

    ~(keystone_admin)]$ sw-patch query --os-region-name SystemController

  7. To update the RegionOne, create the patch strategy using:

    ~(keystone_admin)]$ sw-manager patch-strategy create

  8. Apply the patch strategy:

    ~(keystone_admin)]$ sw-manager patch-strategy apply

    Note

    The system controller is not included in the patch orchestration strategy anymore. You need to patch the system controller before using orchestration to patch the subclouds.

To update the software on the subclouds, you must use the Update Orchestration. For more information, see update-orchestration-of-central-clouds-regionone-and-subclouds.