Ability to specify multiple datastores for deployment

[pauledavey]

Is your feature request related to a problem? Please describe.

When deploying larger environments, it is required to split ESXi host deployments across multiple datastores. This is increasingly important in homelab environments running on non-enterprise grade kit and storage.

Describe the solution you'd like

It would be useful at times to specify different datastores during deployment, e.g specify two datastores for a management only deployment or provision only deployment and allow for weighting of the nested ESXi hosts to be split across these datastores.

Describe alternatives you've considered

Can move VMs after but this is time consuming.

Additional context

No response

[dhruv-tyagi-broadcom]

Thank you for submitting this request and detailing your homelab use case.

While we understand that moving VMs post-deployment can be time-consuming, splitting deployments across multiple datastores with custom weighting would require a significant amount of complex logic to be added to the Holodeck codebase. Because this adds substantial overhead to maintain, and because there are existing workarounds (such as expanding datastore capacity prior to deployment or performing manual vMotions), we won't be implementing this specific feature at this time as we would like to focus on delivering more valuable features by automating other VCF-related tasks through Holodeck.

However, we do see the value in expanding datastore flexibility where it makes sense. To help with similar scenarios, we are going to add support for selecting a different datastore for Site B during a dual-site deployment. We appreciate the feedback!