Add the ability to un/plug vnetX devices to anvil-manage-server-system.

[digimer]

This is a frequently used task with a lot of our users, we need to add support for it to the UI. Once the back-end is done, hand over to @ylei-tsubame for UI integration.

[digimer]

The back-end is ready for testing.

[digimer]

Confirmed manually to be working.

[digimer]

For the tests, call anvil-manage-server-network --server <server_uuid> --mac 52:54:00:aa:bb:cc --unplug and then wait for the output from virsh dumpxml <server_name> to show:

    <interface type='bridge'>
      <mac address='52:54:00:aa:bb:cc'/>
      <source bridge='ifn1_bridge1'/>
      <target dev='vnet1'/>
      <model type='virtio'/>
      <link state='down'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>

Key is <link state='down'/>. Then call again with --plug and wait for that to either change to <link state='up'/> or for the link state element to disappear.

[fabbione]

bouncing back to devel. The tool only works on the node where the VM is running.

[root@an-striker01 ~]# anvil-manage-server-network --server an-test-deploy1 --mac 52:54:00:c2:cc:1a --unplug
Asked to unplug an interface from: [an-test-deploy1] but there was a problem parsing the definition file. More details are likely in the logs.
[root@an-striker01 ~]#
logout
Connection to an-striker01 closed.
[root@an-phy01 ~]# ssh an-a01n01
Last login: Wed Dec 25 06:32:54 2024 from 192.168.122.1
[root@an-a01n01 ~]# anvil-manage-server-network --server an-test-deploy1 --mac 52:54:00:c2:cc:1a --unplug
About to unplug the interface: [vnet0] -> [52:54:00:c2:cc:1a] -> [an-test-deploy1].
Successfully unplugged the interface: [vnet0] -> [52:54:00:c2:cc:1a] -> [an-test-deploy1].
Done!
[root@an-a01n01 ~]# anvil-manage-server-network --server an-test-deploy1 --mac 52:54:00:c2:cc:1a --plug
About to plug in the interface: [vnet0] -> [52:54:00:c2:cc:1a] -> [an-test-deploy1].
Successfully plugged in the interface: [vnet0] -> [52:54:00:c2:cc:1a] -> [an-test-deploy1].
Done!
[root@an-a01n01 ~]#

[fabbione]

just to clarify, most tools are able to operate on a server as long as they are executed on one of the nodes. I don´t expect all tools to work from striker, but proper errors need to be displayed across. There is a major inconsistency here that makes writing tests rather challenging, as a consequence also admin an anvil can become complex.