This is the third post in my series on Hands-on Labs behind the scenes. You can find the previous post on comparing cloud catalogs here.
To date, my biggest problem with synchronizing data between vCD instances has been the time required to export vApp templates from one cloud and import them into another. If you want to preserve vApp structure and (most) metadata, there is really only one way into or out of a vCD cloud. Simply having the VMDKs and VMX file from the backend vSphere is not enough. For those who have had to deal with these mechanisms on a regular basis, you know what I mean.
A vPod containing our base infrastructure for VMworld 2013 development looked something like the following. Most of our final vPods are quite a bit larger than this, but this is a pretty standard starting point.
|Single Site Base vPod|
|VM Name||vCPU||vRAM (GB)||Disk (GB)|