Return-Path: Delivered-To: apmail-incubator-libcloud-archive@minotaur.apache.org Received: (qmail 75388 invoked from network); 3 Mar 2010 02:57:36 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 Mar 2010 02:57:36 -0000 Received: (qmail 96480 invoked by uid 500); 3 Mar 2010 02:57:31 -0000 Delivered-To: apmail-incubator-libcloud-archive@incubator.apache.org Received: (qmail 96447 invoked by uid 500); 3 Mar 2010 02:57:31 -0000 Mailing-List: contact libcloud-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: libcloud@incubator.apache.org Delivered-To: mailing list libcloud@incubator.apache.org Received: (qmail 96439 invoked by uid 99); 3 Mar 2010 02:57:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Mar 2010 02:57:31 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jshwright@gmail.com designates 74.125.78.149 as permitted sender) Received: from [74.125.78.149] (HELO ey-out-1920.google.com) (74.125.78.149) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Mar 2010 02:57:20 +0000 Received: by ey-out-1920.google.com with SMTP id 4so160570eyg.8 for ; Tue, 02 Mar 2010 18:56:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=PHT8SUoS4SAgWhrCDevJ/Ec/zkHfV/7xFisycwHiIoc=; b=U39Ed6IGgTAi4y4WiO1ZnGEIlw+9jLdXdxiWarSIYq1A6JSQf7gk1s5tboBBMaPjqM 9UbRbgKmLypD4BVNiByRtsjnzfRsu9z5AsiL7dkUsd6Wrpwrt9zLRTpGvKva96X4f/cT mkdIbsvsO/GjMlJ60YL258Lu6NBGiHcUuxV04= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=WaKC3ooDo6IrqoMhHBWUTKbFPwDzB35YzjRCq55fgIOZMB5oayNtqHnIp/H8MdAIjz RTf48Qi6Zs1hBWBUJR2AL7qL57w/lhecSzsvKEjV/kSQ/wmAKq4X5MZ0PWpU2W7D9dkP jdrtjUZF7VHPdoriHW3yUs2YCIMB2QWq13LNQ= MIME-Version: 1.0 Received: by 10.213.1.15 with SMTP id 15mr1706407ebd.42.1267585019521; Tue, 02 Mar 2010 18:56:59 -0800 (PST) In-Reply-To: <4239a4321003021559s31169cfdnc982b9e8a2307533@mail.gmail.com> References: <4239a4321003021559s31169cfdnc982b9e8a2307533@mail.gmail.com> Date: Tue, 2 Mar 2010 21:56:59 -0500 Message-ID: <54cddf51003021856g36562c1ap1d4f24f1427064cd@mail.gmail.com> From: Josh Wright To: libcloud@incubator.apache.org Content-Type: multipart/alternative; boundary=000e0ce03fe0cfab050480dca23f Subject: Re: [libcloud] Virtualbox driver for libcloud? --000e0ce03fe0cfab050480dca23f Content-Type: text/plain; charset=ISO-8859-1 The VirtualBox Python API is really straightforward. There are bindings for both the local COM/XPCOM interface, and the SOAP interface. I created VBoxWeb (http://github.com/JshWright/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 ( http://code.google.com/p/vboxweb/)). The documentation for the API is bundled with the SDK. ( http://download.virtualbox.org/virtualbox/3.1.4/VirtualBoxSDK-3.1.4-57640.zip ) If this is something the libcloud community thinks should be added, I'd be happy to contribute. ~JW 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: > http://www.virtualbox.org/manual/ch08.html > --000e0ce03fe0cfab050480dca23f--