I know many of you must have not noticed this anomaly in the vCD UI while creating your Org VDC.
So what am I talking about here. Well, we all know that there are three Allocation models in the VMware vCloud Director right? And one of the model is Pay-As-You-Go. This model only charge you based on your actual consumption of the Cloud compute resources.
However, this model does not charge for the vApps (VMs within the
complex rich wrapper) which has been created and lying there without any one using it (Powered Off). So what happens when you create an Org VDC using this mode.
Well, vCD will create a sub resource pool under the main resource pool (Provider VDC RP/Cluster), however it will not carry any reservation or limit there at this time. What is the next step for you?
Yeah, creating vApps (Consuming the Cloud Resource right ?) there on the Org VDC. Now once you create the vApps there, even after those vApps are created, you still not be able to see that the reservation is there on the Org VDC (Resource Committed). Yes that is the expected behavior.
Once you power on the vApps, based on the resource reservation for the vApps in the PAYG Org VDC model, resources will be committed. You should be able to see the VM reservation and Org VDC RP reservation as well.
Hey wait!! What I just described, you know it by heart now right? Yeah, I know that fact. So you might be wondering, what is different am talking here. Hmmm… I know you guys must have created Org VDC 1000 times now. Hey, did you see all of the texts clearly or by heart? I know it may not be true 🙂
When you start creating an Org VDC at the selection of the Allocation model, did you notice the text there in the description field. Let me show you here.
Yes, see this what you see. This says “Resources are committed only when vApps are created in the Organization VDC.” This is not true.
However, there is an interesting catch on the just next screen to it. Select next and you will see this:
Did you see what it says: “Compute resources are committed only when vApps are running in this Org VDC.” This is the correct thing.
So if you ever noticed and wondering what it is and getting confused, please don’t be. The second screen in the PAYG Configuration is showing you the correct thing. It does commit resources only when you power on those vApps in your PAYG model Org VDC.
Let me show you that as well. In my Setup I have a Org VDC which is configured with PAYG allocation. This VDC has 20% resource reserved for vCPU and Memory both. There are three vApps lying there and powered off.
At this stage, if you go to the VDC -> Administration -> Select the VDC -> Resource Pool, you will get to see the child resource pool for this Org VDC. At this stage go to Properties of this RP. You will see Resource Reservation is 0 for vCPU and Memory.
Now, go back to your My Cloud for this Org and power on the vApps. Based on your settings you will see that the resources are now committed to the Org VDC and also in the VMs as well. In the example follows, you can see the resources are committed after I power on 3 vApps there in my Org VDC.
Conclusion: Don’t get confused looking at the Description text there. I am talking to our internal Dev guys to see how we can fix it quickly. I will update this page.