Up until recently we've had a very simple tagging strategy and all Test went to cluster Test1 and Prod went to cluster Prod2, etc. This was all done via tags on the compute clusters and constraints in the blueprints. We have multiple Test and Prod clusters, but we intentionally directed all our vRA provisioning to just 1 cluster for each environment.
We're trying to understand how vRA would handle spreading that provisioned workload to multiple clusters from a single blueprint. Assuming we tagged all of the Test clusters with the same tag would vRA round-robin them or does it just use the first cluster that meets it's constraints? I couldn't find any info in VMware's docs about what happens when multiple clusters match the constraints. Thanks for any info,
Mike
Hi, mastefani. I guess that vRA places the vms in the first resource that matches the constrains. You can change this behavior.
Please look at the "Placement Policy" in the Provisioning tab of the Project.
And then you can use the "test" button in the Template to see where it would be placed
Hi, mastefani. I guess that vRA places the vms in the first resource that matches the constrains. You can change this behavior.
Please look at the "Placement Policy" in the Provisioning tab of the Project.
And then you can use the "test" button in the Template to see where it would be placed
Perfect, I remember seeing that when I first built out our cloud zones and honestly just kind of forgot about it. Thanks for pointing that out!