starlingx/docs
Code Issues Proposed changes
a18b20c7fd
docs/doc/source/system_configuration/openstack/configuring-a-live-migration-completion-timeout-in-nova.rst
Juanita-Balaraj b0c38784b5 Added --reuse-values to the "system helm-override-update" command 
Updated Patchset 1 comments
Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
Change-Id: I75253277515425e9b933686635a62e3f63141e93
Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
2021-07-21 19:46:45 -04:00

1.6 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 --reuse-values --values ./nova_override.yaml -openstack nova openstack --reuse-values

  3. Confirm that the user_override lists the correct live migration completion timeout.

    ~(keystone_admin)$ system helm-override-show -openstack nova openstack

    The output should include the following:

    live_migration_completion_timeout: 300

  4. Apply the changes.

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