Hello,
When configuring the pVDC, we are unable to see datastore behind a datastore cluster (with or without SDRS).
But if we move the datastore out of the datastore cluster, we can see it throught the SP.
All datasore used tags for matching the SP, and each SP have SIOC configured for max IOPS by vmdk.
vCD 9.7 is normally compatible with datastore cluster ? Or i missed something.
Best regards
Datastore clustering is supported in 9.7 . Were are you assigning the tags ? At Datastore cluster level or individual datastores ?
Hi,
Tags are assigned directly on datastore. But the issue is solved , first i have added the sp with datastore out of datastore cluster then after i could see all the remaing sp with datastore behind datastore cluster.
I don't have explanation how it works since this workaround. but all things are good now.
Best regards
I'm going to open a SR to ask for an official stance on this but in the meantime...
Did we get to the bottom of this? In the past (i.e. vCD 8.x) we tagged both datastores and datastore clusters and we could see both in vCD - happy days.
Now, I'm using vCD 9.7 and when creating a new Provider VDC under the Add Storage window, I can only see storage policies that correspond to datastores that are NOT in any datastore cluster. It doesn't see any datastores that are part of a datastore cluster - exactly what the OP mentions.
The other question is around SDRS settings and whether they are compatible with vCD. For example, assuming we have a number of datastores in a datastore cluster:
Hi,
I got the same error at the beginning ==> Now, I'm using vCD 9.7 and when creating a new Provider VDC under the Add Storage window, I can only see storage policies that correspond to datastores that are NOT in any datastore cluster. It doesn't see any datastores that are part of a datastore cluster - exactly what the OP mentions.
==> I managed the error by adding a single datastore (not behind a cluster datastore) then only after i could see the other SP with datastore behing datastore cluster.
Did you solved your issue ? How ?
Nope, no fix for this, just the workaround which you mentioned.
Unfortunately VMware weren't particularly helpful in qualifying what operations are "safe" to do in vCenter that won't conflict with anything in vCD. It would be helpful to have an official KB article of what is safe and what is not safe to do. They wanted me to list all the things I wanted to do so they could qualify it but I don't really have time to test things for VMware so I pointed them to this post.