While checking out VMware's vCloud Blogs, I came across a great article that explains how Fast Provisioning works in vCloud Director 1.5.
Outside of a lab/test/dev environment I still don't see the value in linked clones for servers but it is a great technology if it is used in the right circumstances.
This is the first part of two posts that I plan to do on linked clones. A linked clone is a duplicate of a virtual machine that uses the same base disk as the original, with a chain of delta disks to track the differences between the original and the clone.
Linked clones have been in vSphere for some time now, but since they are not a feature that can be created, configured or deployed from the vSphere client or ESXi CLI, they do not get a great deal of exposure.
This first post is related to the new Fast Provisioning feature in vCloud Director 1.5. This new feature uses linked clones. In previous versions on vCloud Director, the adding of a vApp Template (containing 1 or more Virtual Machines) to a cloud was aclone operation. This was quite time consuming depending on the number of VMs in the vApp Template. It also consumed quite a bit of disk space. Fast provisioning saves time & space by using linked clones for virtual machine provisioning operations.
continue to article