libcloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Wright <>
Subject Re: [libcloud] Virtualbox driver for libcloud?
Date Wed, 03 Mar 2010 02:56:59 GMT
The VirtualBox Python API is really straightforward. There are bindings for
both the local COM/XPCOM interface, and the SOAP interface. I created
VBoxWeb ( a while back using the Python
API (My version of VBoxWeb is no longer maintained, having
been superseded by the official project of the same name (

The documentation for the API is bundled with the SDK. (

If this is something the libcloud community thinks should be added, I'd be
happy to contribute.


On Tue, Mar 2, 2010 at 6:59 PM, Paul Querna <> wrote:

> On Tue, Mar 2, 2010 at 3:22 PM, Ian Bicking <> wrote:
> > I'm thinking about making a driver for libcloud for creating Virtualbox
> > images.  My use case is primarily to be able to run local tests, and
> maybe
> > secondarily to create developer-ready images.  I'm curious if anyone has
> > considered this general idea, or even has code?  Even a shell script
> would
> > be handy, as I've never done automated virtualization in the past and
> > there's a slightly annoyingly large set of options to sort through.
> >
> > I'm not sure to what degree I should make these into pretend cloud
> servers,
> > and how I should just expose the underlying virtualizing.  There aren't
> > discrete sizes, for instance (though some concepts like node names work
> > fine).  Lastly, the question of where this code should actually go
> > (libcloud, or develop it separately for now).  The way driver
> instantiation
> > works it's not that easy to do separate development, unless I have code
> to
> > just skip libcloud's instantiation system (not hard to do, just feels
> > awkward).
> I think it would be a cool thing to include in libcloud, as I am
> getting tired of booting and killing dozens of  servers every day :)
> I was looking for docs on their API, various blog posts mention some
> kind of SOAP API, but I can't seem to find any info on it.
> Their `VBoxManage` command could easily be wrapped though, to provide
> a simple list/create/destroy/etc:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message