vRA 8.1, Orchestrator Workflow

This post was originally published on this site

We want to avoid the “t-shirt style” configuration for host cpu/memory.


I am attempting to prompt users in the catalog before provisioning for cpuCount and totalMemoryMB values and then set those in the customProperties so that they are used when the host is built. I’ve attempted to apply these changes pre-compute allocation but it doesn’t seem to work.  After the host is provisioned the memory is set to default (1/2048) instead of what was set. Logs show the value is set in customProperties (output).


Can someone recommend a different direction to approach this that will work?

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.