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

Add support for datastore cluster storage #9

Open
ghost opened this issue Apr 15, 2021 · 8 comments
Open

Add support for datastore cluster storage #9

ghost opened this issue Apr 15, 2021 · 8 comments

Comments

@ghost
Copy link

ghost commented Apr 15, 2021

This issue was originally opened by @vheon as hashicorp/packer#10004. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.


Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

From the documentation doesn't seems to be possible to have a packer build with the vsphere-iso builder specifying a Storage DRS, only a specific Datastore is allowed. I've tried to set the Storage DRS name as the datastore property but it fails with:

==> vsphere-iso.packer-build-name: error creating vm: datastore 'Storage-DRS-name' not found

Use Case(s)

Usually using the Storage DRS allows to keep the same configuration even if new datastores are added for more storage.

Potential configuration

I'm not sure if new configuration would be required. Packer could first search for Storage DRS and look for a match of the datastore property and if found use it otherwise look for a match of single datastores.

Potential References

https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.resmgmt.doc/GUID-827DBD6D-08B7-4411-9214-9E126671457F.html

@tenthirtyam
Copy link
Collaborator

Recommend updating the context of this issue. The enhancement request is the to support a datastore cluster.

https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.resmgmt.doc/GUID-A2294106-A2B5-4AE4-8F45-9D22B20B5146.html

Ryan

hmalphettes pushed a commit to hmalphettes/packer-plugin-vsphere that referenced this issue May 7, 2022
@tenthirtyam tenthirtyam changed the title Support for vSphere Storage DRS Add support for datastore cluster storage Oct 4, 2022
@FlorianLaunay
Copy link

Hi @tenthirtyam. It may be a fantastic feature! Will it be planned in the next milestone ?

@DonBower
Copy link

This seems like a highly valued feature. Is there an ETA?

@Shackelford-Arden
Copy link

I wanted to note that Terraform currently supports using datastore clusters:

https://registry.terraform.io/providers/hashicorp/vsphere/latest/docs/data-sources/datastore_cluster

Would be nice to be able to follow a similar pattern here in Packer.

@tenthirtyam
Copy link
Collaborator

Labels updated. The scope would need cover each of the builders a post-processors.

@tenthirtyam tenthirtyam modified the milestones: Backlog, On Deck Jul 1, 2024
@tenthirtyam tenthirtyam modified the milestones: v1.5.0, Backlog Sep 4, 2024
@Zheer09
Copy link

Zheer09 commented Sep 23, 2024

This is very essential to have and this might be a blocker for us that we don't have this feature , as we have up coming project we really needed this feature.

We would appreciate if this feature will be available soon in v1.4.1 @tenthirtyam.

@tenthirtyam
Copy link
Collaborator

tenthirtyam commented Sep 23, 2024

Per the milestones, this would be targeted for v1.8.0 minor release based on priorities and available personal time to work on the project.

@Zheer09
Copy link

Zheer09 commented Sep 23, 2024

Appreciated your hard work

@tenthirtyam tenthirtyam modified the milestones: Backlog, v1.8.0 Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants