With out of box functionality, wondering if anyone has a better way to accomplish the following:
- Multiple Provisioning Groups - PGs have access to multiple networks that they should be able to select from a list
- Each PG has dedicated networks - so they cannot provision VM's to other PG's port group (restricted in the reservations)
Only option I'm seeing, is to create the parent / child drop down relationship with the PG being the primary, which I can populate with the provisioning group custom properties, and the child property VirtualMachine.Network0.Name that filters the networks that are available by the PG selected. Issue is if a user selects a different provisioning group, and then selects a network that isn't part of their reservation (machine build will fail if my memory serves me correct - but hoping to prevent that in the first place).
If there was a way to populate the VirtualMachine.Network0.Name with a value list in some place other than the property dictionary, like for the provisioning group, it would be ideal. Or if I could create the parent/child relationship to the PG the user belongs to (tried this, the dropdown child list requires a parent to be in the format of a drop down list).
Any suggestions on ways to address this cleaner and remove the ability for a user to potentially request an invalid network configuration?