<div dir="ltr">I am in a similar situation as Brian. Having the exact build process for the CentOS AMIs would allow us to not only replicate the process but also verify the origin state for all images which use the base image as a starting point. <div><br><div>Using Packer, we have a relatively streamlined build process for Vagrant, Openstack, XenServer, QEMU, Docker, and VirtualBox We're able to use a standardized kickstart to build all of our base images. We've built a blue printing tool that calculates the state of a running machine. We use the output of this, in conjunction with the kickstart file, Packer configurations, and install media to create a release artifact. </div><div><br></div><div>With both Openstack and AWS, instead of using kickstart to create the image, we start with a image and make modifications to this image. However in the case of Openstack, we are able to build a QEMU image first, then upload that to Openstack. This allows us to continue to pair the kickstart with the release, which is very helpful for ensuring completeness when replicating builds in other environments. </div><div><br></div><div>While there are other options we have pursued to achieve the ensure the known state of an AMI, in the epistemological sense, having the build process used and approved by CentOS would be immensely helpful. Our preference is to begin with an official CentOS release, whether it be an ISO or an AMI in this case. However the AMI is not only behind in releases, requiring a more intensive update, but is also not as transparent as the minimal 1503 release ISO.</div><div><div><br></div><div>Finally, in regards to the EULA, there is no seamless way to accept the EULA, that I havbe found, without logging in through the web portal. This is a small issue but generally more disruptive than desired for unattended build systems.</div></div></div><div><br></div><div>Hopefully this adds a little more insight into how some of us are consuming the AMI's and perhaps some of the issues currently presented when trying to achieve parity across the releases. <br><br></div><div>Thank you,</div><div><br></div><div>Joseph F. Reynolds</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 28, 2015 at 10:03 AM, Karanbir Singh <span dir="ltr"><<a href="mailto:mail-lists@karan.org" target="_blank">mail-lists@karan.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 28/07/15 14:58, Brian Lalor wrote:<br>
</span><span class="">> I’d like to be able to create my own AMIs from scratch and customize them as I see fit. I’ve solved the problem for my own infrastructure, but I’d like to see how CentOS is doing it, and the process should be laid out for other users to see and expand on. I think this is especially important since the AMI IDs aren’t published directly and the AMIs that are on the marketplace are rather old (and also require you to sign a EULA to use them).<br>
<br>
</span>tell me more about this EULA thing, you are using ec2 at that point -<br>
and you should not need anything more than that, right ?<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
--<br>
Karanbir Singh<br>
<a href="tel:%2B44-207-0999389" value="+442070999389">+44-207-0999389</a> | <a href="http://www.karan.org/" rel="noreferrer" target="_blank">http://www.karan.org/</a> | <a href="http://twitter.com/kbsingh" rel="noreferrer" target="_blank">twitter.com/kbsingh</a><br>
GnuPG Key : <a href="http://www.karan.org/publickey.asc" rel="noreferrer" target="_blank">http://www.karan.org/publickey.asc</a><br>
_______________________________________________<br>
CentOS-devel mailing list<br>
<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a><br>
<a href="http://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">http://lists.centos.org/mailman/listinfo/centos-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div style="text-align:left"><span style="font-family:georgia,serif">________________</span></div><div style="text-align:center"><span style="font-family:georgia,serif"><br></span></div><div style="text-align:center"><span style="font-family:georgia,serif">Joseph F. Reynolds </span></div><div style="text-align:center"><font face="georgia, serif"> Chief Executive Officer </font></div><div style="text-align:center"><span style="font-family:georgia,serif">Stackprism || 978-880-8250</span></div></div></div>
</div>