June 2017 - dev - lists.frrouting.org

FRR Packaging: existing guidelines and future plans
by Scott Leggett 07 Jun '17

07 Jun '17

Hi, I'm the current maintainer of quagga in Debian (new maintainer - only as of < 1 year). I just wanted to start a discussion about frr distro integration, and have some questions about the frr roadmap :-) I see that on your wiki[0] and in at least one recent merge[1] that you are moving towards a single system service controlling multiple daemons. I recently removed this feature from the Debian quagga package and replaced it with individual services because I think that the single service controlling multiple daemons is a mistake. There are some subtle bugs in the old debian service management scripts (e.g. [2],[3]), and having a special new mechanism to learn to control the frr daemons, which is different to the way that every other service works, is quite annoying. From the viewpoint of a distro maintainer, it is inconsistent with the unified distribution experience. And finally, disallowing the system service manager (e.g. systemd) from having proper oversight of individual services leads to a significant loss in functionality (e.g. all the features of systemd.exec[4]). In [0] you describe the main motivation for the single system service being that watchfrr is going to start and stop daemons in response to config or vtysh commands. Have you considered using dbus to command the service manager to start and stop daemons instead[5]? On a totally different topic, I thought I saw somewhere that frr is planning to deprecate individual service config files in favour of the integrated config. Is that the case? [0] https://github.com/FRRouting/frr/wiki/Distro-&-Packaging-README-FAQ [1] https://github.com/FRRouting/frr/pull/378 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678946 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412483 [4] https://www.freedesktop.org/software/systemd/man/systemd.exec.html [5] https://www.freedesktop.org/wiki/Software/systemd/dbus/ -- Regards, Scott.

2 2

Todays Technical Meeting Agenda
by Donald Sharp 06 Jun '17

06 Jun '17

1 ) New Issues 2) PR's 3) Anything else? donald

1 1

Re: [dev] Zebra Dataplane module meeting
by Bingen Eguzkitza 06 Jun '17

06 Jun '17

Sorry, I forgot the Subject. :-o On Tue, May 30, 2017 at 10:40 AM, Bingen Eguzkitza <bingen(a)voltanet.io> wrote: > Hi all, > > as we talked during last weekly technical meeting, here you have a Doodle > to set up a meeting to discuss the Zebra Dataplane module: > > https://doodle.com/poll/uwyy7t6edqbg2ucu > > For reference, this is the PR: > > https://github.com/FRRouting/frr/pull/602 > > Choose the options that work for you if you want to be part of the > discussion. > > Thanks, > > ßingen. > > > _______________________________________________ > dev mailing list > dev(a)lists.frrouting.org > https://lists.frrouting.org/listinfo/dev > >

2 4

[Update] Zebra Dataplane Module discussion
by bingen＠voltanet.io 06 Jun '17

06 Jun '17

Does it work now, Vincent? ßingen. You have been invited to the following event. Title: Zebra Dataplane Module discussion Donald, can we use you BlueJeans meeting? https://bluejeans.com/9192742159 When: Wed Jun 7, 2017 5pm – 6pm Madrid Where: https://bluejeans.com/9192742159 Video call: https://plus.google.com/hangouts/_/voltanet.io/bingen <https://plus.google.com/hangouts/_/voltanet.io/bingen?hceid=YmluZ2VuQHZvbHR…> Who: * bingen(a)voltanet.io - organizer

2 1

Invitation: Zebra Dataplane Module discussion @ Wed Jun 7, 2017 5pm - 6pm (CEST) (frr@lists.nox.tf)
by bingen＠voltanet.io 06 Jun '17

06 Jun '17

You have been invited to the following event. Title: Zebra Dataplane Module discussion Donald, can we use you BlueJeans meeting? https://bluejeans.com/9192742159 When: Wed Jun 7, 2017 5pm – 6pm Madrid Where: https://bluejeans.com/9192742159 Video call: https://plus.google.com/hangouts/_/voltanet.io/bingen <https://plus.google.com/hangouts/_/voltanet.io/bingen?hceid=YmluZ2VuQHZvbHR…> Calendar: frr(a)lists.nox.tf Who: * bingen(a)voltanet.io - organizer * renato(a)opensourcerouting.org * David Lamparter * Vincent Jardin * frr(a)lists.nox.tf * russ(a)riw.us * Donald Sharp Event details: https://www.google.com/calendar/event?action=VIEW&eid=MTQ5Njc0NDQxMDkwNiBmc… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account frr(a)lists.nox.tf because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

New Defects reported by Coverity Scan for freerangerouting/frr
by scan-admin＠coverity.com 03 Jun '17

03 Jun '17

Hi, Please find the latest report on new defect(s) introduced to freerangerouting/frr found with Coverity Scan. 1 new defect(s) introduced to freerangerouting/frr found with Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 1 of 1 defect(s) ** CID 1439519: Null pointer dereferences (FORWARD_NULL) /pimd/pim_vty.c: 239 in pim_interface_config_write() ________________________________________________________________________________________________________ *** CID 1439519: Null pointer dereferences (FORWARD_NULL) /pimd/pim_vty.c: 239 in pim_interface_config_write() 233 for (ALL_LIST_ELEMENTS_RO (vrf_iflist (VRF_DEFAULT), node, ifp)) { 234 235 /* IF name */ 236 vty_out(vty, "interface %s%s", ifp->name, VTY_NEWLINE); 237 ++writes; 238 >>> CID 1439519: Null pointer dereferences (FORWARD_NULL) >>> Comparing "ifp->info" to null implies that "ifp->info" might be null. 239 if (ifp->info) { 240 struct pim_interface *pim_ifp = ifp->info; 241 242 if (PIM_IF_TEST_PIM(pim_ifp->options)) { 243 vty_out(vty, " ip pim sm%s", VTY_NEWLINE); 244 ++writes; ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://u2389337.ct.sendgrid.net/wf/click?upn=08onrYu34A-2BWcWUl-2F-2BfV0V0… To manage Coverity Scan email notifications for "frr(a)lists.nox.tf", click https://u2389337.ct.sendgrid.net/wf/click?upn=08onrYu34A-2BWcWUl-2F-2BfV0V0…

1 0

Add as member to development slack channel
by Akshata Danivasa 02 Jun '17

02 Jun '17

Hi, Please can you add me to the development slack channel as a member? Thanks, Akshata

2 2