Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support For DataStoreClusters #94

Open
tonyturino opened this issue Oct 20, 2016 · 4 comments
Open

Support For DataStoreClusters #94

tonyturino opened this issue Oct 20, 2016 · 4 comments

Comments

@tonyturino
Copy link

Is there support for DataStoreClusters? Using DataStores only eliminates a lot of functionality and flexibility that is built into vSphere.

@bradwilliamson
Copy link

bradwilliamson commented Dec 28, 2016

I am looking into this. It appears in the vSphere API RecommendDatastores() and ApplyStorageDrsRecommendation_Task() will accomplish this. The API refers to datastore clusters as "Storage Pods". When you specify a method (create, clone, relocation, reconfigure) for the CloneVM_Task(). The method generates a recommendation on where to place the VM which is the same thing you see in the vSphere client. To perform actually provisioning/cloning of the VM it has to call the ApplyStorageDrsRecommendation_Task() which will then accept the recommendation ID. I believe the RecommendDatastores() will return multiple recommendations in an array. The first one is the best choice.

@Brunzer
Copy link

Brunzer commented Jun 19, 2017

@bradwilliamson Has there been any further progress on this? It would be greatly beneficial to get support for using datastore clusters rather than having to explicitly assign to a specific datastore.

@jjasghar
Copy link
Contributor

@Brunzer we have moved development over to https://github.com/chef-partners/chef-provisioning-vsphere and we are doing our best to maintain it now.

Can you put in an issue there to track this? Use case and maybe we can get some more eyes on.

@Brunzer
Copy link

Brunzer commented Jun 19, 2017

thanks @jjasghar. I saw that there's already an issue open in that repo for this as well. I just commented on it to reference this one as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants