<div dir="ltr"><br><br><br>On Tue, Jun 17, 2014 at 5:17 PM, Karanbir Singh <<a href="mailto:mail-lists@karan.org">mail-lists@karan.org</a>> wrote:<br>><br>> On 06/16/2014 09:11 PM, Colin Walters wrote:<br>> > On Sun, Jun 15, 2014, at 05:27 AM, Scott Dowdle wrote:<br>
> >><br>> >> The easiest way to make your own would be to boot the network install<br>> >> boot.iso and create your own VM in your preferred virt platform. I used<br>> >> KVM and it worked fine. Once the install is done, customize as you see<br>
> >> fit (like add an /etc/yum.repos.d/centos-alpha.repo for example). Shut<br>> >> the machine down and clone the disk image all you want.<br>> ><br>> > The issue you get with that approach is having ssh keys, passwords etc.<br>
> > stored in the image.<br>> ><br>> > If you're in a situation where you need to do this, at least look at:<br>> > <a href="http://libguestfs.org/virt-sysprep.1.html">http://libguestfs.org/virt-sysprep.1.html</a><br>
> ><br>> > The correct thing to do though is to generate images cleanly via<br>> > something like Imagefactory (which does anaconda-in-a-vm).<br>><br>> from the project side, yea - however on the user side the dep chain in<br>
> libguestfs is quite large, most people will not want to install that on<br>> a production setup.<br>><br>> And regardless of what tool we use on the project side - the image<br>> delivered to the consumer end is still going to have metadata issues -<br>
> there needs to be a simpler way to get root pass, network config and<br>> maybe a bootstrap script injected in.<br>><br>> a min-cloud-service to compliment<br>> <a href="https://github.com/cgwalters/min-cloud-agent">https://github.com/cgwalters/min-cloud-agent</a> would/could be an<br>
> interesting win. is there something like that out there already ?<br>><br><br>I'm not exactly sure what your use case is but FWIW a wrote a simple EC2 metadata server as part of dwarf: <a href="https://github.com/juergh/dwarf/blob/master/dwarf/compute/ec2metadata.py">https://github.com/juergh/dwarf/blob/master/dwarf/compute/ec2metadata.py</a>. That could be pulled out and made a standealone service. While working on this I noticed that the avahi daemon interferes with the instance's metadata requests. I'm completely ignorant when it comes to avahi but wouldn't it be nice if it could be taught to fulfill the instance's requests?<br>
<br>Also, if the instance has the NoCloud datasource enabled (which it should) you can use a simple ISO9660 image to provide metadata to cloud-init: <a href="http://cloudinit.readthedocs.org/en/latest/topics/datasources.html#no-cloud">http://cloudinit.readthedocs.org/en/latest/topics/datasources.html#no-cloud</a><br>
<br>...Juerg<br><br><br><br> <br>><br>> this is an ongoing issue in the centos-virt-list as well<br>><br>><br>> --<br>> Karanbir Singh<br>> +44-207-0999389 | <a href="http://www.karan.org/">http://www.karan.org/</a> | <a href="http://twitter.com/kbsingh">twitter.com/kbsingh</a><br>
> GnuPG Key : <a href="http://www.karan.org/publickey.asc">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">http://lists.centos.org/mailman/listinfo/centos-devel</a><br><br></div>