Feature-request: Imported VMs should be made part of VNets and be assigned network leases
|Category:||Core & System|
As an OpenNebula administrator, I would like to be able to:
select which VNets and leases should be assigned to the VIFs of an imported VM.
This facilitates the adoption of OpenNebula on an existing infrastructure, where it shares space and resources with non OpenNebula-managed VMs, particularly the same network space.
It is hard to figure out the network configuration of a machine from the hypervisor, so the easiest would be that the user is able to provide VNet ID and lease for each interface in the Wild VM during "onehost importvm".