starlingx/docs
Code Issues Proposed changes
docs/doc/source/system_configuration/configuring-a-live-migration-completion-timeout-in-nova.rst
Drake Finlay 54ec38e256 Adding System Config Guide 
Incorporated patchset 8 review comments from Mary C.

Conditionalized vendor-specific terms and converted code-block to
parsed-literal as required
Reformatted bulleted lists to definition lists
Implemented abbreviation substitutions
Deleted duplicate content
Some minor edits for clarity
Merged new abbreviation definitions in strings.txt

Responding to Patch 5 comments.

Change-Id: If6dd7c4cb802036445cb65853d8de7652df351c0
Signed-off-by: Stone <ronald.stone@windriver.com>
2020-12-21 13:28:54 -05:00

1.3 KiB
Raw Blame History

Configure a Live Migration Completion Timeout in Nova

You can configure how long to allow for a compute live migration to complete before the operation is aborted.

The following example applies a timeout of 300 seconds to all hosts.

The same basic workflow of creating an overrides file, then using it to update helm overrides for the application, and finally reapplying the application to make your changes effective can be used to apply other Nova overrides globally.

  1. Create a yaml configuration file containing the configuration update.

    ~(keystone_admin)]$ cat << EOF > ./nova_override.yaml
conf:
  nova:
    libvirt:
      live_migration_completion_timeout: 300
EOF

  2. Update the Helm overrides using the new configuration file.

    ~(keystone_admin)]$ system helm-override-update --values ./nova_override.yaml -openstack nova openstack --reuse-values

  3. Apply the changes.

    ~(keystone_admin)]$ system application-apply -openstack