James Cammarata wrote: > On Sat, 04 Oct 2008 20:52:15 -0500, James Cammarata <[EMAIL PROTECTED]> wrote: > >> I'm still working on the snippet part, but I think this is a promising >> start! I've pushed what I've done so far to github, so people can grab >> > it > >> here for testing: git://github.com/jimi1283/cobbler.git (template-files >> branch). >> > > Done! Currently, this is working in the following manner: If the > destination path is a relative path, sync will write the file to the > /var/www/cobbler/rendered directory. If the destination path is absolute, > it won't. Both will be available through the mod_python services as > cblr/svc/op/template/profile/$name/path/$template_path, where template path > is translated in the following manner: > > 1) Underscores are converted to a double underscore > 2) /'s are converted to underscores. > > The sample.ks has a new line in it: $kickstart_template_files, which > generates output like this: > > # Kickstart template files > wget > "http://192.168.1.109/cblr/svc/op/template/profile/testcentos-i386/path/_etc_template__test2"; > --output-document="/etc/template_test2" > wget > "http://192.168.1.109/cblr/svc/op/template/profile/testcentos-i386/path/_etc_template-test"; > --output-document="/etc/template-test" > > And that's about it! Comments are appreciated. > > James C. > > >
All merged now and pushed. I changed a few minor things: (A) by default, templates are rendered in realtime, they are not written to disk. This makes usage in a very direct way easier and works fine for everything non-Solaris, so I think we're ok there. (My recommendation for the Solaris config file templating would be to call the new koan in an init script, actually -- and still pull them down dynamically -- rather than saving them to disk at all) (B) It's now a snippet. (C) Some of the "raise" errors weren't actually skipping, they were aborting, so I changed their error text. Incredibly powerful feature. This is an incredibly powerful feature. That cannot be overstated. This turns cobbler into an ultra-lightweight, easy-to-understand config management system out of the box. It doesn't do things like "keep this service running", but it's plenty solid for configuration files and would be plenty useful when used with Func. Testing welcome. I'm going to add the koan bits next that I talked about earlier, allowing it to be trivial to keep a system up2date with respect to the configuration files as configured in cobbler, which is something suitable to be put on cron if users desire. (Someone can maybe write a snippet to install koan on each host and do so automatically later) I can also think we might want a better way in the web app to edit the individual templates, so rather than having a field where we do "source=dest source2=dest2" we could instead have a nice grid of template files and where they go, with a link to edit some of the stock templates. ( We could also, like snippets, ship some stock templates for configuring a trivial config file or two. ) Comments? Questions? Ideas for other uses? --Michael _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
