Hi David, good question .... I just poked around the APIs a bit. It seems that in vanilla vcloud, a vApp includes the attributes "vappParent" and "children". When a vApp contains more than one VM one of them *must be* designated as the parent; in this case there is a way of getting at individual vms in a multi vm vApp scenario.
However in tMark express vcloud the "vappParent" and "children" attributes don't exist. It seems like the lowest level of granularity is the vApp. This would suggest that tMark are advocating a single VM vApp though this is not explicitly stated (at least there is no obvious way of creating a multi vm vApp or getting at individual VMs in such a scenario), --marios On 05/04/10 23:02, David Lutterkort wrote: > Hi Marios, > > On Thu, 2010-04-01 at 11:57 +0100, Marios Andreou wrote: >> 3. Provisional mapping of vCloud Express entities to d-cloud concepts >> ===================================================================== >> >> 'Instance'<==> 'vAPP' >> >> 'Image'<==> 'vAPP template' >> >> 'Flavor'<==> 'compute options' (and perhaps 'customization options') >> >> 'Realm'<==> 'Organization' OR 'Realm'<==> 'vDC' (probably the latter) > > OVF (in)famously allows bundling multiple VM's together as one 'vApp'. > With the above mapping, would you report the entire vApp back as an > instance or each individual VM as a vApp ? > > It might even be ok to restrict all this to single-VM vApp's, because > for those we know the above mappings won't break any assumptions. > > David > > > _______________________________________________ > deltacloud-devel mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/deltacloud-devel _______________________________________________ deltacloud-devel mailing list [email protected] https://fedorahosted.org/mailman/listinfo/deltacloud-devel
