Hi Russ,<div><br>I think you'll find it hard to get any traction here kickstarts especially in the "cloud front" are used increasingly less in favour of bootstrapping an instance with puppet / chef for provisioning above and beyond the base os.</div>
<div><br></div><div>The tdl format is somewhat of a stop gap between kickstarts and fully fledged provisioning I have found, and a good project providing many example tdls is the Aeolus project: <a href="http://www.aeolusproject.org/">http://www.aeolusproject.org/</a></div>
<div><br></div><div>Myself I have gone the way of kickstarts -> boxgrinder -> oz -> puppet.<br></div><div><br></div><div>Also of note, puppet manifests as they use a ruby DSL version control very well, I can not vouch for chef however.</div>
<div><br></div><div>Cheers</div><div><br></div><div>David</div><div><br></div><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Dec 18, 2012 at 4:15 PM, R P Herrold <span dir="ltr"><<a href="mailto:herrold@owlriver.com" target="_blank">herrold@owlriver.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">in the IRC channel, I am advised by 'msavy' that Boxgrinder is on a path to end as a project, and transition into:<br>
<a href="http://imgfac.org/" target="_blank">http://imgfac.org/</a><br>
<br>
which uses underneath: oz<br>
<a href="https://github.com/clalancette/oz" target="_blank">https://github.com/<u></u>clalancette/oz</a><br>
<br>
Seemingly also, the former (and somewhat broken) appliance-creator goes away<br>
<br>
My goal is to be able to get to an TUI tool:<br>
image building image<br>
that accepts kickstart config files as input, and emits runnable new images of various type, and it looked as though I could graft on the needed elements to Boxgrinder. There is a lot of churn, for example on the Fedora 'cloud' sig mailing list, and on corresponding Debian list, on what to include, or exclude from pre-built cloud images.<br>
<br>
I think those 'cloud' working groups are solving the wrong problem at the wrong place, [some want JEOS to include a listening sshd, and package install tool; others want rsync, or man, or more, or less ... the preferences never end and there is no 'right answer']<br>
<br>
An:<br>
image building image<br>
decouples those design preferences and moves solving those issues into a flat text specification ( a 'ks.cfg', etc) that will work well in a version control system (unlike using a GUI front end which does not)<br>
<br>
-- Russ herrold<br>
</blockquote></div><br></div>