starlingx/docs
Code Issues Proposed changes
docs/doc/source/updates/kubernetes/firmware-update-operations-requiring-manual-migration.rst
egoncalv 4dd4fa7463 Editorial updates - Admin Tasks, User tasks, and Updates and Upgrades Guides. 
Acted on Greg's comments

Patch 1: Acted on Greg's comments and added the missing files.

Patch 2: Solved merge conflicts

Signed-off-by: egoncalv <elisamaraaoki.goncalves@windriver.com>
Change-Id: I70c5d3b9c3927320f977b62878ee60ab9956fc91
2021-05-28 13:55:44 +00:00

1.9 KiB
Raw Blame History

Firmware Update Operations Requiring Manual Migration

On systems with the -openstack application there may be some instances that cannot be migrated automatically by orchestration. In these cases the instance migration must be managed manually.

Do the following to manage the instance re-location manually:

  • Manually firmware update at least one openstack-compute worker host. This assumes that at least one openstack-compute worker host does not have any instances, or has instances that can be migrated. For more information on manually updating a host, see the Display Worker Host Information <displaying-worker-host-information>.
  • If the migration is prevented by limitations in the VNF or virtual application, perform the following:

    • Create new instances on an already updated openstack-compute worker host.

    • Manually migrate the data from the old instances to the new instances.

      Note

      This is specific to your environment and depends on the virtual application running in the instance.

    • Terminate the old instances.

  • If the migration is prevented by the size of the instances local disks:
    • For each openstack-compute worker host that has instances that cannot be migrated, manually move the instances using the CLI. For more information, see Firmware Update Orchestration Using the CLI <firmware-update-orchestration-using-the-cli>.

Once all openstack-compute worker hosts containing instances that cannot be migrated have been firmware updated, firmware update orchestration can then be used to update the remaining worker hosts.