17:00:11 <colindixon> #startmeeting tsc
17:00:11 <odl_meetbot> Meeting started Thu Sep  8 17:00:11 2016 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
17:00:11 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:11 <odl_meetbot> The meeting name has been set to 'tsc'
17:00:16 <colindixon> #topic agenda bashing and roll call
17:00:21 <colindixon> TSC members please #info in
17:00:24 <colindixon> #info colindixon
17:00:31 <colindixon> #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=49599 today's agenda
17:00:48 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-09-01-17.02.html last week's meeing minutes
17:01:16 <rovarga> #info rovarga for jmedved
17:01:33 <gmainzer> #info Gal Mainzer (proxy for gkaempfer)
17:01:52 <ChrisPriceAB> #info Chris price
17:02:11 <dfarrell07> #info Daniel Farrell
17:02:24 <adetalhouet> #info adetalhouet
17:02:30 <abhijitkumbhare> #info abhijitkumbhare
17:02:41 <colindixon> #action colindixon to add APAC time TSC meeting to next week's meeting agenda http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_f447623d29817bc7
17:03:03 <colindixon> #action colindixon to add upgrades as Carbon Dev Forum topic
17:03:14 <colindixon> #acion dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion
17:03:21 <colindixon> #action rovarga will follow up with jira, group management, and user provisioning
17:03:49 <rovarga> #action dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion
17:04:01 <avishnoi> #info Anil Vishnoi
17:04:09 <colindixon> #action dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion
17:04:14 <colindixon> #chair anipbu phrobb
17:04:14 <odl_meetbot> Current chairs: anipbu colindixon phrobb
17:05:54 <colindixon> #action colindixon to schedule when can we schedule the TCP-MD5 termination review
17:07:32 <colindixon> #topic TSC mailing list votes and discussions
17:07:43 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-September/005924.html  VOTE on TSC Election RGs
17:08:03 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-September/005926.html  VOTE on resolving vote-per-person vs. vote-per-interest
17:08:04 <colindixon> #info for other topics see agenda
17:08:13 <colindixon> #topic events
17:08:21 <colindixon> #link https://www.opendaylight.org/global-events
17:08:29 <colindixon> #info we have a summit on 9/27-29
17:08:41 <jamoluhrsen> https://wiki.opendaylight.org/view/Events:Carbon_Dev_Forum
17:08:55 <jamoluhrsen> #link https://wiki.opendaylight.org/view/Events:Carbon_Dev_Forum  <--- DDF topics wiki
17:08:56 <colindixon> #link https://wiki.opendaylight.org/view/Events:Carbon_Dev_Forum please add any topics you want to for the Carbon DDF and add your name to the topics that you're interested in (phrobb uses that when scheduling)
17:09:40 <colindixon> #info phrobb will be scheduling things starting early next week, so please get things in now
17:10:21 <colindixon> #info tykeal is planning to run a keysigning on the second day, send your keys in if you want to participate
17:10:36 <colindixon> #topic Boron
17:10:43 <tykeal> #link https://lists.opendaylight.org/pipermail/discuss/2016-August/006803.html GPG keysigning email
17:10:59 <colindixon> hello odl_meetbot?
17:11:43 <dfarrell07> colindixon: I think it's working? It echo'd back the topic to me
17:11:57 <anipbu> #link https://wiki.opendaylight.org/view/Simultaneous_Release/Boron/Status   <--- Boron Status
17:12:26 <rovarga> #link http://meetings.opendaylight.org/opendaylight-meeting/2016/release/opendaylight-meeting-release.2016-09-07-21.55.log.html yesterday's technical analysis
17:16:22 <edwarnicke> anipbu: Could you add a blocking bug for VBD/HC https://bugs.opendaylight.org/show_bug.cgi?id=6105 ... there is a patch available: https://git.opendaylight.org/gerrit/#/c/40963/
17:24:23 <anipbu> #link https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=294913046   <--- Please see Section on DLUX 20 Patches for the related bugs and patches
17:25:20 <anipbu> edwarnicke: added
17:25:29 <edwarnicke> anipbu: Thank you :)
17:26:24 <colindixon> #Info colindixon notes that the marketing folks at LF have decide to postpoin the announcement until 9/21 (so 9 more days past monday)
17:27:22 <colindixon> #info colindixon says it's frustrating trade-off between not giving users a feature that seems really good, and merging 20 patches that weren't presented until the last minute despite many opportunities to raise this issue
17:29:36 <colindixon> #info vishnoianil notes that he'd really like to take the contribution and as a PTL and developer he'd love to see us fold these patches in, but as a TSC member he wants to draw a line in the sand
17:31:21 <colindixon> #info abhijitkumbhare asks what the risk is of not having this in, rovarga says his understanding is that the new feature is basically not functional
17:31:49 <colindixon> #info daniel malachovsky says that the fixes are just for the yangman application, it's basically a rework of the YangUI
17:31:54 <abhijitkumbhare> That was the same question I had LuisGomez
17:35:13 <LuisGomez> :)
17:35:57 <colindixon> #info daniel says he'd like deprecte YangUI in Boron, and remove it in Carbon, which can't be done without this
17:36:44 <adetalhouet> I haven't talk yet about the DLUX issue, but I do have some insight to add
17:37:56 <colindixon> #info colindixon says that we have two other blocking bugs: (1) a potential performance degradation in OpenFlow plugin and (2) a blocker in honeycomb/vbd
17:38:31 <colindixon> #Info adetalhouet says that the root of this issue was around not having enough committers on DLUX and that resulted in these patches not being cherry-picked before the release,
17:38:47 <abhijitkumbhare> colindixon: I don’t think the potential OpenFlow performance degradation is a regression
17:39:13 <colindixon> #info adetalhouet says that the TSC should be tracking the number of active committers per project so that we can make sure we catch things like this
17:39:36 <colindixon> #info vishnoianil agrees with that
17:39:44 <abhijitkumbhare> But performance will likely be the first thing outside folks will test - as rightly pointed to by LuisGomez (in OFP meeting)
17:40:12 <colindixon> #action colindixon anipbu and phrobb to start a discussion about better tracking committer activity in projects
17:40:13 <rovarga> abhijitkumbhare: are we prepping a perf paper to go with Boron release?
17:40:14 <edwarnicke> abhijitkumbhare: Agree
17:41:35 <abhijitkumbhare> I believe it was planned - but I think LuisGomez and cperf folks have been tracking that as an overall ODL performance activity
17:42:38 <LuisGomez> yes, we are working on our own perf paper based on Boron release
17:43:00 <colindixon> LuisGomez: isn't it likely that we'll find and have to fix more performance bugs between now and RC1 anyway?
17:43:28 <LuisGomez> probably but if we already know about this
17:44:13 <colindixon> #info abhijitkumbhare notes that the openflow plugin issue isn't a regression, it was present in Beryllium, there is no performance shift in our testing, but our testing goes only for 10/30 minutes
17:45:45 <colindixon> #info the honeycomb/vbd blocking bug about removing bridgedomains ocassionaly, it was fixed before, but the forgotten and the regression was found today
17:47:11 <colindixon> #Info Frank says that the current patch still needs more work, the bug results in stale state
17:49:07 <LuisGomez> the openflow fix is 1 line code that has been fully verified with no regresion in csit: https://git.opendaylight.org/gerrit/#/c/45210/
17:49:43 <colindixon> #info colindixon says that his take based on our typical guidance has been that it's good to release on time, but it's better to deliver software with fewer known bugs and stronger
17:53:38 <colindixon> #Info anipbu asks when Frank can get a fix, Frank says he hopes tomorrow, but he doesn't know because there isn't a root cause
17:54:05 <lori> is this not the same bug that has the onliner fix in openflowjava?
17:54:17 <lori> s/onliner/one-liner/
17:54:27 <colindixon> lori: one bug in ofj and another in hc/vbd
17:54:34 <lori> ok
17:55:12 <rovarga> lori: we do not have a fix for VBD
17:56:16 <lori> understood (my confusion stems from someone saying that this bug under discussion has the oneliner fix already merged in carbon, but obviously that was the ofj bug)
18:00:19 <adetalhouet> I agree with the plan
18:00:27 <anipbu> +1 to the plan
18:00:36 <dfarrell07> +1 to plan
18:00:43 <rovarga> sounds like a plan to me
18:00:55 <LuisGomez> +1
18:01:37 <colindixon> #info colindixon says the plan is to fix the three blocking bugs ASAP and respin once we have them, but no later than 11:59p UTC on sunday, then basically get go-nogo votes and test to vote on releasing by next TSC meeting
18:03:51 <colindixon> #info the TSC will have a *very* high bar for what is a blocking bug after that, e.g., it's not clear to colindixon that any of the three above bugs would meet that critiria
18:04:21 * rovarga wonders if we ever had a normal release ...
18:04:39 <tykeal> rovarga: define "normal" ;)
18:04:53 * edwarnicke wonders what surface the release should be normal too
18:05:04 <abhijitkumbhare> rovarga: more important question whether we will have a normal relase :)
18:05:22 <rovarga> so this release feels as broken as H/He ;-)
18:05:29 <dfarrell07> #info Thanks opnfv and frankbrockners  for finding that bug :)
18:05:31 <colindixon> #topic cookies
18:05:35 <colindixon> #endmeeting