Imagefactory is more than a REST interface to oz. Oz creates a JEOS image. The
customization that oz performs is limited to installing additional packages or
running commands within a VM started with the JEOS image. Oz does not have
knowledge of what needs to be added or how an image needs to be
d then the
> 'last-mile' via puppet seems efficient.
>
> (I use Puppet as an example, Chef would be equally appropriate)
>
> Tim
>
>> -Original Message-
>> From: cloud-boun...@lists.fedoraproject.org [mailto:cloud-
>> boun...@lists.fedoraproject.o
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
Just a quick note on the difference between ImageFactory and Oz.
Oz creates a KVM image, does a Just Enough OS (JEOS) install of the operating
system, and provides a means to adding additional packages to and/or running
customization scripts on the OS installed in this image.
ImageFactory creat
The Image Factory team is pleased to announce the release of Image Factory
version 0.2.1. Version 0.2.1 adds features and bugfixes needed to support the
next step in the evolution of Aeolus.
- VMware vSphere support has been added.
- Support for snapshots of EC2 images on EBS has been add
