[Doc] VM Migration policy and status

[bk201]

Is your doc request related to a problem? Please describe or add related issue ID.

Migration policy

To have a document or KB article to explain the VM Migration policy. Including how they work and cons/pros.

https://kubevirt.io/user-guide/operations/live_migration/#understanding-different-migration-strategies

And also includes how to set it in a running cluster:

• globally
• group-wise

Related issue: #4375

Migration status

A doc or KB article to explain how to see a running migration state at this moment. This is done via watching the dom job in virt-launcher pod:

• Find VM's virt-launcher pod.
• Exec bash in the pod.
• Dump the job info

  virsh domjobinfo 1
  

Related issue: #4352

Describe the solution you'd like

[harvesterhci-io-github-bot]

Pre Ready-For-Testing Checklist

• If labeled: require/HEP Has the Harvester Enhancement Proposal PR submitted?
  The HEP PR is at:

• Where is the reproduce steps/test steps documented?
  The reproduce steps/test steps are at:

• Is there a workaround for the issue? If so, where is it documented?
  The workaround is at:

• Have the backend code been merged (harvester, harvester-installer, etc) (including backport-needed/*)?
  The PR is at:

  • Does the PR include the explanation for the fix or the feature?

  • Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?
    The PR for the YAML change is at:
    The PR for the chart change is at:

• If labeled: area/ui Has the UI issue filed or ready to be merged?
  The UI issue/PR is at:

• If labeled: require/doc, require/knowledge-base Has the necessary document PR submitted or merged?
  The documentation/KB PR is at: Add kb of vm live migration policy and configuration harvesterhci.io#42

• If NOT labeled: not-require/test-plan Has the e2e test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue?

  • The automation skeleton PR is at:
  • The automation test case PR is at:

• If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
  The compatibility issue is filed at:

[harvesterhci-io-github-bot]

Automation e2e test issue: harvester/tests#930

[bk201]

Doc is published: https://harvesterhci.io/kb/vm_live_migration_policy_and_configuration