Re: ifupdown2: debconf followup

2016-08-03 Thread Roopa Prabhu
On Wed, Aug 3, 2016 at 2:27 AM, Andrew Shadura wrote: > On 2 August 2016 at 08:47, Roopa Prabhu wrote: >>>> I also heard about some existing mailing list or discussions around >>>> solving ifupdown >>>> problems. We would like to be part of those discussi

Re: ifupdown2: debconf followup

2016-08-01 Thread Roopa Prabhu
On Mon, Aug 1, 2016 at 12:00 AM, Guus Sliepen wrote: > On Sun, Jul 31, 2016 at 06:58:20PM -0700, Roopa Prabhu wrote: > >> And, we will be very happy to work towards making ifupdown2 >> the default in Debian. If there are ways to make that happen, please let us >> know. &

ifupdown2: debconf followup

2016-07-31 Thread Roopa Prabhu
fits there. Thank you, Roopa https://packages.debian.org/sid/ifupdown2 https://github.com/CumulusNetworks/ifupdown2

ifupdown2: getting build/install/boot working on sid

2015-09-09 Thread roopa
it] Description=ifupdown2 init script [Service] Type=oneshot ExecStart=/sbin/ifup -a ExecStop=/sbin/ifdown -a [Install] WantedBy=multi-user.target Thanks, Roopa PS1: https://github.com/CumulusNetworks/ifupdown2 PS2: http://cumulusnetworks.github.io/ifupdown2/ lintian warning: E: ifupdown2: systemd

Re: ifupdown2 - Questions regarding packaging for debian

2015-06-01 Thread roopa
On 6/1/15, 8:55 AM, Guus Sliepen wrote: On Mon, Jun 01, 2015 at 08:40:47AM -0700, roopa wrote: Initial thought (a suggestion from Piotr) was to see if ifupdown2 [1] can be packaged as an alternative to ifupdown. Sure, if there is interest in it, go ahead! To that effect, I have some sample

ifupdown2 - Questions regarding packaging for debian

2015-06-01 Thread roopa
n alternative (I can submit patches for review) ?. Or would it prefer ifupdown2 be provided as a replacement package ?. Thanks, Roopa [1] https://github.com/CumulusNetworks/ifupdown2 [2] http://cumulusnetworks.github.io/ifupdown2/ifupdown2/userguide.html -- To UNSUBSCRIBE, email to debian-devel

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

2015-05-30 Thread roopa
On 5/30/15, 7:24 AM, Marco d'Itri wrote: On May 30, Dmitry Smirnov wrote: I'm not yet sure what can replace "ifupdown" in bonded NIC configurations with "ifenslave"... I am not sure about the obsolete bonding driver, but NM supports the new teaming driver. [1] systemd-networkd support is plan

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

2015-05-29 Thread roopa
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

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

2015-05-28 Thread roopa
On 5/28/15, 10:05 PM, Paul Wise wrote: On Thu, 2015-05-28 at 21:59 -0700, roopa wrote: 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. Please see this

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

2015-05-28 Thread roopa
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 desi