18:02:36 #startmeeting tsc 18:02:36 Meeting started Thu Feb 11 18:02:36 2016 UTC. The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html. 18:02:36 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:02:36 The meeting name has been set to 'tsc' 18:02:39 #topic agenda bashing and roll call 18:02:40 You might want to rechair phrobb 18:02:48 #chair anipbu phrobb- 18:02:48 Current chairs: anipbu colindixon phrobb- 18:02:54 #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=41567#Agenda today's agenda 18:02:55 #info mohnish anumala 18:02:58 #info colindixon 18:03:00 #info Chris Price 18:03:00 #info Daniel Farrell 18:03:10 #link https://lists.opendaylight.org/pipermail/tsc/2016-February/004640.html projects missing system test according to jamoluhrsen 18:03:15 phrobb- has become phrobb 18:03:15 #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-02-04-18.00.html last week's minutes 18:03:24 #chair anipbu phrobb- phrobb 18:03:24 Current chairs: anipbu colindixon phrobb phrobb- 18:03:41 #info LuisGomez 18:03:51 #action colindixon to follow up with GBP updating their wiki pages to be mature 18:04:15 #action colindixon to keep boron planning on our minds 18:04:20 #action colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron? 18:04:26 #action colindixon to follow the two OpenFlow plugin implementations issue to figure out lessons learned and how to avoid similar problems in the future 18:04:49 #action colindixon and phrobb to draft up a Boron release plan that looks like Beryllium and hits before the ODL Summit just in case 18:05:03 #action rovarga to follow up with a counter-proposal with the new workflow ;-) 18:05:43 #topic TSC election 18:05:56 phrobb: are you there? 18:06:37 #info there has been no feedback from the board about our having adopted a preliminary strategy to do away with the platinum designate exception 18:06:42 colindixon: I see 5 18:06:44 #info edwarnicke 18:06:47 6 18:07:09 #topic events 18:07:18 #link https://www.opendaylight.org/global-events the events page 18:08:43 #link 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 18:08:57 #info phrobb- asks for people to please submit something forward for the ODL mini-summit at ONS 18:09:30 #info developer design forum coming up, we need more presentations, phrobb- says please at least register (we currently have only 38) 18:09:36 #link 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 18:10:28 #info the ONS CFP for the ODL minisummit will be open through friday 18:10:57 #info 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 18:11:16 #action phrobb- neela and colindixon to poke at getting a better schedule for ONS 18:11:47 #topic boron 18:12:06 #info phrobb- says he's sending tentative dates for a more-of-the-same release for boron 18:12:30 #info Remind all committers that all patches to master need to be re-verified after stable branch cut before they can be safely merged 18:12:40 #info all patches to master need to be reverified after the stable branch cut 18:12:42 #link https://lists.opendaylight.org/pipermail/release/2016-February/005467.html <-- 3 patches pending in ofconfig, snmp4sdn, tsdr 18:13:24 #topic beryllium 18:13:32 #link https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=2030147923 18:13:34 #undo 18:13:34 Removing item from minutes: 18:13:41 #link https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=2030147923 blocking bugs tracking spreadsheet 18:13:59 #Info we've been doing release reviews all week, they will continue until Monday 18:14:05 #info anipbu notes that we still have some blocking bugs 18:14:21 #link https://bugs.opendaylight.org/show_bug.cgi?id=4527 18:14:39 #Info anipbu advocates waiting to spin RC3 until we have all the blocking bugs fixed since RC3 will be tagged as Beryllium 18:14:42 #undo 18:14:42 Removing item from minutes: 18:14:43 #undo 18:14:43 Removing item from minutes: 18:14:46 #Info anipbu advocates waiting to spin RC3 until we have all the blocking bugs fixed since RC3 will be tagged as Beryllium 18:15:18 #link https://bugs.opendaylight.org/show_bug.cgi?id=4527 anipbu asks if this is actually a blocker and if we are making progress 18:15:42 #action yamahata to create an API waiver per these instructions for BUG-4527 https://wiki.opendaylight.org/view/Simultaneous_Release/Beryllium/Waiver/API 18:16:59 #info VTN is ok for merging the patch for bug 4527. 18:17:02 #info vina_ermagan says this patch isn't a big deal with lisp and they could go either way 18:17:44 #info ChrisPriceAB says that OPNFV would like it, but an SR would be OK 18:17:50 #info hideyuki says it's not a blocker for VTN 18:18:22 #info vishnoianil says he'll update things from the OVSDB perspective shortly, he doesn't think it will be a blocker 18:18:42 #action anipbu will follow up with GBP to see what's going on 18:20:16 #Info 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 18:21:57 #info 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 18:23:05 #info 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 18:23:37 #action anipbu to make sure the bug is filed with tracked with help from vishnoianil 18:24:22 #info anipbu notes that that we were seeing CSIT failures in RC2.2, spinning RC2.2 to see if they go away 18:24:31 #undo 18:24:31 Removing item from minutes: 18:24:38 #info anipbu notes that that we were seeing CSIT failures in RC2.1, spinning RC2.2 to see if they go away 18:25:08 #Info 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 18:25:46 #info hideyuki says the patch for 4678 was just merged 18:26:01 #action hideyuki to update the sheet with the patch and move it to to be verified 18:26:13 #undo 18:26:13 Removing item from minutes: 18:26:26 #action hideyuki to update the sheet with the patch for 4678 and move it to to be verified 18:26:51 #link https://git.opendaylight.org/gerrit/#/c/32602/ the patch for bug 1435 is still waiting for review 18:27:42 #action rovarga to check with TomP and/or Tony about whether 14345 is actually a blocker 18:27:52 #undo 18:27:52 Removing item from minutes: 18:28:13 #info colindixon says that BUG-1435 is not a blocker per the MD-SAL meeting 18:28:45 #Info colindixon says that BUG-3866 is also not a blocker per the MD-SAL meeting 18:28:58 #info new lldp issue blocker : https://bugs.opendaylight.org/show_bug.cgi?id=5327 18:31:06 #info 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 18:31:33 #action anipbu to send a note clarifying our plan for tonight (and also note that stable/beryllium might be locked down) 18:31:50 https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=45904332 <--Release Review 18:32:08 #link 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 18:32:24 #topic system integration and test 18:32:52 #info jamoluhrsen has nothing else to add beyond blocking bugs 18:33:11 #info jamoluhrsen asks that for release reviews to have bugs filed for failures and/or have them logged as non-issues 18:34:14 #info colindixon notes that in Boron we should probably require that tests be expected to succeed, if it's flaky, fix it or disable it 18:34:31 colindixon, here is link: https://wiki.opendaylight.org/view/Integration/Test/Test_Case_Expectations 18:34:48 ack 18:34:55 #topic infrastructure 18:35:07 #info amazingly, things seem to be working well, thanks to zxiiro and tykeal 18:35:12 #info test code guidelines we hope to make Boron requirements 18:35:13 #link https://wiki.opendaylight.org/view/Integration/Test/Test_Case_Expectations 18:35:41 #topic Kalaiselvi K as a committer on LACP 18:36:03 #link https://lists.opendaylight.org/pipermail/lacp-dev/2015-December/000104.html ask for the promotion 18:36:44 #link https://git.opendaylight.org/gerrit/#/q/project:lacp+owner:Kalaiselvi_K%2540Dell.com+status:merged contributions 18:37:35 Lots of good-looking patches 18:37:53 #info there's a majority with mohnish_'s verbal +1, rajesh and venakt voting via mail 18:38:33 #startvote shall the TSC confirm Kalaiselvi K as a committer on LACP? -1, 0, +1 18:38:33 Begin voting on: shall the TSC confirm Kalaiselvi K as a committer on LACP? Valid vote options are -1, 0, +1. 18:38:33 Vote using '#vote OPTION'. Only your last vote counts. 18:38:36 #vote +1 18:38:37 #vote +1 18:38:37 #vote +1 18:38:38 #vote +1 18:38:39 #vote +1 18:38:45 #Info colindixon notes that he's surprised it took this long 18:39:04 #endvote 18:39:04 Voted on "shall the TSC confirm Kalaiselvi K as a committer on LACP?" Results are 18:39:04 +1 (5): ChrisPriceAB, colindixon, LuisGomez, dfarrell07, mohnish_ 18:39:14 #info edwarnicke verbally votes +1 18:39:29 congrats Kalaiselvi! 18:39:32 #agreed Kalaiselvi K is now a committer on LACP 18:40:00 Congrats! 18:40:58 #topic boron planning 18:41:25 #Info 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 18:41:57 #topic tsc election refactoring 18:41:58 #info dfarrell07 has been doing tools research for implementing an election based on recently mostly-approved framework 18:42:10 #info phrobb is getting feedback from board 18:42:58 #info dfarrell07 has been doing some tools research and there's some promising evidence that we can actually implement the ne framework 18:43:57 #info 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 18:45:18 #Info 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 18:45:46 #Info dfarrell07 says he'd like to see us wait, he doesn't see any real problems from waiting 18:46:45 #info 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 18:47:10 #info rovarga said we had wanted to vote on boron with the new TSC, and so the currently standing method would allow that 18:48:39 colindixon: similar is not the same, unless you know something about the election results... ;-) 18:49:45 #Info dfarrell07 agrees that if we want to have the new TSC approve the Boron planning, we really need to have old-style election 18:50:59 #info 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 18:52:29 #info 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 18:54:04 looks like there is convergence on this topic. 18:54:10 release cadence?? 18:55:38 #info 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 18:56:24 Or you could have the committers-at-large have the term for 2 releases (Boron + Carbon), have the term for the representative groups PTLs start at the end of Boron i.e. their term is Carbon + the next. That way you would sort of like Senate - not everyone changes at the same time 18:57:28 #info 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 18:57:33 abhijitkumbhare: it might be more complex to do max mechanics with that, but it could work maybe 18:59:08 #startvote 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? -1, 0, +1 18:59:08 Begin voting 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? Valid vote options are -1, 0, +1. 18:59:08 Vote using '#vote OPTION'. Only your last vote counts. 18:59:19 #vote +1 18:59:30 #vote +1 18:59:30 #vote +1 18:59:32 #vote +1 18:59:32 #vote 0 18:59:39 #vote +1 18:59:41 #vote +1 18:59:54 #endvote 18:59:54 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 18:59:54 0 (1): gkaempfer 18:59:54 +1 (6): LuisGomez, ChrisPriceAB, dfarrell07, edwarnicke, colindixon, mohnish_ 19:00:26 welcome gkaempfer! :) 19:00:48 welcome gkaempfer! 19:00:52 welcome to TSC gkaempfer 19:01:03 #agreed we will have an odl-style election as soon as is reasonable 19:01:08 #topic welcome gideon 19:02:38 #info gkaempfer (Gideon Kaempfer) of HP is their new TSC representative 19:02:54 welcome gkaempfer! 19:03:29 #topic cookies 19:03:35 #endmeeting