#opendaylight-meeting: tsc

Meeting started by colindixon at 17:00:11 UTC (full logs).

Meeting summary

  1. agenda bashing and roll call (colindixon, 17:00:18)
    1. colindixon (colindixon, 17:00:25)
    2. abhijitkumbhare (for ChrisPriceAB ) (abhijitkumbhare, 17:00:34)
    3. LuisGomez (LuisGomez, 17:00:54)
    4. Daniel Farrell (dfarrell07_sick, 17:00:54)
    5. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=44841#Agenda the agenda (colindixon, 17:00:56)
    6. gkaempfer (gkaempfer, 17:00:58)
    7. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-03-24-17.00.html last week's minutes (colindixon, 17:01:18)
    8. ACTION: colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron? (colindixon, 17:01:30)
    9. ACTION: zxiiro will look more into maven central now that we're at least signing things (colindixon, 17:01:40)
    10. rovarga__ proxy for jmedved (rovarga__, 17:02:07)
    11. tykeal says that maven central requies that we push to their nexus, and our documentation link is incorrect according tot hem (colindixon, 17:02:12)
    12. edwarnicke (edwarnicke, 17:02:32)
    13. ACTION: phrobb to send out a thread about a hackfest at the end of june (colindixon, 17:02:38)
    14. mohnish anumala (mohnish_, 17:02:40)
    15. ACTION: ChrisPriceAB and phrobb_ have heather come and talk to the ODL community about how to have a bigger presence at OpenStack (colindixon, 17:02:53)

  2. TSC mailing list votes and discussion (colindixon, 17:04:02)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-March/004923.html TSC elections, blocking on the board approving a shorter than 12-month term for 4 CAL slots (colindixon, 17:04:25)
    2. https://lists.opendaylight.org/pipermail/tsc/2016-March/004961.html vote on Jozef Bacigal as OpenFlow Plugin committer (colindixon, 17:04:39)
    3. https://lists.opendaylight.org/pipermail/tsc/2016-March/004963.html formally approve the Boron release plan (colindixon, 17:04:53)
    4. https://lists.opendaylight.org/pipermail/release/2016-March/006121.html Labeling features experimental until they meet system test requirements (colindixon, 17:05:06)
    5. https://lists.opendaylight.org/pipermail/tsc/2016-March/004956.html MPLS-TP Creation Review over e-mail (colindixon, 17:05:17)
    6. https://lists.opendaylight.org/pipermail/project-proposals/2016-March/000454.html thread about commonality between the two MPLS-TP projects (colindixon, 17:05:29)
    7. https://lists.opendaylight.org/pipermail/tsc/2016-March/004908.html keeping clearn committers lists (colindixon, 17:06:29)

  3. events (colindixon, 17:06:43)
    1. https://www.opendaylight.org/global-events (colindixon, 17:06:54)

  4. boron (colindixon, 17:07:16)
    1. The Boron Autorelease job fails to build didm-identification. Currently working with their team to address the issues. (anipbu, 17:08:05)
    2. Currently missing the M1 status email for the following projects: didm, eman, genius, vbd, kafkaproducer, next, reservation, snbi. These projects have been notified. (anipbu, 17:08:12)
    3. ACTION: colindixon to follow up with why we're seeing faliures in autorelease but not in projects (colindixon, 17:08:46)

  5. stable/beryllium (colindixon, 17:08:52)
    1. nothing this week (colindixon, 17:08:58)

  6. system integration and test (colindixon, 17:09:07)
    1. nothing this week (colindixon, 17:09:15)
    2. jamoluhrsen says that the packaging stuff should go on the download page, but not the deployment scripts (colindixon, 17:10:08)

  7. infratstructure (colindixon, 17:10:39)
    1. last weekend we took an outage for a lot of servies, we're now using 2.12.2 for gerrit (colindixon, 17:11:11)
    2. you now need to add your gpg key and sign pushes if you want to not have a ? next to your owner (colindixon, 17:11:34)
    3. this will fail in gerrit if you use subkeys to sign (which is how tykeal) recomments (colindixon, 17:12:01)
    4. you can use the feature if you have a master key with the default sub of singing (colindixon, 17:12:14)
    5. to do this you need git 2.6 and you can do this with git (colindixon, 17:12:40)
    6. ACTION: tykeal to write this up and send an e-mail about this (colindixon, 17:12:51)
    7. we will be moving Nexus this weekend, with some downtime (colindixon, 17:13:08)
    8. https://lists.opendaylight.org/pipermail/release/2016-March/006139.html downtime e-mail (colindixon, 17:13:50)
    9. gerrit may be slow while we rysnc data from old to new nexus (today) (colindixon, 17:14:05)

  8. Cardinal NMS creation review (colindixon, 17:15:56)
    1. https://wiki.opendaylight.org/view/Project_Proposals:Cardinal (colindixon, 17:16:53)
    2. https://lists.opendaylight.org/pipermail/project-proposals/2016-March/000430.html proposed on 3/11/2016 (colindixon, 17:17:31)
    3. opendaylight monitoring as a service (colindixon, 17:17:31)
    4. idea is to proviede an abstraction for exposing monitoring, diagnositcs, and events in OpenDaylight (colindixon, 17:20:03)
    5. this will then generate an OpenDaylight MIB, monitoring and traps via SNMP for the controller itself (colindixon, 17:20:43)
    6. in later releases the goal is to expose network devices as well (colindixon, 17:21:58)
    7. colindixon notes that there's some information about carbon and boron in the scope, which is unncessary, but probably harmless (colindixon, 17:24:51)
    8. there is a proposed OpenDaylight MIB (colindixon, 17:25:29)
    9. https://wiki.opendaylight.org/view/File:Cardinal-ODL_Monitoring_as_a_Service_V1.pdf slides (colindixon, 17:25:47)
    10. abhijitkumbhare asks if they are expecting people to publish data into this, for now it's that they will grab things they need (colindixon, 17:27:17)
    11. rovarga__ says that there is an RFC which translates to YANG to SMIv2 which would allow YANG models to be be MIBs (colindixon, 17:27:42)
    12. rovarga__ wonders if we would do this by hand or use the RFC description, and then how it woudl be maintained (colindixon, 17:28:02)
    13. rovarga__ basically says that having automated translation would seem like the right way to do (colindixon, 17:28:19)
    14. Rajani says that's probably the right stategy, but it's not clear if that's how they'll do it at first (colindixon, 17:29:02)
    15. vishnoianil asks why are we providing data that's already exposed by MD-SAL also as SNMP (colindixon, 17:29:20)
    16. LuisGomez says that supporting SNMP allows for most NMSes to monitor OpenDaylight, where MD-SAL is harder (colindixon, 17:31:12)
    17. edwarnicke asks if they plan is to run snmpd and snmptradp as separate processes, they say yes (colindixon, 17:31:54)
    18. edwarnicke asks why the decision was to also use snmptrapd and snmpd over Java native with snmp4j (colindixon, 17:33:21)
    19. colindixon asks if it will be platform specific, for now it sounds like yes, Linux, but it's possible to run snmpd and snmptrapd on other platforms (colindixon, 17:34:08)
    20. ACTION: colindixon and edwarnicke to follow up about deployability concerns (colindixon, 17:34:28)
    21. ACTION: colindixon to connect cardinal with the OpenNMS guys to see if there's a way to keep some work in common (colindixon, 17:35:28)
    22. they show a PoC with nagios and netsnmp monitoring OpenDayilght as well as traps (colindixon, 17:35:57)
    23. mohnish_ agrees with rovarga__'s concerns (colindixon, 17:37:37)
    24. rovarga__ notes that the MIB <=> YANG may or may not be bidirectional, it might be only MIB to YANG (colindixon, 17:39:01)
    25. VOTE: Voted on "shall the TSC move the Cardinal project to incubation?" Results are, +1: 6 (colindixon, 17:39:58)
    26. colindixon votes +1 (colindixon, 17:40:16)
    27. AGREED: the Cardinal project is now in incubation (colindixon, 17:40:27)
    28. VOTE: Voted on "shall the TSC allow cardinal to join Boron at offet 2?" Results are, +1: 6 (colindixon, 17:42:19)
    29. AGREED: Cardinal can join Boron at offset 2 (colindixon, 17:42:25)

  9. Atribum BGP Router Creation review (colindixon, 17:42:38)
    1. https://github.com/onfsdn/atrium-docs/wiki/ODL-Based-Atrium-Router-16A (colindixon, 17:42:49)
    2. https://lists.opendaylight.org/pipermail/project-proposals/2016-March/000405.html proposed on 3/2/2016 (colindixon, 17:43:09)
    3. https://wiki.opendaylight.org/view/Project_Proposals:Atrium_Router (mohnish_, 17:44:11)
    4. https://wiki.opendaylight.org/view/Project_Proposals:Atrium_Router (colindixon, 17:44:27)
    5. colindixon asks about the scope, it says it's for "the first release" but we typically try to keep scope for the project, not for ag given release (colindixon, 17:46:31)
    6. colindixon does note that it can be adjusted later if need be, so it's probably not the end of the world, but colindixon is still curious if the intended eventual scope is broader (colindixon, 17:47:03)
    7. colindixon asks for ARP, are you using the ArpHandler in l2switch or a new one? (colindixon, 17:50:28)
    8. colindixon notes that his understanding that right now it's his unnderstand that they're using Quagga, but in the future they might move to using OpenDaylight BGP as an option in the future (colindixon, 17:51:45)
    9. Prem_ asks for the deployment model of running with Quagga, for now Quagga won't be in any opendaylight repo, but will need to be downloaded and run by the user (colindixon, 17:53:02)
    10. rovarga__ says he sees there being dragons in having potentially having two different BGP implementations that ODL would run with (colindixon, 17:58:46)
    11. there are potienail problems with (1) fighting over the BGP port, (2) complicating BGP compatibility testing with ODL b/c we have two ways, (3) reporting stats about BGP being ambiguous (colindixon, 17:59:36)
    12. colindixon notes that we have traditionally have been very clear that competeing options in a space are fine at least at mature and incubation (colindixon, 18:01:36)
    13. VOTE: Voted on "shall the TSC move the the Atrium BGP project to incubation?" Results are, +1: 7 (colindixon, 18:04:36)
    14. offset 2 project in boron (colindixon, 18:05:46)
    15. VOTE: Voted on "shall the TSC allow the Atrium BGP project to join Boron?" Results are, +1: 6 (colindixon, 18:05:59)
    16. gkaempfer also votes +1 (colindixon, 18:06:42)
    17. AGREED: the Atrium BGP router is now an incubation project (colindixon, 18:06:57)
    18. AGREED: teh Atriium BGP router is allowed to join Boron at offest 2 (colindixon, 18:07:15)

  10. cookies (colindixon, 18:07:18)


