CloudClient and provider-VirtualMachine.Memory.Size

[SeanKohler]

vra catalog request submit --id "Centos6" --groupid "XXXX" --reason "test-reason" --description "test-description" --requestedFor "XXXXX" --properties "provider-LinuxRoleApplication=IT Server (IT),provider-ServerPatchGroup=2.Patch Group 2,provider-VirtualMachine.Memory.Size=8192,provider-VirtualMachine.CPU.Count=2"

-------------------------------

Nothing I do will change the memory.  Minimum is set to 4096 in the blueprint.  No Maximum set.  The machine is always built with 4096 memory size.  CPU changes without issue with no maximum set and a minimum of 1 CPU.

What am I missing?

[SeanKohler]

This is when I just submit it without setting CPU and Memory.

When I submit it setting CPU and memory, the CPU changes to a string type... but the memory stays an integer and stays at 4096 even though 8192 is specified.

[SeanKohler]

I should note that I also tried with a Min and Max set... and then picked a value in the range between the two.  Still to no avail...

[AndManLM]

Try without the provider- prefix; VirtualMachine.Memory.Size=8192

[SeanKohler]

Worked perfectly... thanks!

[SeanKohler]

Hi... in CloudClient 3.4 and 3.4.1 (for vRA 6.2.x), the correct memory key is...

MemoryMb=

e.g. (note, I also show Lease here which is also not intuitive)

vra catalog request submit --id "Centos6" --groupid "XXXX" --reason "test-reason" --description "test-description" --requestedFor "XXXXX" --properties "MemoryMb=8192,VirtualMachine.CPU.Count=2,LeaseDays=30,provider-SomeCustomProperty=someValue"

In the older versions of CC, the prior answer applies.

[reneeckstein]

Hi SeanKohler,

thanks for sharing! I searched for a solution for this issue for months..

Regards,

René