#opendaylight-meeting: tsc

Meeting started by colindixon at 18:02:36 UTC (full logs).

Meeting summary

  1. agenda bashing and roll call (colindixon, 18:02:39)
    1. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=41567#Agenda today's agenda (colindixon, 18:02:54)
    2. mohnish anumala (mohnish_, 18:02:55)
    3. colindixon (colindixon, 18:02:58)
    4. Chris Price (ChrisPriceAB, 18:03:00)
    5. Daniel Farrell (dfarrell07, 18:03:00)
    6. https://lists.opendaylight.org/pipermail/tsc/2016-February/004640.html projects missing system test according to jamoluhrsen (colindixon, 18:03:10)
    7. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-02-04-18.00.html last week's minutes (colindixon, 18:03:15)
    8. LuisGomez (LuisGomez, 18:03:41)
    9. ACTION: colindixon to follow up with GBP updating their wiki pages to be mature (colindixon, 18:03:51)
    10. ACTION: colindixon to keep boron planning on our minds (colindixon, 18:04:15)
    11. ACTION: colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron? (colindixon, 18:04:20)
    12. ACTION: colindixon to follow the two OpenFlow plugin implementations issue to figure out lessons learned and how to avoid similar problems in the future (colindixon, 18:04:26)
    13. ACTION: colindixon and phrobb to draft up a Boron release plan that looks like Beryllium and hits before the ODL Summit just in case (colindixon, 18:04:49)
    14. ACTION: rovarga to follow up with a counter-proposal with the new workflow ;-) (colindixon, 18:05:03)

  2. TSC election (colindixon, 18:05:43)
    1. there has been no feedback from the board about our having adopted a preliminary strategy to do away with the platinum designate exception (colindixon, 18:06:37)
    2. edwarnicke (edwarnicke, 18:06:44)

  3. events (colindixon, 18:07:09)
    1. https://www.opendaylight.org/global-events the events page (colindixon, 18:07:18)
    2. edwarnicke notes that the the FD.io consortium launched today and there is a project proposal for it already https://lists.opendaylight.org/pipermail/project-proposals/2016-February/000401.html (colindixon, 18:08:43)
    3. phrobb- asks for people to please submit something forward for the ODL mini-summit at ONS (colindixon, 18:08:57)
    4. developer design forum coming up, we need more presentations, phrobb- says please at least register (we currently have only 38) (colindixon, 18:09:30)
    5. register for the dev design forum on 2/29-3/1 here: https://www.opendaylight.org/events/2016-02-29-000000-2016-03-01-000000/opendaylight-developer-design-forum (colindixon, 18:09:36)
    6. the ONS CFP for the ODL minisummit will be open through friday (colindixon, 18:10:28)
    7. dfarrell07 says that the schedule for ONS looks like ODL talks are all stacked on top of each other while ONOS is more spread out (colindixon, 18:10:57)
    8. ACTION: phrobb- neela and colindixon to poke at getting a better schedule for ONS (colindixon, 18:11:16)

  4. boron (colindixon, 18:11:47)
    1. phrobb- says he's sending tentative dates for a more-of-the-same release for boron (colindixon, 18:12:06)
    2. Remind all committers that all patches to master need to be re-verified after stable branch cut before they can be safely merged (anipbu, 18:12:30)
    3. all patches to master need to be reverified after the stable branch cut (colindixon, 18:12:40)
    4. https://lists.opendaylight.org/pipermail/release/2016-February/005467.html <-- 3 patches pending in ofconfig, snmp4sdn, tsdr (anipbu, 18:12:42)

  5. beryllium (colindixon, 18:13:24)
    1. https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=2030147923 blocking bugs tracking spreadsheet (colindixon, 18:13:41)
    2. we've been doing release reviews all week, they will continue until Monday (colindixon, 18:13:59)
    3. anipbu notes that we still have some blocking bugs (colindixon, 18:14:05)
    4. anipbu advocates waiting to spin RC3 until we have all the blocking bugs fixed since RC3 will be tagged as Beryllium (colindixon, 18:14:46)
    5. https://bugs.opendaylight.org/show_bug.cgi?id=4527 anipbu asks if this is actually a blocker and if we are making progress (colindixon, 18:15:18)
    6. ACTION: yamahata to create an API waiver per these instructions for BUG-4527 https://wiki.opendaylight.org/view/Simultaneous_Release/Beryllium/Waiver/API (colindixon, 18:15:42)
    7. VTN is ok for merging the patch for bug 4527. (hideyuki, 18:16:59)
    8. vina_ermagan says this patch isn't a big deal with lisp and they could go either way (colindixon, 18:17:02)
    9. ChrisPriceAB says that OPNFV would like it, but an SR would be OK (colindixon, 18:17:44)
    10. hideyuki says it's not a blocker for VTN (colindixon, 18:17:50)
    11. vishnoianil says he'll update things from the OVSDB perspective shortly, he doesn't think it will be a blocker (colindixon, 18:18:22)
    12. ACTION: anipbu will follow up with GBP to see what's going on (colindixon, 18:18:42)
    13. colindixon agrees with anipbu that we should wait to spin RC3 until we find out if it's blocking, but if it's a non-blocker, colindixon says it probably makes sense to patch it in SR1 (colindixon, 18:20:16)
    14. colindixon says there are 6 possible blocking bugs: 3866, 1435, 4678, 5304, 4527, and another one to be opened and fixed by vishnoi anil shortly (colindixon, 18:21:57)
    15. the new bug is that when you have a 3-node cluster discovering links via LLDP detecting message sent by other nodes as spoofed, the fixes are pretty straightforward (colindixon, 18:23:05)
    16. ACTION: anipbu to make sure the bug is filed with tracked with help from vishnoianil (colindixon, 18:23:37)
    17. anipbu notes that that we were seeing CSIT failures in RC2.1, spinning RC2.2 to see if they go away (colindixon, 18:24:38)
    18. jamoluhrsen says that it's only been in RC2, it's weird things are massively slower to run, this is likely what's causing BUG 5305 (colindixon, 18:25:08)
    19. hideyuki says the patch for 4678 was just merged (colindixon, 18:25:46)
    20. ACTION: hideyuki to update the sheet with the patch for 4678 and move it to to be verified (colindixon, 18:26:26)
    21. https://git.opendaylight.org/gerrit/#/c/32602/ the patch for bug 1435 is still waiting for review (colindixon, 18:26:51)
    22. colindixon says that BUG-1435 is not a blocker per the MD-SAL meeting (colindixon, 18:28:13)
    23. colindixon says that BUG-3866 is also not a blocker per the MD-SAL meeting (colindixon, 18:28:45)
    24. new lldp issue blocker : https://bugs.opendaylight.org/show_bug.cgi?id=5327 (vishnoianil, 18:28:58)
    25. zxiiro asks what we're building tonight, are we building an actual release? colindixon says to build the final when we have no known blocking bugs, if that's tonight, that's tonight (colindixon, 18:31:06)
    26. ACTION: anipbu to send a note clarifying our plan for tonight (and also note that stable/beryllium might be locked down) (colindixon, 18:31:33)
    27. https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=45904332 <--Release Review (anipbu, 18:31:50)
    28. https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=45904332 release review schedule, please accept the invite, show up on time, and have your two templates filled out (colindixon, 18:32:08)

  6. system integration and test (colindixon, 18:32:24)
    1. jamoluhrsen has nothing else to add beyond blocking bugs (colindixon, 18:32:52)
    2. jamoluhrsen asks that for release reviews to have bugs filed for failures and/or have them logged as non-issues (colindixon, 18:33:11)
    3. colindixon notes that in Boron we should probably require that tests be expected to succeed, if it's flaky, fix it or disable it (colindixon, 18:34:14)

  7. infrastructure (colindixon, 18:34:55)
    1. amazingly, things seem to be working well, thanks to zxiiro and tykeal (colindixon, 18:35:07)
    2. test code guidelines we hope to make Boron requirements (jamoluhrsen, 18:35:12)
    3. https://wiki.opendaylight.org/view/Integration/Test/Test_Case_Expectations (jamoluhrsen, 18:35:13)

  8. Kalaiselvi K as a committer on LACP (colindixon, 18:35:41)
    1. https://lists.opendaylight.org/pipermail/lacp-dev/2015-December/000104.html ask for the promotion (colindixon, 18:36:03)
    2. https://git.opendaylight.org/gerrit/#/q/project:lacp+owner:Kalaiselvi_K%2540Dell.com+status:merged contributions (colindixon, 18:36:44)
    3. there's a majority with mohnish_'s verbal +1, rajesh and venakt voting via mail (colindixon, 18:37:53)
    4. colindixon notes that he's surprised it took this long (colindixon, 18:38:45)
    5. VOTE: Voted on "shall the TSC confirm Kalaiselvi K as a committer on LACP?" Results are, +1: 5 (colindixon, 18:39:04)
    6. edwarnicke verbally votes +1 (colindixon, 18:39:14)
    7. AGREED: Kalaiselvi K is now a committer on LACP (colindixon, 18:39:32)

  9. boron planning (colindixon, 18:40:58)
    1. at this point colindixon thinks we're waiting on concrete plans for either a Beryllium-style release plan or a new, faster release release plan (colindixon, 18:41:25)
    2. dfarrell07 has been doing tools research for implementing an election based on recently mostly-approved framework (dfarrell07, 18:41:58)
    3. phrobb is getting feedback from board (dfarrell07, 18:42:10)
    4. dfarrell07 has been doing some tools research and there's some promising evidence that we can actually implement the ne framework (colindixon, 18:42:58)
    5. dfarrell07, colindixon, and edwarnicke note that they feel like picking represented groups hasn't had any more activity and so waiting to pick one makes sense (colindixon, 18:43:57)
    6. colindixon asks if we want to tentatively just have an at-large election for the 4 seats to try to have an election sooner rather than later (colindixon, 18:45:18)
    7. dfarrell07 says he'd like to see us wait, he doesn't see any real problems from waiting (colindixon, 18:45:46)
    8. edwarnicke notes that he'd like to see us have time to get it right so it would make sense to not delay an election and force things (colindixon, 18:46:45)
    9. rovarga said we had wanted to vote on boron with the new TSC, and so the currently standing method would allow that (colindixon, 18:47:10)
    10. dfarrell07 agrees that if we want to have the new TSC approve the Boron planning, we really need to have old-style election (colindixon, 18:49:45)
    11. colindixon asks if we could do an old-style election that lasts until when the election should have happened, e.g., October rather than 12 months (colindixon, 18:50:59)
    12. colindixon thinks phrobb- also suggests that maybe we could have the at-large part of the new election now, then the full new election next time (colindixon, 18:52:29)
    13. mohnish_ just asked if we could get feedback from the board before we vote to make sure we don't have to revisit this again (colindixon, 18:55:38)
    14. dfarrell07 summarizes things: (1) do old-style election for the 4 at-large members now with terms ending around the boron release, (2) that will then have a new-style election after that, (3) this would be conditioned on the platinum designate waiver being granted by the board for this election based on our plans for the next election (colindixon, 18:57:28)
    15. VOTE: Voted on "shall the TSC move to have an "old-style" election as soon as is reasonable and once we know what the term length will be and getting the waiver from the board?" Results are, 0: 1, +1: 6 (colindixon, 18:59:54)
    16. AGREED: we will have an odl-style election as soon as is reasonable (colindixon, 19:01:03)

  10. welcome gideon (colindixon, 19:01:08)
    1. gkaempfer (Gideon Kaempfer) of HP is their new TSC representative (colindixon, 19:02:38)

  11. cookies (colindixon, 19:03:29)


