Exclude VMs from Fast Provisioning

[Gabrie1]

Hi

Customer uses our vCloud Director environment for their Develop and Acceptance testing. Because they deploy a template vApp multiple times and only change a little data, they're using Fast Provisioning and saving a lot of storage. But..... (there always is a but...) they also have a few VMs of 2.6TB each. When these are deployed on our 5TB datastores, they'll fill the datastore pretty fast. There is an app on them that does have a high change rate. What I'm now looking for is a way to NOT fast provision them, which will force vCloud Director to use a different datastore if it doesn't fit.

Question:

- When looking at the options, it seems that the only way I can do this, is by creating a different Org VDC. Is that correct?

- Is there a way to mix VMs from different Org VDC's in one vApp?

- Any other tips?

Gabrie

[TomasFojta]

If you resize VM's disk during its provisioning from the catalog you will get a full clone instead of a linked clone.

[Gabrie1]

That would indeed be an option, but will vCloud Director then move the VM to a new datastore?

Supose the following on a 5TB datastore I have a VM in a catalog which is 3TB in size. A fast provisioned clone is then made which will start at 100GB. The VM will suddenly want to grow to its max size of 3TB but will of course stop when the 5TB datastore runs full. vCloud Director won't move the VM away without SDRS.

Resizing can only be done when deploying a single VM and that VM can not be added to a vApp. Strangely enough when you add a VM to an existing vApp, you don't get the resize option.