Jasper Capel wrote:
Michael DeHaan wrote:
> Other services could just be a simple as providing some good snippets
> for them, so I think it's up the users to supply them.
>
> One of my definite goals is to get more of the snippets in the stock
> templates and also ship more in /var/lib/cobbler.
>
>
It's a bit off-topic, but in light of the recent developments in
supporting other breeds, how about providing stock snippets this way:
/var/lib/cobbler/redhat/iptables_if_enabled
/var/lib/cobbler/debian/iptables_if_enabled
/var/lib/cobbler/distributionX/iptables_if_enabled
and maybe have a SNIPPET::$breed/iptables_if_enabled, or have SNIPPET::
look in the $breed directory after it's scanned the per_system and
per_profile directory for a snippet to include.
You mean /var/lib/cobbler/snippets/$breed I think, but I'll address that...
You make a good point about distro compatiblity being important. I think
it's just as easy to #if around the breed inside the snippet where
required. "$breed" is exposed to the kickstart templating engine. So we
can use the same snippet in many places regardless of breed, if the
snippet itself is smart. Many things are largely just going to be the
same due to LSB.
If someone sees where something in a snippet we want to use for other
distros is Red Hat specific, feel free to send in a patch or let me
know. One obvious example I know of is using
/etc/rc.d/init.d/servicename restart instead of /sbin/service. I'm sure
there are others and also the basic things like path differences.
However it's true that some things like the network config bits are
definitely kickstart-only, so in those cases, yes, we /might/ want to
namespace them. Since those are still on the devel branch, now is
probably a good time.
--Michael
Jasper
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler