Deadlines

[Simo Sorce]

On Fri, 2014-02-21 at 15:21 +0100, Reindl Harald wrote:
> 
> Am 21.02.2014 15:11, schrieb Colin Walters:
> > On Fri, Feb 21, 2014 at 8:29 AM, Jóhann B. Guðmundsson <johannbg at gmail.com> wrote:
> >> Network Manager should go away on server installs it never work properly and nobody used it
> > 
> > No, you are wrong.
> > 
> > Red Hat Enterprise Linux 7(.0) will default to NetworkManager, and even if all resources that are presently on
> > NetworkManager were dropped today and focused on networkd, we'd still need a long ongoing investment in actively
> > maintaining it both for the ongoing server case *and* for the client case  (GNOME is deeply invested in NM)
> 
> you missed the "on server installs"
> 
> so the question is valid in case we talk about *Fedora server*, F21 is delayed because
> Fedora.next / Fedora products and so systemd-209 should not be the target for F21 and
> even considered for F20 in it's release cycle after systemd-208 is not that bugfree
> 
> that RHEL7 defaults to NM is no argumentation for Fedora
> systemd-209 simply was not available for RHEL7 target
> the same as systemd was not for RHEL6 which uses hence upstart

We can look at systemd-networkd in a distant future when it will be
proven to do what a generic server install needs.
However its time is not now.

NM has been enhanced to work in a great many situations, it includes
comprehensive support for all the situations systemd-networkd started
supporting and many more. It has a comprehensive CLI, TUI and even GUI
interface for administration that is completely lacking in systemd and
it has been tested and improved for a long time.

It can be easily integrated with things like cockpit as it offers a
broad dbus API.

People are working on getting deep integration so that NM can provide
out of the box DNSSEC support for the whole system too (try to install
dnssec-trigger on your F20 machine now to get a taste of it).

Etc, etc...

I do not think systemd will reach that level of functionality (and
probably never should, it makes no sense to duplicate all this work).

Systemd-networkd will probably be usable in some specialized cases (like
getting network in network boot systems or other well defined and
confined situations) but is not a general purpose network management
tool now, so it shouldn't be our default choice at the moment.

Simo.

-- 
Simo Sorce * Red Hat, Inc * New York