Merge pull request #48241 from sabrinajess/CNV12562

CNV-12562: New content for configuring live migration policies

Author: sjhala-ccs

_topic_maps/_topic_map.yml

@@ -284,7 +284,7 @@ Topics:
     File: installing-bare-metal-network-customizations
   - Name: Installing a user-provisioned bare metal cluster on a restricted network
     File: installing-restricted-networks-bare-metal
-- Name: Installing on-premise with Assisted Installer 
+- Name: Installing on-premise with Assisted Installer
   Dir: installing_on_prem_assisted
   Distros: openshift-enterprise
   Topics:
@@ -3395,6 +3395,8 @@ Topics:
     File: virt-cancel-vmi-migration
   - Name: Configuring virtual machine eviction strategy
     File: virt-configuring-vmi-eviction-strategy
+  - Name: Configuring live migration policies
+    File: virt-configuring-live-migration-policies
 # Node maintenance mode
 - Name: Node maintenance
   Dir: node_maintenance

modules/virt-configuring-a-live-migration-policy.adoc

@@ -0,0 +1,54 @@
+// Module included in the following assemblies:
+//
+// * virt/live_migration/virt-configuring-live-migration-policies.adoc
+
+
+:_content-type: PROCEDURE
+[id="virt-configuring-a-live-migration-policy_{context}"]
+= Configuring a live migration policy
+
+Use the `MigrationPolicy` custom resource definition (CRD) to define migration policies for one or more groups of selected virtual machine instances (VMIs).
+
+You can specify groups of VMIs by using any combination of the following:
+
+* Virtual machine instance labels such as `size`, `os`, `gpu`, and other VMI labels.
+* Namespace labels such as `priority`, `bandwidth`, `hpc-workload`, and other namespace labels.
+
+For the policy to apply to a specific group of VMIs, all labels on the group of VMIs must match the labels in the policy.
+
+[NOTE]
+====
+If multiple live migration policies apply to a VMI, the policy with the highest number of matching labels takes precedence. If multiple policies meet this criteria, the policies are sorted by lexicographic order of the matching labels keys, and the first one in that order takes precedence.
+====
+
+.Procedure
+
+. Create a `MigrationPolicy` CRD for your specified group of VMIs. The following example YAML configures a group with the labels `hpc-workloads:true`, `xyz-workloads-type: ""`, `workload-type: db`, and `operating-system: ""`:
+
++
+[source,yaml]
+----
+apiVersion: migrations.kubevirt.io/v1alpha1
+kind: MigrationPolicy
+metadata:
+  name: my-awesome-policy
+spec:
+  # Migration Configuration
+  allowAutoConverge: true
+  bandwidthPerMigration: 217Ki
+  completionTimeoutPerGiB: 23
+  allowPostCopy: false
+
+  # Matching to VMIs
+  selectors:
+    namespaceSelector: <1>
+      matchLabels:
+        hpc-workloads: true
+        xyz-workloads-type: ""
+    virtualMachineInstanceSelector: <2>
+      matchLabels:
+        workload-type: db
+        operating-system: ""
+----
+<1> Use `namespaceSelector` to define a group of VMIs by using namespace labels.
+<2> Use `virtualMachineInstanceSelector` to define a group of VMIs by using VMI labels.

virt/live_migration/virt-configuring-live-migration-policies.adoc

@@ -0,0 +1,14 @@
+:_content-type: ASSEMBLY
+[id="virt-configuring-live-migration-policies"]
+= Configuring live migration policies
+include::_attributes/common-attributes.adoc[]
+:context: virt-live-migration
+
+toc::[]
+
+You can define different migration configurations for specified groups of virtual machine instances (VMIs) by using a live migration policy.
+
+:FeatureName: Live migration policy
+include::snippets/technology-preview.adoc[]
+
+include::modules/virt-configuring-a-live-migration-policy.adoc[leveloffset=+1]