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

[roopa <roopa@cumulusnetworks.com>]

On 5/29/15, 1:44 AM, Michael Biebl wrote:
> Am 29.05.2015 um 06:59 schrieb roopa:
> > 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.
> Does ifupdown2 handle hotplugged / dynamic interfaces, and if so, how?
> Is it written as a daemon?
It does not have a daemon right now..., and we use netplugd for 
dynamic/hotplugged interfaces when needed. We are thinking of adding a 
daemon that listens to netlink events  from the kernel, but that
was mainly for creating a cache of interface objects from the kernel for 
faster ifquery support.
But this daemon could also be used do the same thing netplugd does.

thanks,
Roopa