#opendaylight-meeting: tsc

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

Meeting summary

  1. agenda bashing and roll call (colindixon, 17:00:25)
    1. gkaempfer (gkaempfer, 17:00:32)
    2. colindixon (colindixon, 17:00:43)
    3. Daniel Farrell (dfarrell07, 17:01:07)
    4. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=45906#Agenda today's agenda in it's usual place (colindixon, 17:01:08)
    5. Tony Tkacik (ttkacik, 17:01:16)
    6. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-04-21-17.00.html last meetings' minutes (colindixon, 17:01:21)
    7. edwarnicke (edwarnicke, 17:01:23)
    8. abhijitkumbhare (abhijitkumbhare, 17:01:42)
    9. vishnoianil (vishnoianil, 17:01:59)
    10. mohnish anumala (mohnish_, 17:03:17)
    11. https://lists.opendaylight.org/pipermail/discuss/2016-May/006476.html mail trying to move carbon planning forward (colindixon, 17:03:24)
    12. #link https://lists.opendaylight.org/pipermail/discuss/2016-May/006476.html colindixon made the changes here to clarify the boron release plan (colindixon, 17:03:35)
    13. https://lists.opendaylight.org/pipermail/discuss/2016-May/006475.html (jamoluhrsen, 17:04:00)
    14. https://lists.opendaylight.org/pipermail/discuss/2016-May/006475.html planning openflow project reorganization (colindixon, 17:04:23)
    15. ACTION: colindixon to reach out to tykeal to write up and send an e-mail about signing commits in gerrit (colindixon, 17:04:29)
    16. ACTION: colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron? (colindixon, 17:04:30)
    17. ACTION: colindixon to get anton to post JSON-RPC plugin slides here: https://wiki.opendaylight.org/view/Project_Proposals:JSON-RPC2.0-plugin (colindixon, 17:04:31)
    18. ACTION: tykeal to e-mail the TSC with the list of semi-archived silos to figure out how to proceed (colindixon, 17:04:54)
    19. for quorum we have colindixon gkaempfer dfarrell07 edwarnicke abhijitkumbhare vishnoianil ttkacik mohnish_ we have quorum (phrobb, 17:06:02)

  2. new TSC members (colindixon, 17:06:20)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-May/005170.html CAL elections have finished (colindixon, 17:06:29)
    2. CALs are: colindixon, ttkacik, abhijitkumbhare, edwarnicke (colindixon, 17:06:48)
    3. abhijitkumbhare introduces himself he's been around a while and mostly involved in openflowplugin (colindixon, 17:07:31)
    4. ttkacik has also been around a while—since the beginning of OpenDaylight (colindixon, 17:07:51)
    5. https://lists.opendaylight.org/pipermail/tsc/2016-May/005158.html vishnoianil is replacing LuisGomez as Brocade's platinum designate (colindixon, 17:08:32)
    6. vishnoianil has also been around forever, was the first non-Cisco committer and worked before the first code drop (colindixon, 17:08:54)

  3. MPLS-TP creation reviews (colindixon, 17:09:14)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-March/004956.html MPLS-TP Service creation review (colindixon, 17:09:32)
    2. https://lists.opendaylight.org/pipermail/tsc/2016-April/005033.html [Creation Review] MPLS-TP solution (colindixon, 17:09:54)
    3. ACTION: colindixon to drive the MPLS-TP creation reviews to conclusion (colindixon, 17:10:09)

  4. TSC list discussions and votes (colindixon, 17:11:09)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-May/005152.html Requesting more frequent releases from ODL (colindixon, 17:11:12)
    2. colindixon asks if we've figured out how to meet Brady's needs in the short term (colindixon, 17:11:55)
    3. dfarrell07 says it's mixed for one installer in OPNFV (Apex) they are doing the right thing and it works, for others, things aren't as friendly (colindixon, 17:12:23)
    4. dfarrell07 says in the short term, it could work to use autorelease builds (colindixon, 17:12:38)
    5. there's a job to be done around cleaning up autorelease tests to allow for a quick glance evaluation of autorelease builds, integration/test is working on that (colindixon, 17:13:23)
    6. https://lists.opendaylight.org/pipermail/tsc/2016-May/005149.html split-out projects and lifecycle states (colindixon, 17:14:46)
    7. ACTION: dfarrell07 to ask Brady if what we're planning is meeting his needs (colindixon, 17:15:02)

  5. events (colindixon, 17:15:57)
    1. https://www.opendaylight.org/global-events (colindixon, 17:16:08)
    2. the LF events people have come back with the week after the OPNFV summit in berlin as the best time for the Hackfest, Tu/W (6/28-29) at the doubletree in San Jose, the room would hold 100 people (colindixon, 17:17:04)
    3. that's a few days before API freeze for offset 2 and a few days before code freeze for offset 0 (colindixon, 17:17:26)
    4. edwarnicke points out that it's hard travel to do those two things back to back (colindixon, 17:18:34)
    5. colindixon asks if we could move it 2 or 3 weeks earlier, phrobb says not really, no space (colindixon, 17:18:53)
    6. especially when one of those two things is in Europe and the other NA West Coast ;) (edwarnicke, 17:18:58)
    7. dfarrell07 asks if it could be W/Th (6/29-6/30 to make travel a bit easier), that means that the second day would be the deadlines mentioned above (offset 0 M5, offset 2 M4) (colindixon, 17:21:10)
    8. dfarrell07 asks if it could be Th/F, people say try to avoid Fridays to end up traveling on the Saturday, also July 4th (in the US) and July 1st (in Canada) means it might be cutting into people's vacations (colindixon, 17:22:46)
    9. ACTION: phrobb to send e-mail asking if the 6/29-30 date works for people for a hackfest in the south bay (colindixon, 17:24:10)
    10. https://www.opendaylight.org/events/2016-09-27-000000-2016-09-29-000000/opendaylight-summit-2016 the CFP for the OpenDayligtht summit closes TOMORROW (colindixon, 17:24:47)
    11. we're in the high-30s now, but we're looking to be over 50, so it's actually looking pretty good (colindixon, 17:25:03)
    12. https://www.opendaylight.org/events/2016-06-20-000000-2016-06-23-000000/opnfv-summit OPNFV summit in Berlin starts on 6/20 (colindixon, 17:25:25)

  6. boron (colindixon, 17:25:38)
    1. There are plans to upgrade the distribution to Karaf 3.0.6 with a patch in odlparent. Projects should test their projects against the patch if possible. (anipbu, 17:26:04)
    2. https://git.opendaylight.org/gerrit/26323 <--- Patch upgrading Karaf (anipbu, 17:26:09)
    3. https://wiki.opendaylight.org/view/Weather#Upgrade_to_Karaf_3.0.x <--- Weather Item for Karaf Upgrade (anipbu, 17:26:13)
    4. DIDM is currently breaking Autorelease. We are tracking it on bug 5843 (anipbu, 17:26:31)
    5. https://bugs.opendaylight.org/show_bug.cgi?id=5843 <--- Bug Tracking Breakages (anipbu, 17:26:36)
    6. Boron M2 Offset 2 is due today. Please send your status report. (anipbu, 17:26:49)
    7. https://wiki.opendaylight.org/view/Simultaneous_Release:Boron_Release_Plan#M2:_Final_Release_Plan <--- Status Template (anipbu, 17:27:02)
    8. https://lists.opendaylight.org/pipermail/tsc/2016-April/005139.html Vratko asking questions about a stable distribution in Boron (colindixon, 17:27:51)
    9. https://wiki.opendaylight.org/view/Simultaneous_Release:Boron_Release_Plan#Stable_and_Extended_Features stable feature requirements (jamoluhrsen, 17:29:29)
    10. ACTION: colindixon to ask offset 0 projects when/if they could have stable features and what they would be (colindixon, 17:29:31)
    11. dfarrell07 says that this came up in the integration call and they concluded that it might be too late to have stable features in offset 0 projects which would prevent almost everything (colindixon, 17:30:59)
    12. jamoluhrsen notes that stable feature requirements are really tough (colindixon, 17:31:09)
    13. colindixon notes that he's pretty sure that the MD-SAL meets all these requirements, and he's surprised that it couldn't do it in Boron (colindixon, 17:33:09)
    14. rovarga notes that it's not so much that it couldn't meet the requirements now, but that some new feature changes (expected in Boron) might or might not meet those requirements today (colindixon, 17:34:07)
    15. rovarga also notes that they will need to make sure there are no design issues in the APIs that would be stuck there to be stable (colindixon, 17:35:05)

  7. stable/beryllium (colindixon, 17:35:16)
    1. We initially targeted Beryllium SR2 Release on 4/28, but our latest build has OPENFLOWPLUGIN test failures in the integration distribution test job. (anipbu, 17:36:06)
    2. https://wiki.opendaylight.org/view/Simultaneous_Release/Beryllium/SR2/Status <--- Status Summary (anipbu, 17:36:10)
    3. https://bugs.opendaylight.org/show_bug.cgi?id=5523 <--- OpenFlow Li Plugin Cluster Bug (anipbu, 17:36:15)
    4. it looks like there are regressions with the new openflow plugin tests with clustering (colindixon, 17:36:18)
    5. https://git.opendaylight.org/gerrit/#/c/38369/ <--- Proposed Patch (anipbu, 17:36:18)
    6. colindixon asks if we should push SR2 out more than a week (already a week today) and fix the bug, or try to keep closer to schedule to avoid the regression (colindixon, 17:38:54)
    7. jamoluhrsen notes that "real customers from real companies that are using the -li plugin" (colindixon, 17:39:08)
    8. it sounds the consensus is to wait for a fix (colindixon, 17:39:30)
    9. ACTION: abhijitkumbhare to either review or find people to review the openflowplugin patch to fix Be-SR2 (colindixon, 17:41:44)

  8. system integration and test (colindixon, 17:41:48)
    1. we had 9 system test waiver requests in Beryllium, we only have 1 so far for Carbon (colindixon, 17:42:24)
    2. please get them in (colindixon, 17:42:33)

  9. infrastructure (colindixon, 17:42:45)
    1. the intent was to move the jenkins sandbox to the private cloud this weekend, but an issue was found and that's delaying things (colindixon, 17:43:29)
    2. continued work on build slaves, lots of changes around streamlined Vagrant definitions as well as soon docs on how to use the Vagrant definitions outside our CI (colindixon, 17:44:07)
    3. zxiiro says if you're using JJB, they release 1.5 this week, so there's an update to look at (colindixon, 17:44:33)

  10. Mohamed El-Serngawy as a committer on AAA (colindixon, 17:45:06)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-May/005160.html (colindixon, 17:45:12)
    2. VOTE: Voted on "shall the TSC approve Mohamed El-Serngawy as a committer on AAA?" Results are, +1: 7 (colindixon, 17:47:21)
    3. note ttkacik voted verbally +1 (colindixon, 17:47:30)
    4. AGREED: Mohamed El-Serngawy in now a committer on AAA (colindixon, 17:47:37)

  11. OpenDove Archive Review (colindixon, 17:47:58)
    1. https://wiki.opendaylight.org/view/Archive_Proposals/Open_DOVE (colindixon, 17:48:04)
    2. https://lists.opendaylight.org/pipermail/tsc/2016-March/004953.html posted on 3/28/2016 (colindixon, 17:48:15)
    3. colindixon notes that the project has been inactive for 18 months and the one remaining active committer (Ryan Moats) agreed with course of action (colindixon, 17:49:31)
    4. VOTE: Voted on "shall the TSC move the Open DOVE project to archived?" Results are, +1: 8 (colindixon, 17:50:32)
    5. AGREED: the Open DOVE project is now archived (colindixon, 17:50:42)

  12. TSC chair elections (colindixon, 17:50:57)
    1. ACTION: phrobb to kick off elections for TSC chair and how long the term will be, it's the same clause that specifies that term, so the board's existing waiver would likely apply (colindixon, 17:53:07)
    2. ACTION: phrobb to inform the board that we're assuming the waiver applies to both (colindixon, 17:53:20)
    3. AGREED: the TSC agrees that the next TSC chair's term should match the current TSC term (ending at the end of Boron) (colindixon, 17:55:25)

  13. TSC election planning (colindixon, 17:55:45)
    1. we have another CAL election in ~5 months (colindixon, 17:55:54)
    2. we need a complete voting system for the new mechanics that works by then (colindixon, 17:56:06)
    3. this includes tooling, picking represented groups, and the properties of those groups (colindixon, 17:56:39)
    4. ACTION: dfarrell07 to drive forward tooling and planning for the next TSC election (colindixon, 17:57:33)
    5. edwarnicke notes that the framework seems to have agreement from everyone, colindixon notes that the only posisble complaint was that it might be too compliex (colindixon, 17:58:01)
    6. dfarrell07 is planning to help explain things simply so that others can understant (colindixon, 17:58:53)

  14. thanking Luis Gomez for his service (colindixon, 17:59:04)
    1. everyone thanks Luis for his time on the TSC and everything he's done for the project, OpenDaylight would not be where it is today with him (colindixon, 17:59:44)
    2. LuisGomez isn't going anywhere though (colindixon, 17:59:51)
    3. LuisGomez says it's really all about the community (colindixon, 18:00:08)

  15. cookies (colindixon, 18:00:10)


