James Cammarata wrote: > On Sat, 27 Sep 2008 22:12:21 -0500, James Cammarata <[EMAIL PROTECTED]> wrote: > >> Available via git hub: >> git://github.com/jimi1283/cobbler-template-files.git >> > > Made an update to this to force the destination to always be relative to > the rendered directory, in order to prevent someone from accidentally > overwriting system files (or maliciously, if a user were granted sudo > access to cobbler. > > I've also created a more generic github repo: > git://github.com/jimi1283/cobbler.git > > Thanks. > > James c. > >
We were talking about this on IRC right now, and the idea was this.... use Cobbler as a full fledged templating system, if desired, for ANY files needed, and have this all set up to deliver these files in kickstart. Example: cobbler system edit --name=foo --template-files="/srv/myiptables.template=/etc/sysconfig/iptables" This would generate in the kickstart code for the following snippet: %post $wget_extra_template_files And the templated files could be served up by mod_python, so no syncing would be required* wget http://cobbler.example.org/cblr/svc/op/ks/system/$name/file/_etc_sysconfig_iptables -O .... # etc * = for Solaris support, that James was working on, we'll have to save them on the filesystem. What does this get us? (A) an iptables solution, for free (B) free templating for arbitrary config files for those that decide they do not want a config management system -- i.e. installing systems in a disconnected environment, machines that will be deployed beyond the provisioning network, already have another system you want to use, etc. I think that's a *huge* feature and would be very easy to understand, especially when we add the bits in the kickstart to auto-slurp the files we associate automatically with each profile and/or system. Very cool. Discussion welcome! --Michael _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
