[imgfac] centos, support for non-cloud xen, vmware (persona/enterprise)

Darren Hartford binarymonk01 at yahoo.com
Thu May 23 14:54:26 UTC 2013


Thanks everyone for the quick and multiple responses, shows community activity! :-)

I'm going to start playing with this, but first it appears need Fedora 16 or 17 to run (still running 14, so upgrading that first before trying imgfac).

Steve's explanation sounds close to what I would expect (and similar to boxgrinder), just unsure where to find available plugins such as if virtualization target/provider plugins (xen, vmware) exists versus the current cloud plugins.

-Darren




________________________________
 From: Steve Loranz <sloranz at redhat.com>
To: Anthony R Tiradani <tiradani at fnal.gov> 
Cc: Darren Hartford <binarymonk01 at yahoo.com>; "aeolus-users at lists.fedorahosted.org" <aeolus-users at lists.fedorahosted.org> 
Sent: Wednesday, May 22, 2013 10:11 AM
Subject: Re: [imgfac] centos, support for non-cloud xen, vmware	(persona/enterprise)
 


That's not entirely accurate.

Image Factory produces three types of images. 

1) The Base Image is a JEOS (Just Enough OS) + OS level customizations image, and this is what we use Oz for in what is currently the only shipping OS plugin. Future OS plugins may use something other than Oz for this, especially if those plugins are for an OS that Oz doesn't support.

2) The Target Image is an image that has been transformed to work on a specific cloud or hypervisor. For some, such as RHEV, there is really nothing to do here. For others, such as EC2, it's rather involved. Each cloud we support has its own Cloud plugin. Oz is not used for this. The important thing to note is that you can specify a Base Image id and create as many target images from that as you want. A new Base Image will not be created in that case. We do offer a shortcut, where you can instead provide a template instead of a base image id and a Base Image will be created.

3) The Provider Image is the image that actually ends up on the cloud or hypervisor. At this point, we are not really adding any per region customizations to the image, but instead record any metadata such as the providers id for the image, etc. Again, if you provide a target image id, you can push as many provider images off that same target image as you want without rebuilding. Again, you have the option to shortcut that and provide a template to have the whole tree built in one step.

The two points to take away from this are that you do not need to rebuild every time and there is more to Image Factory than Oz.

-steve


On May 22, 2013, at 8:33 AM, Anthony R Tiradani <tiradani at fnal.gov> wrote:

 I use OZ since Image Factory has no concept of one and only one image per set of unique parameters.  Every build is a new image.  However, Image Factory uses OZ under the covers so you end up using the same code to build the image in either case.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fedorahosted.org/pipermail/aeolus-users/attachments/20130523/c39ea940/attachment.html>


More information about the aeolus-users mailing list