18:00:13 <colindixon> #startmeeting tsc
18:00:13 <odl_meetbot> Meeting started Thu Jan 28 18:00:13 2016 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
18:00:13 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:00:13 <odl_meetbot> The meeting name has been set to 'tsc'
18:00:17 <colindixon> #topic agenda bashing and roll call
18:00:20 <colindixon> #info colindixon
18:00:32 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-01-21-18.00.html last week's meeting minuts
18:00:51 <dfarrell07> #info Daniel Farrell
18:00:57 <ChrisPriceAB> #info Chris Price
18:01:06 <colindixon> #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=40650#Agenda the agenda in it's usual place
18:01:34 <dfarrell07> colindixon: 343632
18:02:13 <colindixon> #action colindixon to keep boron planning on our minds
18:02:18 <jmedved> #info jmedved
18:02:19 <mohnish_> #info mohnish anumala
18:02:27 <colindixon> #action colindixon to send a reminder e-mail about TWS on boron planning on monday
18:02:55 <edwarnicke> #info edwarnicke
18:03:12 <LuisGomez> #info LuisGomez
18:04:54 <colindixon> #action colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
18:05:14 <colindixon> #action colindixon to follow this issue to figure out lessons learned and how to avoid the two diffenent openflow plugin in the future
18:06:11 <colindixon> #topic events
18:06:25 <colindixon> #link https://www.opendaylight.org/global-events
18:06:51 <colindixon> #link https://www.opendaylight.org/events/2016-01-31-000000-2016-02-01-000000/open-networking-india-symposium-2016 open networking india sunday/monday of this week phrobb will be there
18:07:05 <colindixon> #link https://www.opendaylight.org/events/2016-02-15-000000-2016-02-19-000000/cisco-live-berlin Cisco Live Berlin, phrobb and ChrisPriceAB will be on a panel there
18:07:19 <ChrisPriceAB> & cdub
18:07:30 <colindixon> #link https://www.opendaylight.org/events/2016-02-29-000000-2016-03-01-000000/opendaylight-developer-design-forum develper design forum 2/29 and 3/1, you can submit ideas and topics there if you want, there will be some unconference
18:08:02 <colindixon> #info many other events upcoming
18:08:38 <colindixon> #info notifications about the acceptances to ONS should be going out over the next bit, PC meetings should be over on Friday, some acceptances have already gone out
18:09:14 <colindixon> #info CFP for OpenStack closes on Monday (2/1) submit NOW
18:10:36 <colindixon> #info there is a mini-summit going on at ONS, there's CFP open now, having 6-8 slots, it will happen on Monday, 3/14, please submit now, you should have an e-mail, deadline is a week from Friday
18:10:48 <colindixon> #info there will be ONOS, ODL, and OPNFV mini-summits at least
18:11:24 <colindixon> #info LuisGomez expresses concern about the density of events and attending, e.g., both the dev design forum and the mini-summit at ONS
18:11:45 <colindixon> #action phrobb will make sure the mini-summit is on the events page
18:12:41 <colindixon> #topic boron
18:12:44 <colindixon> #Info no updates today
18:12:47 <colindixon> #undo
18:12:47 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x203c610>
18:13:11 <colindixon> #Info zxiiro says there are patches to switch to JDK8 for building. some projectss still need to do that
18:13:28 <colindixon> #Info rovarga says there are also a bunch of patches to move to equinox 3.9, please merge those too
18:13:52 <zxiiro> #link https://git.opendaylight.org/gerrit/#/q/status:open+project:releng/builder+branch:master+topic:jdk8only jdk8 patches
18:14:31 <rovarga> #info equinox upgrade: https://git.opendaylight.org/gerrit/#/q/topic:java8equinox
18:14:33 <colindixon> #action colindixon to bring up jdk8 and equinox next week so see if we're tracking
18:14:39 <rovarga> #link https://git.opendaylight.org/gerrit/#/q/topic:java8equinox
18:14:46 <colindixon> #topic beryllium
18:15:05 <colindixon> #Info we've had isseus with tests in RC0 and nearly no projects reported system test results
18:15:21 <colindixon> #info anipbu will be more aggresive to report things for RC1 to make sure we get better data
18:16:00 <colindixon> #info anipbu notes that build time for beryllium autorelease has gone up, zxiiro is investigating, on 1/21 it took 7 hours to build, on 1/22 it went up to 11 hours
18:16:09 <colindixon> #Info zxiiro asks anyone who might know why, to let him know
18:16:28 <colindixon> #info there were some issues with merging the fix to BUG4295, but they've been fixed now
18:17:15 <colindixon> #link https://wiki.opendaylight.org/view/Weather#Current_Weather_Report
18:17:40 <colindixon> #info anipbu says that there are some blocker bugs in Beryllium, anipbu has reached out to ask if they're actually blockers, if they'll be fixed, and/or if they can be downgraded
18:18:04 <colindixon> #topic system integration and test
18:18:18 <colindixon> #info projects please, Please, PLEASE report system test status for RC1
18:18:38 <colindixon> #topic infrastructure
18:18:50 <colindixon> #info we've had issues with dead ports and how quickly we can reap them, they are now running that script every 4 hours now, that should help
18:19:23 <colindixon> #topic Group Based Poilcy graduation review
18:19:38 <colindixon> #chair anipbu phrobb- phrobb
18:19:38 <odl_meetbot> Current chairs: anipbu colindixon phrobb phrobb-
18:19:39 <alagalah> #link https://wiki.opendaylight.org/view/Group_Based_Policy_(GBP)/Mature_Project_Proposal GBP Mature Project graduation proposal
18:21:03 <colindixon> #info one highlight is cooperating with SFC which was the first peer-to-peer example of that according LuisGomez
18:24:23 <colindixon> #Info colindixon goes through what's on the proposal and comments briefly, it all seems to look good to him
18:24:48 <colindixon> #info mohnish_ asks how far they are into the boron planning and how much churn/change we can expect
18:25:20 <vrpolak> Some parts of BGP+SFC demo are running as CSIT jobs, for example https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-1node-6node-all-stable-lithium/
18:25:21 <colindixon> #info alagalah says there's at least four tnew things they want to do, he's going to europe tomorrow to help scope those out internally and then bring it forward later
18:25:31 <colindixon> vrpolak: thanks!
18:25:51 <colindixon> #link vrpolak notes some parts of BGP+SFC demo are running as CSIT jobs, for example https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-1node-6node-all-stable-lithium/
18:26:21 <colindixon> #info alagalah says in GBP (and perhaps more broadly) we don't tend to give people informaiton about things past the next release, that information might be useful for the AG
18:26:39 <LuisGomez> #info these are all good examples of projects cooperation that we want to see more going forward.
18:27:31 <colindixon> #starvote shall the TSC move the Group Based Policy project to mature? -1, 0, +1
18:27:35 <mohnish_> #vote +1
18:27:40 <colindixon> #startvote shall the TSC move the Group Based Policy project to mature? -1, 0, +1
18:27:40 <odl_meetbot> Begin voting on: shall the TSC move the Group Based Policy project to mature? Valid vote options are -1, 0, +1.
18:27:40 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
18:27:43 <colindixon> #vote +1
18:27:45 <dfarrell07> #vote +1
18:27:47 <mohnish_> #vote +1
18:27:47 <LuisGomez> #vote +1
18:27:55 <ChrisPriceAB> #vote +1
18:28:05 <jmedved> #vote +1
18:28:07 <ChrisPriceAB> (and that goes to setting the right example too.)
18:28:34 <edwarnicke> alagalah: should feel special that GBPs vote was starred ;)
18:28:39 <colindixon> #endvote
18:28:39 <odl_meetbot> Voted on "shall the TSC move the Group Based Policy project to mature?" Results are
18:28:39 <odl_meetbot> +1 (6): jmedved, LuisGomez, ChrisPriceAB, dfarrell07, colindixon, mohnish_
18:28:40 <colindixon> #info note that edwarnicke also votes +1
18:29:00 <alagalah> GroupBasedPolicy
18:29:08 <colindixon> #agreed the Group Based Policy project is now a mature project in OpenDaylight
18:29:13 <ChrisPriceAB> congrats kieth and team!
18:29:15 <dfarrell07> congrats alagalah and GBP!
18:29:19 <LuisGomez> congrats GBP
18:29:28 <shague> Congrats!
18:29:28 <anipbu> congrats GBP!
18:29:29 <mohnish_> congrats GBP and Keith
18:29:32 <alagalah> Thanks folks!
18:29:35 <Prem_> Congrats Kieth and GBP!
18:29:40 <jamoluhrsen> alagalah, cookie time!
18:29:51 <colindixon> #topic committer promotions on OVSDB
18:29:57 <abhijitkumbhare> Congrats Keith & GBP !
18:30:01 <colindixon> #link https://lists.opendaylight.org/pipermail/ovsdb-dev/2016-January/002472.html Vishal Thapar as committer on OVSDB
18:30:18 <colindixon> #link https://lists.opendaylight.org/pipermail/ovsdb-dev/2016-January/002470.html Stephen Kitt as OVSDB Committer
18:30:50 <colindixon> #link https://git.opendaylight.org/gerrit/#/q/project:ovsdb+owner:%22Stephen+Kitt+%253Cskitt%2540redhat.com%253E%22+status:merged merged patches from Stephen in OVSDB
18:31:36 <colindixon> #link https://git.opendaylight.org/gerrit/#/q/project:ovsdb+status:merged+owner:%22Vishal+Thapar+%253Cvishal.thapar%2540ericsson.com%253E%22 meged patches from Vishal in OVSDB
18:32:08 * edwarnicke thanks colindixon for the links to commits :)
18:32:35 <colindixon> #startvote shall the TSC move Stephen Kitt to being a committer on OVSDB? -1, 0, +1
18:32:35 <odl_meetbot> Begin voting on: shall the TSC move Stephen Kitt to being a committer on OVSDB? Valid vote options are -1, 0, +1.
18:32:35 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
18:32:39 <colindixon> #vote +1
18:32:41 <edwarnicke> #vote +1
18:32:41 <dfarrell07> #vote +1
18:32:43 <jmedved> #vote +1
18:32:44 <mohnish_> #vote +1
18:32:45 <LuisGomez> #vote +1
18:32:52 <colindixon> #endvote
18:32:52 <odl_meetbot> Voted on "shall the TSC move Stephen Kitt to being a committer on OVSDB?" Results are
18:32:52 <odl_meetbot> +1 (6): jmedved, LuisGomez, edwarnicke, dfarrell07, colindixon, mohnish_
18:32:53 <ChrisPriceAB> #vote +1
18:33:00 <colindixon> #Info ChrisPriceAB also votes +1
18:33:01 <ChrisPriceAB> damn, keyboard spasm
18:33:02 <LuisGomez> #vote +1
18:33:12 <dfarrell07> LuisGomez: made the first one
18:33:29 <colindixon> #startvote shall the TSC move Vishal to being a comitter on OVSDB? -1, 0, +1
18:33:29 <odl_meetbot> Begin voting on: shall the TSC move Vishal to being a comitter on OVSDB? Valid vote options are -1, 0, +1.
18:33:29 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
18:33:32 <mohnish_> #vote +1
18:33:32 <colindixon> #vote +1
18:33:32 <edwarnicke> #vote +1
18:33:33 <dfarrell07> #vote +1
18:33:34 <ChrisPriceAB> #vote +1
18:33:36 <LuisGomez> #vote +1
18:33:38 <jmedved> #vote +1
18:33:42 <colindixon> #endvote
18:33:42 <odl_meetbot> Voted on "shall the TSC move Vishal to being a comitter on OVSDB?" Results are
18:33:42 <odl_meetbot> +1 (7): jmedved, LuisGomez, dfarrell07, ChrisPriceAB, edwarnicke, colindixon, mohnish_
18:34:00 <colindixon> #agreed both Stephen Kitt and Vishal Thapar are now committers on OVSDB
18:34:14 <abhijitkumbhare> Congrats Stephen Kitt & Vishal Thapar
18:34:24 <dfarrell07> congrats skitt and Vishal! :)
18:34:36 <Prem_> Congrats Stephen & Vishal :)
18:35:21 <ChrisPriceAB> I'm comfy with the situation.
18:35:50 <colindixon> #topic OpenFlow plugin graduation reviews
18:36:00 <colindixon> #Info colindixon asks if we're ready to review this given the current situation
18:36:32 <colindixon> #info abhijitkumbhare says sure, rovarga says he's worried about the current situation and without a plan it's hard to endorse the project as mature
18:37:00 <colindixon> #info ChrisPriceAB says that he feels like we have a plan and so, he's OK proceding with the discussion
18:37:08 <dfarrell07> #info dfarrell07 is concerned about flux in OFPlugin, would expect a more stable design from a Mature project
18:37:49 <colindixon> #info rovarga notes that there was a failure of communcation to figure out how how and when projects could migration, abhijitkumbhare says the plan has always been to migrate people in boron, it was people that hadn't asked migrating to the LIthium plugin that caused issues
18:39:12 <colindixon> #info LuisGomez says his take was that the release committments were met by the OpenFlow plugin
18:40:16 <hideyuki> FYI, at the begining of the Beyrllium, we (VTN project) had a conversation with OFP project guys about the plan of the bouth OFP-Lithium and OFP-Helium. And, at that time, we heard that they were going to work on both plugins for Beryllium.
18:40:31 <colindixon> #info rovarga notes that it's not that he doesn't feel that this review shouldn't happen, but he'd like to understand what the plan is to go forward
18:40:32 <dfarrell07> #info dfarrell07 also expects Mature projects to communicate during the Mature Release Process very well, isn't sure the design changes were up to that quality standard
18:40:46 <colindixon> #info hideyuki notes at the begining of the Beyrllium, we (VTN project) had a conversation with OFP project guys about the plan of the bouth OFP-Lithium and OFP-Helium. And, at that time, we heard that they were going to work on both plugins for Beryllium
18:41:44 <colindixon> #info phrobb note that in the release plan does not note needing to move between features
18:43:30 <dfarrell07> #info dfarrell07 is concerned about lack of docs about this change (which seems to be an API change) in Be release plan, isn't sure that's "following the Mature Release process"
18:43:40 <colindixon> #info phrobb also notes that there are no API changes, but there were actually some API changes for the new plugin
18:46:11 <colindixon> #info ChrisPriceAB notes that if the plan was always to deliver both, then there wasn't an API change in Beryllium, just two versions with compatibility concerns
18:46:51 <colindixon> #info colindixon notes that actually vishnoianil (and the broader openflowplugin team) did manage to fix the old design to ensure that it worked for everyone in the release to avoid delaying or blocking the release, while it was ugly, in the end they dealt with the hardship
18:47:18 <colindixon> #info abhijitkumbhare says that they do plan to move to one implementation in boron
18:47:55 <colindixon> #info colindixon asks if there are APIs that need to be deprecated NOW so that they could be removed in Boron (would we allow that)
18:48:38 <rovarga> FWIW, the XID+Notification programming is utterly unusable by any application which wants to have any notion of certainity that a flow has hit the network and should be deprecated nwo
18:48:40 <colindixon> #link https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Graduation_Proposal
18:48:41 <ttkacik1> maturity is about project ... stable-feature is about code implementation
18:49:39 <rovarga> I think the point of 'following the mature release process' is making sure the need for end-of-release heroics is virtually eliminated
18:50:00 <dfarrell07> rovarga: +1
18:50:31 <colindixon> #Info mohnish_ says as it stands in Beryllium, no project is using the new plugin by default, so that does ask about what "working code base" means in this context if the plan is to move to the new design
18:50:38 <dfarrell07> #info dfarrell07 and rovarga think the point of 'following the mature release process' is making sure the need for end-of-release heroics is virtually eliminated
18:50:49 <colindixon> ttkacik1: it does demand at least a working code base
18:55:31 <dfarrell07> #info dfarrell07 notes that he's on the record (TSC mailing list) as arguing for a more expansive interpretation of "following the Mature Release process"
18:57:01 <LuisGomez> rovarga: i think this community as well as others have end-of-release heroics and i am not sure how we are going to eliminate that when ODL is not first priority for most folks here.
18:59:25 <edwarnicke> #info as written, I don't think the governance makes any distinctions among offset-0,1,2
19:00:42 <alagalah> +1 colindixon ... compared to the end of Li .... this has been really pleasant
19:01:22 <colindixon> #startvote shall the TSC move the OpenFlow Plugin project to mature? -1, 0, +1
19:01:22 <odl_meetbot> Begin voting on: shall the TSC move the OpenFlow Plugin project to mature? Valid vote options are -1, 0, +1.
19:01:22 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts.
19:01:30 <dfarrell07> #vote -1
19:01:37 <jmedved> #vote -1
19:02:52 <dfarrell07> colindixon: I don't think you should stop the vote, it'd be like us bullying ppl
19:02:58 <colindixon> #vote +1
19:03:11 <LuisGomez> #vote +1
19:03:52 <ChrisPriceAB> #vote +1
19:04:04 <mohnish_> #vote 0
19:04:11 <edwarnicke> #vote 0
19:04:58 <colindixon> #endvote
19:04:58 <odl_meetbot> Voted on "shall the TSC move the OpenFlow Plugin project to mature?" Results are
19:04:58 <odl_meetbot> 0 (2): mohnish_, edwarnicke
19:04:58 <odl_meetbot> +1 (3): colindixon, LuisGomez, ChrisPriceAB
19:04:58 <odl_meetbot> -1 (2): dfarrell07, jmedved
19:05:32 <colindixon> #Info at least for now the resolution fails, there are several people who would like more information and might change there vote (notably edwarnicke mohnish_)
19:07:16 <colindixon> #info abhijitkumbhare asks when openflowplugin could come back to ask again, dfarrell07 says he'd like to see people come back after the Boron release
19:08:35 <jmedved> colindixon: if you agree with both sides, can you possibly be swayed to voting 0 next time? ;-)
19:08:46 <colindixon> jmedved: possibly
19:09:00 <colindixon> #info colindixon says he doesn't think there are mechanics that stop you from coming back to ask for another vote immediataly
19:09:31 <colindixon> #info colindixon, edwarnicke, dfarrell07 and others say there's another part that is when the TSC would feel like it would make sense
19:09:46 <colindixon> #Info rovarga says maybe right after the Beryllum release would be another option
19:10:26 <rovarga> #info I meant after next Release Review (which is Beryllium at this moment)
19:10:43 <colindixon> #info colindixon throws out Be-SR1 as another target
19:10:53 <colindixon> #info jmedved says all of those sounded like good candidates
19:11:00 <colindixon> #topic cookies
19:11:00 <rovarga> #info I do not thinkk SR1 has Releaseds Reviews
19:11:20 <colindixon> #info rovarga is correct only at formal release
19:11:23 <colindixon> #endmeeting