[Feature]: Deploy Holodeck on vCenter as a target using custom VM and Template Folder structure
@dhruv-tyagi-broadcom is already working on this.
Since Jun 22, 2026.
- Dominant language
- HTML
- Stars
- 30
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Description
I'm using a host that's part of a cluster under a vCenter Server. Since this client environment is shared with other projects and Proof of Concepts (PoCs), there's a permission limitation limiting my use to only one host. However, for resource provisioning, I only have one folder that propagates permissions for VM consumption, and I don't have these permissions on the Cluster object.
Use case / Motivation
I'm not sure if there's another way to modify one of the scripts to add the logical path for provisioning, both for nested hosts and the VCF Installer, to a specific folder where my user has permissions to consume VMs. Any ideas?
Proposed solution
No response
Additional context
Documentation talk about Holorouter deployment on vCenter as target, but not specific about consumption of New-Holodeck scripts to customize the target options mentioned above.
"Holodeck 9 supports deployments on both stand-alone ESX hosts as well as vCenter as target. Choose the appropriate tab below to follow the instructions for your specific target to deploy Holorouter."
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.