A few questions about maintaining volumes with this driver

[jwbennet]

My group has been setting this up to try it out and another group which runs our vSphere instance has a few questions which I could use some help answering:

1. Can we use thick provisioning for the disks instead of thin?
2. Can you point the driver to a datastore cluster or multiple data stores?
3. If one of our datastores starts to reach its capacity our standard practice is to use vmotion to rebalance some disks from one datastore to another which causes them to be renamed. Would this cause issues?
4. Can you expand disks after their initial creation? If not is there a recommended practice to handle that?

If you have any insight into these questions I would greatly appreciate it!

[jm66]

Hi @jwbennet

1. Technically you can, however, this is not configurable. You just have to edit the driver file and change a few lines.
2. As far as I know, Datastore clusters are not supported currently.
3. Yes, since a fixed datastore is configured.
4. Not sure how to address this. cc @pratikvgupta, @wallnerryan

Hope it helps.
JM

[jwbennet]

Hello @jm66,

Thanks for your feedback! I think one of our biggest sticking points is we would like to use a datastore cluster for this instead of a single datastore. If anyone has thoughts of what it might take to implement I'd be happy to submit a PR.

Thanks,
James

[jm66]

I believe via the vSphere API implementing storageResourceManager but we'll have to do some testing.