Unfortunately, I'm not able to add vSAN storage policies to the existing PVDC (it's not choosable). It's probably because the old cluster does not have access to vsan storage (and its storage policy). Provider VDC "compute" is added by resource pool.
I'll try to explain my situation more to give more clues:
- one vCenter with 2 clusters
1. old cluster with traditional iscsi storage from the disc array
2. new vSAN cluster
- so neither compute nor storage is shared
- VMotion network and VM networks are shared.
- for workload outside of vCloud Director I'm able to do cross-cluster vmotion (Migrate -> Change both compute resource and storage) and everything works perfectly.
vCloud Director situation:
1. Old cluster is added with its resource pool as Provider VDC, with its datastores (and base on that also with its storage policies).
2. New cluster is also added with its dedicated resource pool as another Provider VDC
- Each cluster has its own DVS and portgroups (external networks in vCD)
Seems like there is no way to trigger the "Change both compute resource and storage" operation from vcloud director
- I'm trying to move VM to the new vApp within the same organization (old vapp in old Organization VDC - added to org from old Provider VDC , new empty vApp in new Organization VDC - added from new Provider VDC), but it doesn't work online. I'm able to move VM like that only when it's powered off. This only works online when its shared compute - So I'm able to online migrate VMs between storage policies (=datastores), but only when i got shared compute, which I don't have in this case
Thank you for your answers 🙂
