This is just to clarify the confusion which no one able to address is up to the mark.....
When we create one vAPP from one vAPP-Template under one Catalog, it also creates one VM.
Once the vAPP is powered on, the VM also have same status & also there will be 2 VMs listed in vCenter Resource Pool with similar configuration/compute resource.
What is the purpose & technical benefit of automatically creating duplicate VMs in vCenter Server (i.e. one for vAPP & another for VM)
Not only listed in vCenter console, it also have the same options & features. So what is the way to distinguish the vAPPs & VMs in vCenter console, which was created by VCD.
And finally the doubt is, why we need to spend duplicate copies of VMs for a single instance. Which takes double of the space for vAPP & corresponding VM.
I believe vAPP should be a logical container which has the same basic operations as a virtual machine, but can contain multiple virtual machines and encapsulate not only virtual machines but also their inter-dependencies and resource allocations allowing for single-step power operations, cloning, deployment, and monitoring of the entire application.
So why there is a need to list the vAPP (created by VCD) as a VM (in vCenter console) by occupying similar storage & computer resource ?