Re: Some questions regarding extension of cobbler suse snippets/templates

2012-02-02 Thread Christian Horn
Hi, modifications required, or not considered useful? Christian On Sat, Jan 21, 2012 at 08:34:12PM +0100, Christian Horn wrote: > Hi, > > > On Fri, Jan 20, 2012 at 09:24:36PM +0100, Jörgen Maas wrote: > > The networking snippet should be updated to reflect the new interface_type > > naming sch

Re: Some questions regarding extension of cobbler suse snippets/templates

2012-02-02 Thread Michael DeHaan
Anything for SuSE's default sample.xml should first strive for parity with the Red Hat example -- ideally it should set up networking, have the config integration, etc. I'm not against shipping a "complex" example showing more but "complex" should not be the default. I'd like it to aim for pa

Re: Some questions regarding extension of cobbler suse snippets/templates

2012-02-02 Thread Christian Horn
On Thu, Feb 02, 2012 at 10:44:37AM -0500, Michael DeHaan wrote: > Anything for SuSE's default sample.xml should first strive for parity > with the Red Hat example -- ideally it should set up networking, have > the config integration, etc. The autoyast_complex.xml provides the network setup in rh

Re: Some questions regarding extension of cobbler suse snippets/templates

2012-02-02 Thread Michael DeHaan
I think we're ok as is unless anyone has objections/suggestions. Send me a github pull request and we can merge it. Yes, it sounds like it should just replace the default if it more or less does what the RHEL-compatible one does. I was confused earlier because it had some bonus capabilities th