Hi there, (Not currently a libcloud dev, so can't comment on your offer.)
A belated thanks for sending notice of Clapp. It really looks cool. I checked out your bitbucket page. I'm wondering if you can expand a bit on the use-case. I hate defining things oppositionally, so please cut me off if I'm making a totally lame comparison, but I thought of OVF when I read your description. If the difference between OVF + CLAPP that you take the burden off of the vm-manager? (In addition to supporting more formats AND providers.) andy @thesethings On Mon, Dec 14, 2009 at 8:16 AM, Solomon Hykes <[email protected]>wrote: > Hi libclouders, > > Following up on Alex's message: > > > Subjects discussed (please fill in the gaps if I missed something): > > [...] > > - Needs around image formats and configuration management. Right now > > Rackspace and EC2 are really the only platforms you can get your files > > on to to bootstrap the process. > > I would like to offer my assistance on this. I started writing a tool > called Clapp [1], which stands for "cloud appliance". It defines a > format for server images which you can actually manage. The idea is to > maintain a single "template" image which is small and version > controlled, then generate images in any format, for any cloud, as you > need them. I've seen this approach implemented on production systems > and it works wonderfully. > > In my experience we typically rely too much on runtime configuration > tools like Puppet and Chef, just because the image management > experience is so awful. Hopefully we can change that! > > I would love to discuss, and contribute to, anything related to image > management in libcloud. Keep up the good work! > > [1] You can check out a POC at http://bitbucket.org/dotcloud/clapp > > > Best, > Solomon Hykes >
