Nested vApps in vcloud director

[RanjnaAggarwal]

Is it possible to create nested vapps in vcloud director?

[Sreec]

Not Possible. May i know the use case?

[cfor]

Not directly possible.  But would be good to know the use case.

What I have seen done a bunch is a single vApp with several networks.  Then the systems in the vApp attached to the different networks (and VMs named sometimes with and ID).  This sort of gets the job done in some cases.  (But they do have to be on the same org vdc and that can sometimes limit options.

Example:

Need to show 3 sites in a testing lab vApp.

sitea-web : networkA

sitea-db : networkA

sitea-services : networkA

siteb-web : networkB

siteb-db : networkB

siteb-services : networkB

sitec-web : networkC

sitec-db : networkC

sitec-services : networkC

[RanjnaAggarwal]

One of my client has given the use case and that is:-

He said they are using nested vapp concept at vsphere level as given in the screenshot attached here

They are using this not only for Poweron or Poweroff but also for taking backup of particular type of vApp VMs only. This is what he is expecting in vCloud director vApp.

[IamTHEvilONE · Accepted solution]

Nesting vapps won't happen in vCD.  They will be parallel vApps.  This isn't stopping you from writing an automation tool/website which would show what you have there.

vRA will eventually address this, but they don't use vApps.  all the VMs just become machines to be managed without the concept of being part of a vApp.  it'll be that you have a multi-machine blueprint that uses two other multi-machine blueprints (one DB tier, on App tier).

[admin]

Multi machine blueprint can be added into single machine blueprint, In a multi machine blue print another multi machine blue print cannot be added. Correct me if I am wrong.

[RanjnaAggarwal]

Single Machine Blueprnt can be added in to multimachine blueprint but multimachine can not be even added to single machine blueprint,

[IamTHEvilONE]

In vRA 7, there is just blueprints ... none of this single vs multi naming convention.

See: http://www.vladan.fr/vrealize-automation-7-announced/

"It’s possible to built a nested blueprints! Let’s say you build a blueprint. Save it, make it available, and then consume this blueprint into the canvas to use it."

It's pretty useful for the service definition of making building block components from different Blueprints.