Meeting ended at 18:07:21 UTC (full logs).

Action items

  1. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
  2. zxiiro will look more into maven central now that we're at least signing things
  3. phrobb to send out a thread about a hackfest at the end of june
  4. ChrisPriceAB and phrobb_ have heather come and talk to the ODL community about how to have a bigger presence at OpenStack
  5. colindixon to follow up with why we're seeing faliures in autorelease but not in projects
  6. tykeal to write this up and send an e-mail about this
  7. colindixon and edwarnicke to follow up about deployability concerns
  8. colindixon to connect cardinal with the OpenNMS guys to see if there's a way to keep some work in common


Action items, by person

  1. ChrisPriceAB
    1. ChrisPriceAB and phrobb_ have heather come and talk to the ODL community about how to have a bigger presence at OpenStack
  2. colindixon
    1. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
    2. colindixon to follow up with why we're seeing faliures in autorelease but not in projects
    3. colindixon and edwarnicke to follow up about deployability concerns
    4. colindixon to connect cardinal with the OpenNMS guys to see if there's a way to keep some work in common
  3. edwarnicke
    1. colindixon and edwarnicke to follow up about deployability concerns
  4. tykeal
    1. tykeal to write this up and send an e-mail about this
  5. UNASSIGNED
    1. zxiiro will look more into maven central now that we're at least signing things
    2. phrobb to send out a thread about a hackfest at the end of june


People present (lines said)

  1. colindixon (110)
  2. odl_meetbot (19)
  3. LuisGomez (9)
  4. abhijitkumbhare (9)
  5. edwarnicke (8)
  6. gkaempfer (7)
  7. mohnish_ (7)
  8. dfarrell07 (6)
  9. rovarga__ (6)
  10. ChrisPriceAB (3)
  11. gzhao (2)
  12. anipbu (2)
  13. Gaurav_ (1)
  14. tykeal (1)
  15. dfarrell07_sick (1)


Generated by MeetBot 0.1.4.