[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#786902: O: ifupdown -- high level tools to configure network interfaces



On 5/27/15, 8:18 PM, Paul Wise wrote:
On Thu, May 28, 2015 at 1:41 AM, Christoph Anton Mitterer wrote:

Haven't tried systemd-networkd yet, but at least NM fails in even very
simple cases (like resolving is broken, when I disconnect the wire and
go back to wifi, etc. pp.) ... plus the whole design, that it tries to
be the canonical configuration place but still uses the actual native
tools for all tasks, seems to be simply wrong...
I believe the latest versions in unstable are better in this regard.

Sorry if I am intercepting this thread at the wrong spot..., but I just wanted to bring up
ifupdown2 again.

We are running Debian on an enterprise class switch/router..and we initially started with the /etc/network/interfaces file format and ifupdown. That stuck..and we are very happy with it. And we currently have quite a large user base. It would really be great if debian continued to support the current /etc/network/interfaces
format.

ifupdown did pose a few challenges to manage interfaces at the scale we deploy (sometimes more than 2000 interfaces bridges/bonds etc). But we loved the extensibility and modularity it provided. And the only difficulty continuing with ifupdown was extending it in bash and literate programing language it was written in.

We decided to rewrite it but continue to provide the existing user interface and also extend it with other features which would make configuration easier. And we rewrote it in python https://github.com/CumulusNetworks/ifupdown2. We have built a lot of documentation around it for more complex interface configurations (google ifupdown2 for some hits). Choice of python was mainly because of the readily available python modules for network configuration today. We were able to add interface graph, json and template support with a few lines of code. A wide range of netlink python modules for network configuration are also available today. And many are already part of the debian distribution.

I understand that there may be some concerns of it being in python.
But, We should be able to make it work with a python-minimal installation if desired.

We plan to post it for inclusion as an alternative to ifupdown (using the debian alternatives infrastructure), hoping to make it easier
for people who may be interested in trying it out.

Thanks to piotr@debian.org for providing some initial feedback on the packaging requirements

Thanks.


Reply to: