17:00:19 #startmeeting tsc 17:00:19 Meeting started Thu May 5 17:00:19 2016 UTC. The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html. 17:00:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:19 The meeting name has been set to 'tsc' 17:00:25 #topic agenda bashing and roll call 17:00:32 #info gkaempfer 17:00:40 TSC members please #info in 17:00:43 #info colindixon 17:01:07 #info Daniel Farrell 17:01:08 #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=45906#Agenda today's agenda in it's usual place 17:01:16 #info Tony Tkacik 17:01:21 #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-04-21-17.00.html last meetings' minutes 17:01:23 #info edwarnicke 17:01:42 #info abhijitkumbhare 17:01:59 #info vishnoianil 17:03:07 #link https://lists.opendaylight.org/pipermail/discuss/2016-May/006476.html 17:03:10 #undo 17:03:10 Removing item from minutes: 17:03:17 #info mohnish anumala 17:03:24 #link https://lists.opendaylight.org/pipermail/discuss/2016-May/006476.html mail trying to move carbon planning forward 17:03:35 #link #link https://lists.opendaylight.org/pipermail/discuss/2016-May/006476.html colindixon made the changes here to clarify the boron release plan 17:04:00 https://lists.opendaylight.org/pipermail/discuss/2016-May/006475.html 17:04:23 #link https://lists.opendaylight.org/pipermail/discuss/2016-May/006475.html planning openflow project reorganization 17:04:29 #action colindixon to reach out to tykeal to write up and send an e-mail about signing commits in gerrit 17:04:30 #action colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron? 17:04:31 #action colindixon to get anton to post JSON-RPC plugin slides here: https://wiki.opendaylight.org/view/Project_Proposals:JSON-RPC2.0-plugin 17:04:54 #action tykeal to e-mail the TSC with the list of semi-archived silos to figure out how to proceed 17:06:02 #info for quorum we have colindixon gkaempfer dfarrell07 edwarnicke abhijitkumbhare vishnoianil ttkacik mohnish_ we have quorum 17:06:20 #topic new TSC members 17:06:29 #link https://lists.opendaylight.org/pipermail/tsc/2016-May/005170.html CAL elections have finished 17:06:48 #Info CALs are: colindixon, ttkacik, abhijitkumbhare, edwarnicke 17:07:31 #Info abhijitkumbhare introduces himself he's been around a while and mostly involved in openflowplugin 17:07:51 #info ttkacik has also been around a while—since the beginning of OpenDaylight 17:08:32 #link https://lists.opendaylight.org/pipermail/tsc/2016-May/005158.html vishnoianil is replacing LuisGomez as Brocade's platinum designate 17:08:54 #info vishnoianil has also been around forever, was the first non-Cisco committer and worked before the first code drop 17:09:14 #topic MPLS-TP creation reviews 17:09:32 #link https://lists.opendaylight.org/pipermail/tsc/2016-March/004956.html MPLS-TP Service creation review 17:09:54 #link https://lists.opendaylight.org/pipermail/tsc/2016-April/005033.html [Creation Review] MPLS-TP solution 17:10:09 #action colindixon to drive the MPLS-TP creation reviews to conclusion 17:10:24 #link https://lists.opendaylight.org/pipermail/tsc/2016-May/005152.html Requesting more frequent releases from ODL 17:11:00 #undo 17:11:00 Removing item from minutes: 17:11:09 #topic TSC list discussions and votes 17:11:12 #link https://lists.opendaylight.org/pipermail/tsc/2016-May/005152.html Requesting more frequent releases from ODL 17:11:55 #info colindixon asks if we've figured out how to meet Brady's needs in the short term 17:12:23 #info 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 17:12:38 #info dfarrell07 says in the short term, it could work to use autorelease builds 17:13:23 #info 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 17:14:46 #link https://lists.opendaylight.org/pipermail/tsc/2016-May/005149.html split-out projects and lifecycle states 17:15:02 #action dfarrell07 to ask Brady if what we're planning is meeting his needs 17:15:57 #topic events 17:16:08 #link https://www.opendaylight.org/global-events 17:17:04 #Info 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 17:17:26 #info that's a few days before API freeze for offset 2 and a few days before code freeze for offset 0 17:18:34 #Info edwarnicke points out that it's hard travel to do those two things back to back 17:18:53 #info colindixon asks if we could move it 2 or 3 weeks earlier, phrobb says not really, no space 17:18:58 #info especially when one of those two things is in Europe and the other NA West Coast ;) 17:20:15 +1 on 6/29 +/- day 17:21:10 #Info 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) 17:21:36 and July 1st is a Canadian holiday ;) 17:22:46 #Info 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 17:23:33 #action phrobb to send e-mail asking if the 6/29-30 date works for people 17:23:42 #undo 17:23:42 Removing item from minutes: 17:23:54 Personally I will not make it till around July 20 - but whatever works for the majority 17:24:10 #action phrobb to send e-mail asking if the 6/29-30 date works for people for a hackfest in the south bay 17:24:47 #link https://www.opendaylight.org/events/2016-09-27-000000-2016-09-29-000000/opendaylight-summit-2016 the CFP for the OpenDayligtht summit closes TOMORROW 17:25:03 #info we're in the high-30s now, but we're looking to be over 50, so it's actually looking pretty good 17:25:25 #link https://www.opendaylight.org/events/2016-06-20-000000-2016-06-23-000000/opnfv-summit OPNFV summit in Berlin starts on 6/20 17:25:38 #topic boron 17:26:04 #info 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. 17:26:09 #link https://git.opendaylight.org/gerrit/26323 <--- Patch upgrading Karaf 17:26:13 #link https://wiki.opendaylight.org/view/Weather#Upgrade_to_Karaf_3.0.x <--- Weather Item for Karaf Upgrade 17:26:31 #info DIDM is currently breaking Autorelease. We are tracking it on bug 5843 17:26:36 #link https://bugs.opendaylight.org/show_bug.cgi?id=5843 <--- Bug Tracking Breakages 17:26:49 #info Boron M2 Offset 2 is due today. Please send your status report. 17:27:02 #link https://wiki.opendaylight.org/view/Simultaneous_Release:Boron_Release_Plan#M2:_Final_Release_Plan <--- Status Template 17:27:51 #link https://lists.opendaylight.org/pipermail/tsc/2016-April/005139.html Vratko asking questions about a stable distribution in Boron 17:29:29 #link https://wiki.opendaylight.org/view/Simultaneous_Release:Boron_Release_Plan#Stable_and_Extended_Features stable feature requirements 17:29:31 #action colindixon to ask offset 0 projects when/if they could have stable features and what they would be 17:29:35 IIRC a project can't have "stable" projects until they're mature 17:29:43 s/projects/features/ 17:29:49 stable feature requirements are really tough 17:30:59 #info 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 17:31:09 #info jamoluhrsen notes that stable feature requirements are really tough 17:33:09 #info 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 17:34:07 #info 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 17:35:05 #Info 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 17:35:16 #topic stable/beryllium 17:36:06 #info We initially targeted Beryllium SR2 Release on 4/28, but our latest build has OPENFLOWPLUGIN test failures in the integration distribution test job. 17:36:10 #link https://wiki.opendaylight.org/view/Simultaneous_Release/Beryllium/SR2/Status <--- Status Summary 17:36:15 #link https://bugs.opendaylight.org/show_bug.cgi?id=5523 <--- OpenFlow Li Plugin Cluster Bug 17:36:18 #info it looks like there are regressions with the new openflow plugin tests with clustering 17:36:18 #link https://git.opendaylight.org/gerrit/#/c/38369/ <--- Proposed Patch 17:38:32 I know there are real customers from real companies that are using the -li plugin. 17:38:41 we should not release with a regression 17:38:54 #info 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 17:39:08 #info jamoluhrsen notes that "real customers from real companies that are using the -li plugin" 17:39:30 #info it sounds the consensus is to wait for a fix 17:41:44 #action abhijitkumbhare to either review or find people to review the openflowplugin patch to fix Be-SR2 17:41:48 #topic system integration and test 17:42:24 #info we had 9 system test waiver requests in Beryllium, we only have 1 so far for Carbon 17:42:33 #info please get them in 17:42:45 #topic infrastructure 17:43:29 #info the intent was to move the jenkins sandbox to the private cloud this weekend, but an issue was found and that's delaying things 17:44:07 #info 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 17:44:33 #info zxiiro says if you're using JJB, they release 1.5 this week, so there's an update to look at 17:45:06 #topic Mohamed El-Serngawy as a committer on AAA 17:45:12 #link https://lists.opendaylight.org/pipermail/tsc/2016-May/005160.html 17:46:16 #startvote shall the TSC approve Mohamed El-Serngawy as a committer on AAA 17:46:16 Unable to parse vote topic and options. 17:46:23 #startvote shall the TSC approve Mohamed El-Serngawy as a committer on AAA? -1,0,+1 17:46:23 Begin voting on: shall the TSC approve Mohamed El-Serngawy as a committer on AAA? Valid vote options are -1, 0, +1. 17:46:23 Vote using '#vote OPTION'. Only your last vote counts. 17:46:32 #vote +1 17:46:33 #vote +1 17:46:34 #vote +1 17:46:35 #vote +1 17:46:35 #vote +1 17:46:38 #vote +1 17:46:38 #vote +1 17:47:10 ttkacik: ? 17:47:21 #endvote 17:47:21 Voted on "shall the TSC approve Mohamed El-Serngawy as a committer on AAA?" Results are 17:47:21 +1 (7): gkaempfer, dfarrell07, edwarnicke, colindixon, mohnish_, vishnoianil, abhijitkumbhare 17:47:30 #info note ttkacik voted verbally +1 17:47:37 #agreed Mohamed El-Serngawy in now a committer on AAA 17:47:58 #topic OpenDove Archive Review 17:48:04 #link https://wiki.opendaylight.org/view/Archive_Proposals/Open_DOVE 17:48:15 #link https://lists.opendaylight.org/pipermail/tsc/2016-March/004953.html posted on 3/28/2016 17:49:31 #info colindixon notes that the project has been inactive for 18 months and the one remaining active committer (Ryan Moats) agreed with course of action 17:49:42 #startvote shall the TSC move the Open DOVE project to archived? -1,0,+1 17:49:42 Begin voting on: shall the TSC move the Open DOVE project to archived? Valid vote options are -1, 0, +1. 17:49:42 Vote using '#vote OPTION'. Only your last vote counts. 17:49:46 #vote +1 17:49:48 #vote +1 17:49:48 #vote +1 17:49:48 #vote +1 17:49:49 #vote +1 17:49:50 #vote +1 17:49:51 #vote +1 17:49:53 #vote +1 17:50:32 #endvote 17:50:32 #endvote 17:50:32 Voted on "shall the TSC move the Open DOVE project to archived?" Results are 17:50:32 +1 (8): gkaempfer, dfarrell07, edwarnicke, colindixon, ttkacik, mohnish_, vishnoianil, abhijitkumbhare 17:50:42 #agreed the Open DOVE project is now archived 17:50:57 #topic TSC chair elections 17:50:58 huzzah! 17:53:07 #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 17:53:20 #action phrobb to inform the board that we're assuming the waiver applies to both 17:55:25 #agreed the TSC agrees that the next TSC chair's term should match the current TSC term (ending at the end of Boron) 17:55:45 #topic TSC election planning 17:55:54 #info we have another CAL election in ~5 months 17:56:06 #info we need a complete voting system for the new mechanics that works by then 17:56:39 #info this includes tooling, picking represented groups, and the properties of those groups 17:57:22 i just want to call out and say thanks for luis for his excellent contribution as a tsc member 17:57:33 #action dfarrell07 to drive forward tooling and planning for the next TSC election 17:58:01 #info 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 17:58:03 +1 vishnoianil Thanks for all of your sage advice as TSC member LuisGomez 17:58:06 +1 to vishnoianil ’s point about LuisGomez - excellent contribution from him as a TSC member 17:58:29 huge thanks LuisGomez! 17:58:35 +1 to LuisGomez 17:58:36 thanks LuisGomez! 17:58:42 thanks Luis 17:58:53 #info dfarrell07 is planning to help explain things simply so that others can understant 17:59:04 #topic thanking Luis Gomez for his service 17:59:16 thanks all 17:59:44 #info 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 17:59:48 well said, thanks LuisGomez 17:59:51 #info LuisGomez isn't going anywhere though 18:00:08 #info LuisGomez says it's really all about the community 18:00:10 #topic cookies 18:00:14 #endmeeting