Add Tempest scenario to validate NIC teaming

[Ihar Hrachyshka]

The following scenario is used in production environments to simulate hardware NIC teaming.

1. Create VM1 with port=IP1/MAC1, port2=IP2/MAC2. Disable port security for port2.
2. Create VM2 with port=IP3/MAC3.
3. Boot the two VMs.
4. For VM1, change the IP and MAC for port2 to IP1/MAC1 (using ip link / ip addr inside the VM).
5. Validate that packets directed to IP1/MAC1 are delivered to both VM ports.
6. Validate that packets sent by VM1 through port2 using IP1/MAC1 are delivered to VM2.

This scenario allows users to run a NIC teaming software inside the VMs that would - once a failure is detected on one of the links - take over IP1/MAC1 pair in master/slave fashion.

For reference, context on how NIC teaming is configured and used in RHEL: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/configuring-network-teaming_configuring-and-managing-networking

[Brian Haley (brian-haley)]

So I have a question since we've played with bonding inside a VM and it's not always straightforward to get it working properly. Is this also using the bonding or team driver inside the VM with both of the ports?

Or maybe your patch to Tempest will make that obvious :)

[Ihar Hrachyshka (ihar-hrachyshka)]

To validate the scenario end-to-end, yes, you would need to deploy a service to manage the bond (teamd?)

That said, tempest scenario could mimic the behavior as per steps 1-6 without running a teaming service inside the VM.

---

btw I don't have capacity to write the scenario right now, sorry. I put it here for in case someone would like to take it. Consider it a backlog item for a feature that is used in the wild but that has no test coverage in upstream.