<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Just to try to clear up what I meant...<br>
<br>
With BoxGrinder when you build an image it is written to a single
file. All subsequent builds overwrite that file. ImageFactory
writes to a new file each time you build the image and as far as I
could tell, the only way to know which file name is the current
build is to manually parse the output. I script my builds so I
need to know the file name. <br>
<br>
I understand and know about Steve's points, but I do have to
iterate builds when developing new images, and I don't want to
push until the image is "right". So OZ works best for me.<br>
<br>
Thanks,<br>
<pre class="moz-signature" cols="72">Anthony Tiradani
<a class="moz-txt-link-abbreviated" href="mailto:tiradani@fnal.gov">tiradani@fnal.gov</a>
+1 630 840 4479</pre>
On 05/23/2013 09:54 AM, Darren Hartford wrote:<br>
</div>
<blockquote
cite="mid:1369320866.46336.YahooMailNeo@web141401.mail.bf1.yahoo.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div style="color:#000; background-color:#fff; font-family:tahoma,
new york, times, serif;font-size:12pt">Thanks everyone for the
quick and multiple responses, shows community activity! :-)<br>
<br>
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).<br>
<br>
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.<br>
<br>
-Darren<br>
<div><span><br>
</span></div>
<div><br>
</div>
<div style="font-family: tahoma, new york, times, serif;
font-size: 12pt;">
<div style="font-family: times new roman, new york, times,
serif; font-size: 12pt;">
<div dir="ltr">
<hr size="1"> <font face="Arial" size="2"> <b><span
style="font-weight:bold;">From:</span></b> Steve
Loranz <a class="moz-txt-link-rfc2396E" href="mailto:sloranz@redhat.com"><sloranz@redhat.com></a><br>
<b><span style="font-weight: bold;">To:</span></b>
Anthony R Tiradani <a class="moz-txt-link-rfc2396E" href="mailto:tiradani@fnal.gov"><tiradani@fnal.gov></a> <br>
<b><span style="font-weight: bold;">Cc:</span></b>
Darren Hartford <a class="moz-txt-link-rfc2396E" href="mailto:binarymonk01@yahoo.com"><binarymonk01@yahoo.com></a>;
<a class="moz-txt-link-rfc2396E" href="mailto:aeolus-users@lists.fedorahosted.org">"aeolus-users@lists.fedorahosted.org"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:aeolus-users@lists.fedorahosted.org"><aeolus-users@lists.fedorahosted.org></a> <br>
<b><span style="font-weight: bold;">Sent:</span></b>
Wednesday, May 22, 2013 10:11 AM<br>
<b><span style="font-weight: bold;">Subject:</span></b>
Re: [imgfac] centos, support for non-cloud xen, vmware
(persona/enterprise)<br>
</font> </div>
<div class="y_msg_container"><br>
<div id="yiv8906170992">
<div>
<div>That's not entirely accurate.</div>
<div><br>
</div>
<div>Image Factory produces three types of images. </div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>-steve</div>
<div><br>
</div>
<br>
<div>
<div>On May 22, 2013, at 8:33 AM, Anthony R Tiradani
<<a moz-do-not-send="true" rel="nofollow"
ymailto="mailto:tiradani@fnal.gov"
target="_blank" href="mailto:tiradani@fnal.gov">tiradani@fnal.gov</a>>
wrote:</div>
<br class="yiv8906170992Apple-interchange-newline">
<blockquote type="cite"><span
style="font-family:'Lucida
Grande';font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;display:inline;float:none;"> 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.</span></blockquote>
</div>
<br>
</div>
</div>
<br>
<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>