Hi Sergio, you may have a look at vcloud.py on our branch at mist.io, at https://github.com/mistio/libcloud/tree/mistio We follow a similar approach, list_nodes for example returns nodes for all vApps, and thus you can run actions on the VMs more easily. Btw this uses multiprocessing to query vapps on parallel and is quicker than asking all vApps serially.
We also have been thinking how these changes could be pushed upstream to libcloud. Hope you will find something useful there Cheers, Markos On Mon, Feb 16, 2015 at 12:10 PM, Sergio Rua <[email protected]> wrote: > Hi all, > > I've started a project at my company on my spare time to automate builds > in our vCloud provider. I started using libcloud for this but I finding the > library to be quite limited. My biggest problem with the vCloud driver is > that it seems to be wholly oriented to manage and orchestrate vApps when I > would like it to do the same for VMs instead and use the vApps just a > containers for the virtual machines. For example, I have a vApp with 10 > virtual machines. There is no function in libcloud that would allow me to > power off on of the VMs; I would have to power off the whole vApp. > > I know some people ignore the vApps model completely and make it one vapp > equals one vm but this just doesn't work for me. > > I've initially started creating my own module extending > VCloud_1_5_NodeDriver but I'm wondering if the changes I'm making could be > of interest to the project. I don't have much time and my own needs will > take precedence into any work I can contribute but I'm happy to do so. > > Thank you > Sergio Rua > > ______________________________________________________________ > learndirect Limited > Registered in England No. 3980770 > Registered Office: Dearing House, 1 Young Street, Sheffield, S1 4UP > > ______________________________________________________________ >
