OVA: support for configuring ovfenv

[arturshadnik]

Right now, forklift does not offer any mechanism for configuring an ovfenv during migrations using OVA provider. Some OVAs require an env to be configured in order to function properly. Adding support for this will involve several steps:

• Extend OVA provider server and inventory server to return relevant parts of the OVF template parsed here. The section which includes relevant data is Envelope.VirtualSystem.ProductSection https://pkg.go.dev/github.com/vmware/[email protected]/ovf#ProductSection. This will allow the user to see which Properties are required and need to be configured before the migration. Draft PR here: feat: add ova ProductSection to ova provider server resp #1204

• Extend Plan CR with a new optional field Plan.Spec.VM.OvaEnvConfigMap, a reference to a ConfigMap in the target namespace. The ConfigMap can be attached as a disk to the KubeVirt VM, per instructions here. The ConfigMap will contain ovfenv.xml. It can then be mounted inside the running VM to make the ovfenv accessible.

• Include a vmtoolsd-shim binary to a) mount the disk to the VM and b) make the env available to the VM/application. For the shim, I will provide source code, but the way its implemented is open. One options is to release it as a separate binary that users can download as needed, for example using a custom virt-customize script. Another option could be to include it in the virt-v2v image and copy it into the guest OS during conversion. Open to suggestions.

With these 3 components, users will have what they need to be able to determine which env parameters need to be set, configure them, and make them available once the VM is running.

[mnecas]

Extend Plan CR with a new optional field Plan.Spec.VM.OvaEnvConfigMap, a reference to a ConfigMap in the target namespace. The ConfigMap can be attached as a disk to the KubeVirt VM, per instructions here. The ConfigMap will contain ovfenv.xml. It can then be mounted inside the running VM to make the ovfenv accessible.

If there will be any changes to the CRD, I'll be required to create a design doc describing the changes.
Generally would like to have the design doc for any large changes. For example: #1213

[mnecas]

Include a vmtoolsd-shim binary to a) mount the disk to the VM and b) make the env available to the VM/application. For the shim, I will provide source code, but the way its implemented is open. One options is to release it as a separate binary that users can download as needed, for example using a custom virt-customize script. Another option could be to include it in the virt-v2v image and copy it into the guest OS during conversion. Open to suggestions.

What would the purpose of the vmtoolsd-shim?

[arturshadnik]

Please see the design doc here #1226