vCD 10.1 - Misleading storage consumption in OVDC Overview

[paulklassen]

Today I noticed something odd...

When I create a OVDC (Organization Virtual Data Center) and allocate let's say 20GHz CPU, 16GB RAM and 50GB Storage the following will
happen, when I try to create a VM.

In this scenario I want to allocate all OVDC resources to this single VM, so I want this VM to have 20GHz CPU, 16GB RAM and 50GB Storage.
But it won't work, it will always fail and the reason for that is, that vCD claims the VM woul exceed the storage quota.
For some reason I don't know, the allocated RAM consumes the allocates Storage. In this Case I would need at least 66GB Storage if I
want a VM with 16GB RAM and 50GB Storage. Or I have to create a smaller Disk for this VM with the size of 34GB instead of 50 (50GB storage - 16GB RAM = 34GB Free "storage")

So my question is basically: Why does RAM consume the Storage Quota? It makes no sense to me, could someone please explain this?
Or is this simply some kind of bug? If yes, how to fix it?

[dcljrick]

Hi paulklassen,

​I have opened a SR ticket for the exact same storage question last week and the answer from the support Team is that it's normal...

Even if you use the Flex allocation model with option "Include VM Memory Overhead" you will face the exact same issue and the support told me that the documentation is confusing...

Documentation : Include VM Memory Overhead -> Include or exclude memory overhead in this VDC. When set to true, you might not be able to use the full capacity of the VDC because the memory overhead of every powered-on VM is also taken from the available capacity of the VDC. When set to false, the memory overhead is taken from the provider VDC and not from the allocated capacity of the VDC.

I am not convinced that it's the way it should funktion, but the Support Team told me to provisions storage + RAM size to my customers... Totally tupid but no other way to go at the moment.

Julien