Meeting ended at 19:03:35 UTC (full logs).

Action items

  1. colindixon to follow up with GBP updating their wiki pages to be mature
  2. colindixon to keep boron planning on our minds
  3. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
  4. colindixon to follow the two OpenFlow plugin implementations issue to figure out lessons learned and how to avoid similar problems in the future
  5. colindixon and phrobb to draft up a Boron release plan that looks like Beryllium and hits before the ODL Summit just in case
  6. rovarga to follow up with a counter-proposal with the new workflow ;-)
  7. phrobb- neela and colindixon to poke at getting a better schedule for ONS
  8. yamahata to create an API waiver per these instructions for BUG-4527 https://wiki.opendaylight.org/view/Simultaneous_Release/Beryllium/Waiver/API
  9. anipbu will follow up with GBP to see what's going on
  10. anipbu to make sure the bug is filed with tracked with help from vishnoianil
  11. hideyuki to update the sheet with the patch for 4678 and move it to to be verified
  12. anipbu to send a note clarifying our plan for tonight (and also note that stable/beryllium might be locked down)


Action items, by person

  1. anipbu
    1. anipbu will follow up with GBP to see what's going on
    2. anipbu to make sure the bug is filed with tracked with help from vishnoianil
    3. anipbu to send a note clarifying our plan for tonight (and also note that stable/beryllium might be locked down)
  2. colindixon
    1. colindixon to follow up with GBP updating their wiki pages to be mature
    2. colindixon to keep boron planning on our minds
    3. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
    4. colindixon to follow the two OpenFlow plugin implementations issue to figure out lessons learned and how to avoid similar problems in the future
    5. colindixon and phrobb to draft up a Boron release plan that looks like Beryllium and hits before the ODL Summit just in case
    6. phrobb- neela and colindixon to poke at getting a better schedule for ONS
  3. hideyuki
    1. hideyuki to update the sheet with the patch for 4678 and move it to to be verified
  4. phrobb
    1. colindixon and phrobb to draft up a Boron release plan that looks like Beryllium and hits before the ODL Summit just in case
    2. phrobb- neela and colindixon to poke at getting a better schedule for ONS
  5. rovarga
    1. rovarga to follow up with a counter-proposal with the new workflow ;-)
  6. vishnoianil
    1. anipbu to make sure the bug is filed with tracked with help from vishnoianil


People present (lines said)

  1. colindixon (104)
  2. odl_meetbot (20)
  3. dfarrell07 (12)
  4. mohnish_ (5)
  5. anipbu (5)
  6. ChrisPriceAB (4)
  7. jamoluhrsen (4)
  8. LuisGomez (3)
  9. abhijitkumbhare (3)
  10. edwarnicke (2)
  11. gkaempfer (1)
  12. rovarga (1)
  13. hideyuki (1)
  14. zxiiro (1)
  15. vishnoianil (1)
  16. phrobb (0)
  17. phrobb- (0)


Generated by MeetBot 0.1.4.