future of Boxgrinder ... building cloud images

[Steve Loranz]

I completely agree with this. I didn't mean for it to seem otherwise.

-steve


On Dec 18, 2012, at 2:03 PM, cloud-request at lists.fedoraproject.org wrote:

> ------------------------------
> 
> Message: 7
> Date: Tue, 18 Dec 2012 20:03:51 +0000
> From: Tim Bell <Tim.Bell at cern.ch>
> To: Fedora Cloud SIG <cloud at lists.fedoraproject.org>,
> 	"herrold at owlriver.com"	<herrold at owlriver.com>
> Subject: RE: cloud Digest, Vol 36, Issue 24
> Message-ID:
> 	<5D7F9996EA547448BC6C54C8C5AAF4E5A856BF9B at CERNXCHG01.cern.ch>
> Content-Type: text/plain; charset="utf-8"
> 
> 
> I don’t see an image factory approach and a puppet approach as being competitors.
> 
> We need to find ways to produce common images for multiple hypervisors in an automated fashion. Booting VMs and then waiting 30 minutes for a yum update (or even worse, waiting an hour for Office 2013 to install) is not exactly elastic computing so a regular run of standard version builds is a key function.
> 
> Puppet provides the function to take the base images and create the custom configurations.
> 
> Organising up-to-date standard images for the common platforms and then the 'last-mile' via puppet seems efficient.
> 
> (I use Puppet as an example, Chef would be equally appropriate)
> 
> Tim
> 
>> -----Original Message-----
>> From: cloud-bounces at lists.fedoraproject.org [mailto:cloud-
>> bounces at lists.fedoraproject.org] On Behalf Of Steve Loranz
>> Sent: 18 December 2012 19:13
>> To: herrold at owlriver.com
>> Cc: cloud at lists.fedoraproject.org
>> Subject: Re: cloud Digest, Vol 36, Issue 24
>> 
>> Russ,
>> 
>> Apologies if I'm misinterpreting what you're saying here, but I think that
>> imagefactory can do what you are looking for. The core of imagefactory
>> supplies the REST interface, CLI, provides some storage for built images, and
>> manages dispatching work to the plugins. The plugins do the heavy lifting and
>> these are separated as OS and Cloud plugins. We currently have one OS plugin
>> that started off as Fedora/RHEL specific and uses Oz to create a base JEOS
>> image. All of the customization that creates a target image from a base image
>> is done by a cloud plugin.
>> 
>> So, you could have a very minimal TDL that creates a minimal base JEOS
>> image. You could then supply your own Cloud plugin for your virt service that
>> does the customization you want.
>> 
>> The imagefactory project is packaged separately from Aeolus and can be used
>> without any other component from Aeolus. Oz is used by the current OS plugin,
>> but that plugin can be replaced by another that uses some other method of
>> provisioning.
>> 
>> -steve