Is your feature request related to a problem? Please describe?
As of today, vJailBreak doesnot support independent disk migration which are not attached to any VMs. For kubernetes workload migration, it is essential to migrate these volumes.
Detailed Description
As part of our migration from VMWare to PF9, we are facing one issue related to independent volume migration. For Kubernetes cluster in VMWare, we are using CNS Volumes (in VCenter Hypervisor) & Independent Disk (vCloud Director) for kubernetes Persistent Volume requirement. During migration with vJailBreak, it only migrated disks attached to VM and doesnot support above two types of volume migration.
We are requesting for support of above volumes. CNS Volumes/ Independent Disks are VMDK under the hook and expectation is that these volumes should be migrated independently to Openstack Cinder Volumes preserving same volume name as of VMWare one.
Anything else you would like to add?
No response
Is your feature request related to a problem? Please describe?
As of today, vJailBreak doesnot support independent disk migration which are not attached to any VMs. For kubernetes workload migration, it is essential to migrate these volumes.
Detailed Description
As part of our migration from VMWare to PF9, we are facing one issue related to independent volume migration. For Kubernetes cluster in VMWare, we are using CNS Volumes (in VCenter Hypervisor) & Independent Disk (vCloud Director) for kubernetes Persistent Volume requirement. During migration with vJailBreak, it only migrated disks attached to VM and doesnot support above two types of volume migration.
We are requesting for support of above volumes. CNS Volumes/ Independent Disks are VMDK under the hook and expectation is that these volumes should be migrated independently to Openstack Cinder Volumes preserving same volume name as of VMWare one.
Anything else you would like to add?
No response