initial work to reconcile devices from launcher pods

[ibrokethecloud]

IMPORTANT: Please do not create a Pull Request without creating an issue first.

Problem:

Rancher allows provisioning of downstream clusters to leverage vGPUs.

When used with a machine deployment of more than 1 node, the actual gpu allocated is different from name specified since kubevirt leverages the DeviceName field to calculate launcher pod resource requirements, which are then subsequently used by schedular to identify correct nodes.

Since the actual name is not really used for device allocation, any random string can be used and this makes it difficult to track vGPU allocation in the cluster.

Solution:

PR introduces a minor change to leverage pod environment variables being set by the device plugin during the ContainerAllocateResponse. The additional vmi controller execs into the launcher pod to identify the ID set for resource, and subsequently map it to the GPU/Hostdevice resources. Once the devices are identify an annotation is set on the VM to provide info about actual device from a pool of devices passed through to the VM

For example for a host device this looks as follows:

harvesterhci.io/deviceAllocationDetails: '{"hostdevices":{"intel.com/8d26":["vgpu-01-0000001d0"]}}'

For GPU devices ithis looks as follows:

  harvesterhci.io/deviceAllocationDetails: '{"gpus":{"nvidia.com/NVIDIA_A2-2Q":["vgpu-01-000008005"]}}'

When a VM is shutdown the annotation is used to replace name for vGPU or host devices with actual device names from the deviceAllocationDetails annotation. This ensures that the VM can be edited and devices can be removed from Harvester UI post provisioning.

Related Issue:

Test plan:

[ibrokethecloud]

backend changes related to: rancher/dashboard#11399

[Yu-Jack]

LGTM, and just a reminder. We need to raise a chart PR for updating the service account permission to allow that pcidevices-controller can list/update virtualmachines and list virtualmachineinstances.