Meeting ended at 18:00:14 UTC (full logs).

Action items

  1. colindixon to reach out to tykeal to write up and send an e-mail about signing commits in gerrit
  2. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
  3. colindixon to get anton to post JSON-RPC plugin slides here: https://wiki.opendaylight.org/view/Project_Proposals:JSON-RPC2.0-plugin
  4. tykeal to e-mail the TSC with the list of semi-archived silos to figure out how to proceed
  5. colindixon to drive the MPLS-TP creation reviews to conclusion
  6. dfarrell07 to ask Brady if what we're planning is meeting his needs
  7. phrobb to send e-mail asking if the 6/29-30 date works for people for a hackfest in the south bay
  8. colindixon to ask offset 0 projects when/if they could have stable features and what they would be
  9. abhijitkumbhare to either review or find people to review the openflowplugin patch to fix Be-SR2
  10. phrobb to kick off elections for TSC chair and how long the term will be, it's the same clause that specifies that term, so the board's existing waiver would likely apply
  11. phrobb to inform the board that we're assuming the waiver applies to both
  12. dfarrell07 to drive forward tooling and planning for the next TSC election


Action items, by person

  1. abhijitkumbhare
    1. abhijitkumbhare to either review or find people to review the openflowplugin patch to fix Be-SR2
  2. colindixon
    1. colindixon to reach out to tykeal to write up and send an e-mail about signing commits in gerrit
    2. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
    3. colindixon to get anton to post JSON-RPC plugin slides here: https://wiki.opendaylight.org/view/Project_Proposals:JSON-RPC2.0-plugin
    4. colindixon to drive the MPLS-TP creation reviews to conclusion
    5. colindixon to ask offset 0 projects when/if they could have stable features and what they would be
  3. dfarrell07
    1. dfarrell07 to ask Brady if what we're planning is meeting his needs
    2. dfarrell07 to drive forward tooling and planning for the next TSC election
  4. phrobb
    1. phrobb to send e-mail asking if the 6/29-30 date works for people for a hackfest in the south bay
    2. phrobb to kick off elections for TSC chair and how long the term will be, it's the same clause that specifies that term, so the board's existing waiver would likely apply
    3. phrobb to inform the board that we're assuming the waiver applies to both
  5. tykeal
    1. colindixon to reach out to tykeal to write up and send an e-mail about signing commits in gerrit
    2. tykeal to e-mail the TSC with the list of semi-archived silos to figure out how to proceed


People present (lines said)

  1. colindixon (105)
  2. odl_meetbot (15)
  3. anipbu (12)
  4. jamoluhrsen (8)
  5. abhijitkumbhare (5)
  6. mohnish_ (4)
  7. dfarrell07 (4)
  8. edwarnicke (4)
  9. vishnoianil (4)
  10. gkaempfer (3)
  11. tykeal (3)
  12. phrobb (2)
  13. ttkacik (2)
  14. gzhao (1)
  15. LuisGomez (1)
  16. zxiiro (1)


Generated by MeetBot 0.1.4.