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 StarlingX. For Distributed Cloud, you must include an additional CLI parameter.

About this task

If you prefer, you can use the Horizon Web interface. For more information, see Upload and Apply 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 StarlingX updating procedures, see the StarlingX Updates and Upgrades: Introduction guide.

For SystemController of Distributed Cloud (and the central update repository), you must include the additional CLI parameter --os-region-name with the value SystemController when using CLI 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

Procedure

  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 DC patch orchestration strategy anymore. You need to patch the system controller before using DC orchestration to patch the subclouds.

Postrequisites

To update the software on the subclouds, you must use the Distributed Cloud Update Orchestration. For more information, see Update Orchestration of Subclouds.