9.16. Configuring a dedicated network for live migration
You can configure a dedicated secondary network for live migration. A dedicated network minimizes the effects of network saturation on tenant workloads during live migration.
9.16.1. Configure a dedicated secondary network for live migration 링크 복사링크가 클립보드에 복사되었습니다!
Configure a dedicated secondary network for live migration to minimize the effects of network saturation on tenant workloads during live migration.
Prerequisites
-
You installed the OpenShift CLI (
oc). -
You logged in to the cluster as a user with the
cluster-adminrole. - Each node has at least two Network Interface Cards (NICs).
- The NICs for live migration are connected to the same VLAN.
- You have configured a Linux bridge network.
Procedure
Create a
NetworkAttachmentDefinitionmanifest according to the following example:apiVersion: "k8s.cni.cncf.io/v1" kind: NetworkAttachmentDefinition metadata: name: my-secondary-network namespace: openshift-cnv spec: config: '{ "cniVersion": "0.3.1", "name": "migration-bridge", "type": "macvlan", "master": "eth1", "mode": "bridge", "ipam": { "type": "whereabouts", "range": "10.200.5.0/24" } }'-
metadata.name: Defines the name of theNetworkAttachmentDefinitionobject. -
config.master: Defines the name of the NIC to be used for live migration. -
config.type: Defines the name of the CNI plugin that provides the network for theNetworkAttachmentDefinition. -
config.range: Defines an IP address range for the secondary network. This range must not overlap the IP addresses of the main network.
-
Open the
HyperConvergedCR in your default editor by running the following command:$ oc edit hco kubevirt-hyperconverged -n openshift-cnvAdd the name of the
NetworkAttachmentDefinitionobject to thespec.virtualization.liveMigrationConfigstanza of theHyperConvergedCR.Example
HyperConvergedmanifest:apiVersion: hco.kubevirt.io/v1 kind: HyperConverged metadata: name: kubevirt-hyperconverged namespace: openshift-cnv spec: virtualization: liveMigrationConfig: completionTimeoutPerGiB: 800 network: <network> parallelMigrationsPerCluster: 5 parallelOutboundMigrationsPerNode: 2 progressTimeout: 150 # ...-
spec.virtualization.liveMigrationConfig.network: Defines the name of the MultusNetworkAttachmentDefinitionobject to be used for live migrations.
-
-
Save your changes and exit the editor. The
virt-handlerpods restart and connect to the secondary network.
Verification
When the node that the virtual machine runs on is placed into maintenance mode, the VM automatically migrates to another node in the cluster. You can verify that the migration occurred over the secondary network and not the default pod network by checking the target IP address in the virtual machine instance (VMI) metadata.
$ oc get vmi <vmi_name> -o jsonpath='{.status.migrationState.targetNodeAddress}'