Goal

Ensure the multi requested chassis feature can be used on an IC cluster.

We want to use this for KubeVirt VM live-migrations. 

KubeVirt VMs run in a Kubernetes pod, thus, we are planning on doing something like:

(assuming the VM is scheduled in nodeA and will be migrated to nodeB)

t=0: (only src pod exists) requested-chassis = nodeA
t=X: (mid migration; src and dst pod exist) requested-chassis = nodeA,nodeB
t=y: (migration has ended; only dst pod exists) requested-chassis = nodeB

Scope of this issue

• Make sure that the requested-chassis parameter can handle migrations in environments where nodes are connected to different logical switches.
• Test that multiple-chassis and the activation-strategy work effectively for transit switches in OVN Kubernetes.
• If there are issues, create Jira tickets.

The issue only involves testing migration from one node to another when the pod or VM is directly attached to a transit switch.

Notes

• Utilize requested-chassis parameter
• Ask Ales Musil for assistance
• Even though OVN should provide support for seamless live-migration, there may be issues: https://bugzilla.redhat.com/show_bug.cgi?id=1903653
• This is already done in Neutron and Kube OVN. See the presentation from KubeVirt Summit 2024

Done Checklist