vRealize Orchestrator (vRO/vCO) and vCloud Director – fixing bugs in "Add a vDC"
When you are using a VMware orchestration platform with an official VMware plugin to manage a VMware product, you don’t really expect to have to fix the out-of-the-box workflows. However, during some testing of some workflows with a client the other day we ran into a couple of issues with the vCloud Director plugin workflows.
Software versions used
- vCloud Director 5.5.1 (appliance for development) and 5.5.2 (production deployment)
- vRealize Orchestrator Appliance 22.214.171.124
- vCloud Director plugin 126.96.36.199
CPU allocations are incorrect for both "Add a VDC"
When you provide the CPU allocation model properties for the Allocation Pool model the first problem is decrypting the naming – it doesn’t match the names in the vCloud Director interface!
The "CPU (GHz)" value is the vCPU speed, and the "CPU Quota (GHz)" value is the CPU allocation