17:00:01 <colindixon> #startmeeting tsc
17:00:01 <odl_meetbot> Meeting started Thu Apr  2 17:00:01 2015 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
17:00:01 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:01 <odl_meetbot> The meeting name has been set to 'tsc'
17:00:07 <colindixon> #topic roll call and agenda bashing
17:00:18 <colindixon> #chair phrobb regXboi dfarrell07
17:00:18 <odl_meetbot> Current chairs: colindixon dfarrell07 phrobb regXboi
17:00:25 * colindixon looks for tbachmann
17:00:26 * regXboi not on phone yet
17:00:42 <colindixon> #link https://wiki.opendaylight.org/view/TSC:Main#Agenda the agenda in it’s usual place
17:00:53 <colindixon> #chair phrobb1
17:00:53 <odl_meetbot> Current chairs: colindixon dfarrell07 phrobb phrobb1 regXboi
17:01:01 <colindixon> #info colindixon
17:01:09 <regXboi> #info regXboi
17:01:20 <ChrisPriceAB> #info Chris Price
17:01:23 <colindixon> TSC members please #info in
17:02:02 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-03-26-17.00.html last week’s minutes (mostly for action items)
17:02:05 <dfarrell07> colindixon: I'm here
17:02:11 <colindixon> dfarrell07: awesome!
17:02:16 <dlenrow> #info dlenrow
17:02:32 <dlenrow> I'm IRC only today...
17:02:37 <jmedved> #info jmedved
17:02:39 <mohnish> #info mohnish anumala
17:02:57 <colindixon> #info Eric Multanen on the phone for Uril (https://lists.opendaylight.org/pipermail/tsc/2015-April/002826.html)
17:04:05 <cdub> #info Chris Wright
17:04:10 * regXboi made it to the phone
17:04:15 <edwarnicke> #info edwarnicke
17:04:32 <colindixon> #action LuisGomez to start drafting a list of qualifiers for an issue for being a blocker to an SR - edwarnicke to assist
17:05:07 <colindixon> #action regXboi, Wojciech. edwarnicke, and Mahesh to organize meeting to talk about AAA keystone federation
17:05:33 <mohnish> will join the call a bit late ... but on IRC
17:06:04 <colindixon> #info ttkacik1 says that he has talked to Wojciech about how to boostrap AAA from the MD-SAL (action item from last week)
17:06:20 <colindixon> #action LuisGomez to start a thread about how to unblock integration testing until patches are merged
17:07:24 <colindixon> #topic Events
17:07:31 <dneary> Hi all
17:07:33 <dfarrell07> Laptop crashed, IRC mobile atm (so no minutes)
17:07:50 <colindixon> dfarrell07: understood
17:08:02 <tykeal> GPG keysigning party will happen during the hackfest
17:08:05 <colindixon> #info the hackfest is coming in 2 weeks, so projects please try to figure out what to dover
17:08:05 <tykeal> #link https://lists.opendaylight.org/pipermail/dev/2015-March/000409.html <- GPG keysigning party for hackfest information
17:08:08 * ChrisPriceAB chair me if you lie
17:08:08 <edwarnicke> tykeal: +1 :)
17:08:13 <colindixon> #chair ChrisPriceAB
17:08:13 <odl_meetbot> Current chairs: ChrisPriceAB colindixon dfarrell07 phrobb phrobb1 regXboi
17:08:23 <colindixon> #info the india forum is foign to happen the week of 4/21
17:08:36 <colindixon> #link http://www.opendaylight.org/news/events/ events on the ODL page
17:08:48 <ChrisPriceAB> #info OpenDaylight activities are planned at the OpenStack summit as well
17:08:59 * ChrisPriceAB yep
17:09:03 <dneary> no colindixon
17:09:07 <dneary> I can't hear you
17:09:15 <tykeal> dneary: lol
17:09:45 <colindixon> #info mini-summit (and cfp) for NFV world
17:09:58 <colindixon> #info mini-summit (and cfp) for the Open networking Summit
17:10:10 * ChrisPriceAB too fast
17:10:25 * ChrisPriceAB +1 I really hope so
17:10:34 <colindixon> #info there’s our summit and design forum (we will call for topics for the design forum after Li releases)
17:10:53 <regXboi> #info regXboi asks if the hackfest would be virtual-friendly again?
17:11:11 <colindixon> #info phrobb says we’ll do the same as we’ve done in the past, but no more unless we have other ideas
17:11:12 <regXboi> #info answer is that what was is done in the past would be done again, but no more
17:11:38 <snackewm> #info Eric Multanen in attendance for Uri Elzur
17:11:41 <ChrisPriceAB> #info there is an ONF app-fest planned in may.
17:11:53 <colindixon> #link https://www.opennetworking.org/?p=1695&option=com_wordpress&Itemid=471 the ONF Appfest (nee Plugfest) is May 18-22
17:12:10 <ChrisPriceAB> #info abhijit adds that the event has extended to include applications and non-ONF members
17:12:11 <colindixon> #link https://www.eventbrite.com/e/onf-appfest-registration-16131345288 registration closes on 4/10
17:13:13 <colindixon> #info ODL hasn’t been there in the past, but in the last one HP used ODL to participate
17:13:54 <ChrisPriceAB> #info ColinDixon asks if anyone is interested in participating
17:14:01 <colindixon> #info ChrisPriceAB says Ericsson is hosting it and will be testing/presenting the ODL controller
17:14:31 <colindixon> #action ChrisPriceAB to mail discuss/tsc (and others) to see if others are going to participate
17:14:37 <colindixon> #info mlemay will also be there
17:14:50 <dfarrell07> can I do: #action ChrisPriceAB to send mail to TSC list about attending ONF app-fest
17:15:04 <dfarrell07> ah, nvm
17:15:11 * dfarrell07 is back but reading scroll-back
17:15:20 <ChrisPriceAB> #action abhijitkumbhare to pick up the action on to e-mail the lists.
17:15:26 <colindixon> #info note it’s actualy the same dates as the OpenStack summit
17:15:29 <colindixon> ChrisPriceAB: :p
17:15:41 * ChrisPriceAB :D
17:15:46 <mlemay> dang.. I double booked :S
17:16:00 * ChrisPriceAB yeah, but the gas district beckins mlemay
17:16:42 <dfarrell07> #action catohornet will send mail to Integration team about helping with app-fest
17:16:57 <mlemay> @ChrisPriceAB: Difficult decisions (OS vs AppFest)
17:16:57 <dfarrell07> colindixon: yep, back and trying to catch up
17:17:24 <colindixon> #topic sytem integration & test
17:17:25 * ChrisPriceAB still in a twist over it mlemay, giving me ulcers
17:17:36 <dfarrell07> #info catohornet reports for Luis (away for week) on Integration
17:17:44 <colindixon> #info catohornet would like to encourage projects to get their system tests in as soon as possible
17:18:51 <colindixon> #topic Lithium update
17:19:10 <dfarrell07> #info regXboi suggests having M* dates on Wednesdays
17:20:07 <colindixon> #link https://docs.google.com/spreadsheets/d/1KPpO9LH539Vlcoa4RvLa6PPCdLifi5JD-ihRhlybqeo/edit#gid=1196332566 Lithium tracking spreadsheet
17:21:31 <colindixon> #info phrobb says that there are 3 projects which are at risk of having to drop out of Lithium
17:21:47 <colindixon> #info Maple with Yale-related IPR issues is at risk fo getting no conent in
17:22:01 <colindixon> #Info Plugin2OC has been effectively non-responsive for weeks now
17:22:17 <zxiiro> #link https://lists.opendaylight.org/pipermail/plugin2oc-dev/2015-March/000069.html
17:22:27 <colindixon> #info the SXP projec has also be non-responsive, but jmedved is working inside Cisco to try to revive them
17:23:25 <dfarrell07> #info phrobb et al have been very accommodating with non-responsive projects
17:23:29 <colindixon> #info phrobb says from his perspective that we have been as bend-over-backward willing to work with projects and they haven’t particpated at all
17:23:32 <regXboi> whow
17:24:04 <dfarrell07> zxiiro: which project was that?
17:24:13 <zxiiro> dfarrell07: plugin2oc
17:24:34 <dfarrell07> #info Plugin2OC non-merges/respones are blocking zxiiro's tagging efforts
17:24:44 <dfarrell07> #undo
17:24:44 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x18b7090>
17:24:51 <dfarrell07> #info Plugin2OC non-merges/responses are blocking zxiiro's tagging efforts
17:25:47 <dfarrell07> #info edwarnicke suggests giving a (final, I think) warning to non-responsive projects about being dropped from Li
17:27:22 <colindixon> #action phrobb to send mail to Plugin2OC saying that barring an objection from them, they are likely going to be dropped from Lithium at the next TSC meeting
17:28:35 <colindixon> #action colindixon to send mail to the TSC list to start a conversation about how to deal with projects that have no remaining active committers
17:28:39 <regXboi> #info there are a few projects where the original committers are stepping down without new ones being promoted in their place
17:28:56 <regXboi> #info so how do we want to deal with projects where all committers are gone
17:29:02 <dfarrell07> #info New contributors have joined these non-responsive projects, but aren't committers, need a way to deal with this
17:29:19 <regXboi> #info jmedved has people to replace the committers on sfc, but we need to figure out the committer issue there
17:29:29 <colindixon> SXP
17:29:30 <colindixon> #undo
17:29:30 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x17c2ed0>
17:29:42 <colindixon> #info jmedved has people to replace the committers on SXP, but we need to figure out the committer issue there
17:29:58 <regXboi> #info the problem is that the other three committers in SXP are unresponsive
17:30:50 <gzhao> Question: how do we make sure project fact are up to date, i.e, project lead and project contact are accurate.
17:31:00 <colindixon> gzhao: good question
17:31:29 <colindixon> gzhao: tykeal and phrobb will know about committers since it’s in a config file
17:31:35 <dfarrell07> #info colindixon and edwarnicke point out that obvious solutions to problems described above (terminate, force-add new committers, contact old committers) are painful or not working, looking for better ones
17:32:14 <tykeal> colindixon: not exactly a config file, but an LDAP script call away for a report ;)
17:33:19 <dfarrell07> #info colindixon suggests moving this to the mailing list
17:34:16 <colindixon> #info zxiiro says he submitted a variety of patches around auto-release, and a working prototype of the auto-release builder based on that
17:34:37 <colindixon> #action zxiiro to e-mail release to get people to merge patches with a list of patches
17:34:55 <colindixon> #topic infrastructure
17:35:18 <colindixon> #info tykeal says sandbox has been moved to it’s own resources as of Tuesday to avoid contention with the releng/builder
17:35:48 <colindixon> #info tykeal says the releng/silo has been “gumming up” where it loses slaves and won’t bring new ones, the only current solution is to reset jenkings
17:36:02 <colindixon> #info they are detecting it and fixing when they can, but if you see it bring it to their attention
17:36:46 <colindixon> #info yesterday, people noted that people noted that gerrit pushes/patches were taking a long time, and they noted that there were queued jobs when it happened
17:36:58 <colindixon> #info possible solutions  include moving to a machine with more RAM
17:37:57 <colindixon> #action tykeal to add some of these issues to the Weather page: https://wiki.opendaylight.org/view/Weather
17:39:00 <colindixon> #info tykeal notes that we will likely get a dashboard and less issues that we have now as we move to nodepool and zuul
17:39:11 <dfarrell07> colindixon: I have committer promotion stuff queued
17:39:23 <colindixon> dfarrell07: thanks!
17:39:36 <dfarrell07> tykeal: I will send you one ASAP
17:39:38 <colindixon> #action people send GPG keys to tykeal
17:39:51 <colindixon> #undo
17:39:51 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Action object at 0x1bab350>
17:40:19 <dfarrell07> #info People should follow up with tykeal about key signing
17:40:24 <dfarrell07> #topic Committer promotion of Martin Sunal for GBP
17:40:29 <alagalah> #link https://lists.opendaylight.org/pipermail/groupbasedpolicy-dev/2015-April/001039.html
17:40:34 <dfarrell07> #undo
17:40:34 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x1b941d0>
17:40:35 <dfarrell07> #link https://lists.opendaylight.org/pipermail/groupbasedpolicy-dev/2015-April/001039.html Nomination email thread
17:40:42 <dfarrell07> #link http://spectrometer.opendaylight.org/?metric=loc&release=all&user_id=msunal Spectrometer report for Martin Sunal
17:41:05 <colindixon> #info 4 (of 6) committters gave a +1 with no -1s
17:41:31 <dfarrell07> #info GBP issues with Spec reports, but has been contributing tons says alagalah
17:42:03 <colindixon> #link https://git.opendaylight.org/gerrit/#/q/project:groupbasedpolicy+owner:%22Martin+Sunal+%253Cmsunal%2540cisco.com%253E%22 patches on GBP
17:42:09 <dfarrell07> #info GBP only has two active committers, needs more
17:43:40 <regXboi> #chair tbachman
17:43:40 <odl_meetbot> Current chairs: ChrisPriceAB colindixon dfarrell07 phrobb phrobb1 regXboi tbachman
17:43:41 <colindixon> #info a major patch will come in the next week and we can review this again then
17:43:53 <dfarrell07> #info It's suggested that the vote is pushed to next week to allow for current large pending patch to be merged
17:44:00 <dfarrell07> #undo
17:44:00 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1b94250>
17:44:20 * tbachman wanders in to the room — needs to get on webex
17:44:35 <dfarrell07> #topic Beryllium Planning
17:44:58 <dfarrell07> #info colindixon suggests everyone chime in on mailing list thread
17:45:08 <dfarrell07> #link https://lists.opendaylight.org/pipermail/tsc/2015-April/002829.html Relevant mailing list thread
17:45:37 <dfarrell07> #info edwarnicke points out that everyone is very heads-down at the moment, will be hard to get input between now and Li
17:46:31 * tbachman is back on
17:47:28 <dfarrell07> tbachman: hey there :)
17:47:35 <tbachman> dfarrell07: hey!
17:47:48 * tbachman screws head on right… cracks knuckles
17:47:52 <dfarrell07> lol
17:48:07 * tbachman is a bit out of context
17:48:24 * dfarrell07 doesn't know how to sum this up
17:48:29 * tbachman is the same
17:48:33 <cdub> while waiting for mvn...chime into conversation
17:48:38 <cdub> not that challenging
17:48:42 <tbachman> lol
17:49:08 <tbachman> dfarrell07: it sounds like this is re: Beryllium planning?
17:49:19 <tbachman> #info ChrisPriceAB says he feels it’s worth having the Beryllium discussion now
17:49:19 <cdub> tbachman: yes
17:49:24 <tbachman> cdub: thx ;)
17:49:31 <dfarrell07> #info colindixon and cdub point out that people likely can find time to contribute, even while heads-down
17:49:38 <dfarrell07> #undo
17:49:38 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1aaf190>
17:49:39 <gzhao> tbachman: dfarrell07 someone are IRC only -:)
17:49:56 <dfarrell07> #info colindixon and cdub point out that people likely can find time to contribute to Be release discussion, even while heads-down
17:50:02 <tbachman> gzhao:  ;)
17:50:31 <colindixon> #info rovarga says that he wants to avoid what happened with Lithium where everyone vanished after Helium and did nothing and we rushed the Lithium plan out the door
17:50:32 <tbachman> #info rovarga says that the Lithium plan was created as a result of running up against the clock — thinks we should start now to avoid doing the same in Beryllium
17:50:35 <tbachman> #undo
17:50:35 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1a8c3d0>
17:50:35 <tbachman> lo
17:50:37 <tbachman> lol
17:50:39 <tbachman> colindixon: thx ;)
17:51:20 <tbachman> #info rovarga points out that some projects are going to M5, which is only bug fixing
17:51:38 <tbachman> #info cdub agrees with rovarga — we have a history of doing the release and taking a long break/vacation
17:52:05 <dfarrell07> tbachman: glad to have you back, you're at least 20% faster at minutes than I am :)
17:52:06 <tbachman> #info colindixon says we need to have the discussion on don’t change vs. meaningful change
17:52:12 <tbachman> dfarrell07: not ;)
17:52:14 <tbachman> but thx
17:52:55 <colindixon> #action colindixon to add “consolidate requirements” to lesseons learned from Helium
17:52:58 <tbachman> #info edwarnicke says one of the major complaints he heard was what they had to do was scattered all over the place — a simple attempt to consolidate everything in to one place would help
17:53:24 <gzhao> M3 seems to need a little extra time
17:53:48 <tbachman> #info colindixon elaborates on edwarnicke’s comment — testing requirements, doc requirements, and baseline release requirements were in different places
17:53:54 <tbachman> hear hear
17:54:11 <cdub> colindixon: cool, i think that's what i said ;)
17:54:37 <tbachman> should we shift topic?
17:54:46 <colindixon> #topic Board requests to the TSC
17:54:53 <tbachman> colindixon: thx
17:55:00 <colindixon> can we #link in the two links from the agenda
17:55:03 <tbachman> #info regXboi says he hopes to take time today to answer that
17:55:12 * tbachman is out of his usual preparedness
17:55:23 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2015-March/002806.html board requests
17:55:35 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2015-March/002818.html some of colindixon’s ideas for how to respond
17:55:45 <tbachman> colindixon: thx
17:55:49 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2015-March/002740.html use case pipeline thread (started before)
17:56:11 <dneary> It would be so useful for Gerrit patchsets to have a "commit message" saying what's changed since the last patchset. Looking through the diffs is a pain.
17:56:32 <colindixon> #action everyone please contribute to both the Be release planning and Board requests
17:56:37 <tbachman> #info on the previous topic, rovarga is fine with a 2 month preparation; but if that is to happen, we need to know now in order to plan for it
17:57:03 <colindixon> tbachman: thanks!
17:57:06 <tbachman> colindixon: np!
17:57:29 <ChrisPriceAB> don't listen to those OPNFV folks...
17:57:41 <tbachman> #info on the previous topic (release planning), regXboi brings up the possibility of using isotope type releases
17:57:43 <colindixon> sorry
17:57:44 <tbachman> colindixon: we lost you
17:57:45 <colindixon> lost phone
17:57:50 * edwarnicke is in favor of naming things after isotopes.... but recognizes it may not be a good idea ;)
17:57:51 <tbachman> in the move?
17:57:54 <colindixon> I’d like to see us timebox Be
17:57:55 <dfarrell07> you'd like to see... lol
17:57:57 <colindixon> release planning
17:58:04 <regXboi> colindixon - you dropped
17:58:05 <colindixon> so, people chime in on the mailing list in the next week
17:58:07 <colindixon> I know
17:58:08 <regXboi> but you know that :)
17:58:10 <edwarnicke> colindixon: timeboxing sounds good
17:58:12 <tbachman> #info colindixon would like to see the Beryllium release timeboxed
17:58:16 <ChrisPriceAB> Can we timebox to October?  Target = OPNFV Rel 2!
17:58:33 <regXboi> ChrisPriceAB - I'd really rather that be an isotope of Lithium
17:58:39 <tbachman> #info colindixon asks folks to chime in on the mailing list on Beryllium release planning for next week’s TSC
17:58:44 <regXboi> because of it being October
17:58:47 <dneary> phrobb, I put a new case study up on the wiki: https://wiki.opendaylight.org/view/Packet_Design
17:58:47 <colindixon> #info if you care about the Be relese plan try to chime in in the next week, as I’d like to be able to have sombody (phrobb?) create a draft release plan
17:58:48 <ChrisPriceAB> I can buy that regXboi.
17:59:07 <regXboi> and that's why I'm thinking of isotopes and push Be out to next year
17:59:07 <ChrisPriceAB> Can we raise that as a planning topic for Lithium?
17:59:21 <dfarrell07> edwarnicke: he's saying that there are existing bugs that need attention
17:59:24 <tbachman> any of this going into the hackfest?
17:59:24 <colindixon> #info even if only to say that you can’t afford time right now
17:59:25 <ChrisPriceAB> Lithium - feature drop release.
17:59:40 <regXboi> colindixon: ack
17:59:52 <dneary> Lithium *does* have isotopes - wasn't aware of it
17:59:54 <ChrisPriceAB> Ok, need mor discussion but I would be very happy and it serves OPNFV needs.
18:00:01 <regXboi> dneary :)
18:00:03 <cdub> dfarrell07: should #info that
18:00:09 * dneary was wondering if the isotope metaphor was stretching it
18:00:13 * tbachman missed that
18:00:16 <dfarrell07> I will try
18:00:30 <colindixon> #topic performance isseus in the Lithium release
18:00:43 * ChrisPriceAB I appreciated it dneary, chuckling quietly
18:00:44 <abhijitkumbhare> regXboi ChrisPriceAB - as per our charter we need to have 2 releases in the year - so a mini release lined up with OPNFV makes sense - otherwise we need to get an exception for the 2 release requirement
18:00:46 <dfarrell07> #info There are perf existing bugs, known and documented and bugs raised that need attention.
18:00:57 <rovarga> #info I actually wanted to imply that there are three topics wrestling for attention: getting Li out, getting Be planned, discussing the response to the Board. getting all done at the same time will prove ... challenging.
18:01:05 <tbachman> #link https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Performance_Test:Results wiki page for performance testing results
18:01:06 <regXboi> abhijitkumbhare: that was in the background
18:01:17 <regXboi> tbachman to the rescue again!
18:01:24 <dfarrell07> #info Integration team has some perf in CI, more going in to CI very soon (many people working on it actively)
18:01:25 <tbachman> lol
18:01:32 <edwarnicke> markat: https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Performance_Test:Results is awesome
18:01:33 <tbachman> dfarrell07: to the rescue too!
18:01:45 * tbachman wonders if markat is Mahesh
18:01:46 <ChrisPriceAB> isotope releases probably require branching :s
18:01:50 <edwarnicke> markat: Mind if I put all the bugs under a single section so we can link directly to the collection of bugs?
18:02:01 * ChrisPriceAB cheers all
18:02:45 <tbachman> #info regXboi sasy we need to figure out the Beryllium/Lithium isotope discussion
18:02:47 <rovarga> regXboi: I would prefer one well-engineered release to two releases :)
18:02:59 <tbachman> #info abhijitkumbhare says as per our charter we need to have 2 releases in the year - so a mini release lined up with OPNFV makes sense - otherwise we need to get an exception for the 2 release requirement
18:03:37 <tbachman> #info regXboi says OPNFV has a deadline in October — an isotope releases targeted at that use case may make sense, with Beryllium being a release that addresses larger issues (e.g. architecture)
18:03:54 <mohnish> regXboi: +1
18:04:14 <tbachman> #info colindixon urges again for folks to take this to the mailing list
18:04:19 <cdub> colindixon: that's not kernel-style
18:04:20 <edwarnicke> are we now 5 minutes over time?
18:04:27 <tbachman> edwarnicke: 4 ;)
18:04:32 <colindixon> cdub: sorry
18:04:58 <cdub> colindixon: no worries, just educating ;)
18:05:04 <colindixon> cdub: I’d love to better understand
18:05:09 <regXboi> #topic cookies
18:05:14 <regXboi> :)
18:05:21 <colindixon> #endmeeting