Network configuration future
dcbw at redhat.com
Fri Sep 7 18:08:34 UTC 2012
On Mon, 2012-09-03 at 09:20 +0200, Olaf Kirch wrote:
> On Friday 31 August 2012 02:47:38 Bill Nottingham wrote:
> > I'm not saying you *can't* do it, but it's also not something to do
> > lightly.
> Totally agreed. But what are really the points of maximum stickiness?
> Obviously, configuration files and command line interfaces.
> So, for a new network management framework, this means
> - using ifconfig/route should continue to work (ie the service
> shouldn't touch interfaces unless told so)
Touching an interface depends on your use-cases. For many cases it
should be automatically managed without any intervention from the user,
and in many other cases, that should be under the control of the
administrator. It's definitely not an either/or choice.
> - there should be ifup/ifdown scripts that offer the same
> semantics as the current ones, as far as possible.
Yes; we've modified the ifup/ifdown scripts to handle interaction with
> - there should be a way to parse old-style ifcfg files
Yes; obviously anything that handles network management on Fedora needs
to do this.
> Could you think of any other?
> Neo didn't bring down the Matrix. SOA did. (soafacts.com)
> Olaf Kirch - Director SUSE Linux Enterprise; R&D (okir at suse.com)
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
More information about the devel