[systemd-devel] [RFC][PATCH] networkd: add a basic network daemon

Tom Gundersen teg at jklm.no
Wed Nov 6 16:44:43 PST 2013


On Wed, Nov 6, 2013 at 3:08 AM, Kok, Auke-jan H
<auke-jan.h.kok at intel.com> wrote:
> On Tue, Nov 5, 2013 at 4:33 PM, Tom Gundersen <teg at jklm.no> wrote:
>> This daemon listens for and configures network devices tagged with
>> 'systemd-networkd'. By default, no devices are tagged so this daemon
>> can safely run in parallel with existing network daemons/scripts.
>>
>> Networks are configured in /etc/systemd/network/*.network. The first .network
>> file that matches a given link is applied. The matching logic is similar to
>> the one for .link files, but additionally supports matching on interface name.
>>
>> The mid-term aim is to provide an alternative to ad-hoc scripts currently used
>> in initrd's and for wired setups that don't change much (e.g., as seen on
>> servers/and some embedded systems).
>>
>> Currently, static addresses and a gateway can be configured, mostly as a proof
>> of concept. I expect to expand on this as soon as we are agreed on the basic
>> design.
>>
>> Comments, testing and contributions greatly appreciated!
>
> alright, I'll comment, but it took me 5 minutes to clear the coffee
> off my monitor...
>
> Looking at the feature list, why are you not contributing to connman
> instead? It seems you're going to be duplicating a ton of code.... And
> connman does what your goal is, meaning you can pre-provision static
> configurations without any of the more involved dependencies. It has a
> DBus interface for status, configuration etc....
>
> I'm frankly shocked a bit, not sure what to say. Maybe this is a great
> thing, but, without a doubt someone will want to convert this code
> long term into connman / NM, and at that point we have 3 standards,
> not 2. Best to try and stick to 2 standards and fix the one that has
> the best long-term prospective value.

Sorry about the monitor ;-) It seems others already answered (thanks
for that!), but please ping me if you have any further concerns or
questions.

Cheers,

Tom


More information about the systemd-devel mailing list