This months vCloud Digest is a bit of a bumper edition – we have been so busy with other work and the run up to VMworld it had to be put on the back burner – meanwhile I moved house, and we all know how that can set you back. We had LOADS of content – and in effort to catch-up I’ve dispensed with my usual “backstory” and screen grabs to illustrate the question. Normal service will be resumed with the next digest. The other news is… I’ve discovered we have similar digest for EUC issues. So I’m hoping to do the same for EUC technologies as well.
Once again we are indebted to our esteemed colleagues throughout the company for providing this content including:
Tomas Fojta, Massimo Re Ferre, William Lam, Michael Haines, Ian Hamblen, Taruna Gandhi, Sean Howard, Christian Prediger, Ray Budavari, Keith Luck, Kim Ranyard, Rich Bourdeau, Evan Bills, Jonathan Hemming, Kyle Smith, : Sanjay Patnaik, Timo Sugliani, Zack Kielich, Tom O’Rourke
vCloud 5.1.2 Allocation Pool Options During Upgrade
Q. What does the following mean in the vCD 5.1.2 release notes?
“Allocation pool organization virtual datacenters can be elastic or non-elastic: Starting with vCloud Director 5.1.2, system administrators can configure Allocation Pool organization virtual datacenters with Single Cluster Allocation Pool (SCAP), making them non-elastic. This is a global setting that affects all Allocation Pool organization virtual datacenters. By default, Allocation Pool organization virtual datacenters have Single Cluster Allocation Pool enabled. Systems upgraded from vCloud Director 5.1 that have Allocation Pool organization virtual dataceters with virtual machines spanning multiple resource pools have Single Cluster Allocation Pool disabled by default.
To change the Single Cluster Allocation Pool setting go to System > Administration > General > Miscellaneous. Before enabling Single Cluster Allocation Pool, migrate any virtual machines on secondary resource pools to the organization virtual datacenter’s primary resource pool.”
A. Essentially vCD 5.1.2 allows you to choose between the vCD 1.5 allocation model and the vCD 5.1.1 allocation model.
With an Upgrade from 1.5:
1) Admin upgrades VCD to 5.1.x. The Single Cluster Allocation Pool (SCAP) flag is turned on by default and all existing Allocation Pool Org VDCs are in SCAP mode (non-elastic).
2) All new Org VDCs subsequently created on all PVDCs will be restricted to a single cluster and never span clusters.
3) The semantics of new/existing Org VDCs in single cluster mode will be exactly the same as 1.5 allocation pool and non-elastic.
4) Post upgrade, cloud admin should be able to set the global SCAP flag OFF at any time to convert all his Org VDCs to elastic.
5) Once the SCAP flag is OFF, all the newly created allocation pool Org VDCs are elastic after that.
Upgrade from 5.1 – Case 1, you have some Org VDCs that already have VMs in more than one cluster.
Post upgrade, the default mode of VCD will be elastic (same as 5.1) and all allocation pool Org VDCs continue to remain elastic. The SCAP flag is turned OFF by default. If an admin tries to turn the SCAP flag ON at this time, he will receive an error message that he needs to first manually migrate his VMs in single cluster for all Org VDCs that have VMs spanning clusters. The admin then manually migrates VMs belonging to elastic AP Org VDCs to a single cluster. This means that admin can now turn SCAP flag ON. All the elastic allocation pool Org VDCs are now in single cluster mode. All subsequently created allocation pool Org VDCs are now in single cluster mode.
With an Upgrade from 5.1:
Even though allocation pool Org VDCs are elastic, none of the allocation pool Org VDCs are spanning clusters. This is same as upgrade from 1.5.
With an Upgrade from 5.1.1:
Same as upgrade from 5.1.0. So if you did not have any Org VDC spanning multiple clusters it would revert to vCD 1.5 non elastic setting. Otherwise it will remain elastic (no change).