16:56:44 #startmeeting 16:56:44 Meeting started Thu Apr 17 16:56:44 2014 UTC. The chair is phrobb. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:56:44 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:57:01 #topic TSC Members please #info in 16:57:06 #info dmm 17:01:31 #info Kent Watsen 17:02:18 has the meeting started? 17:02:24 yet 17:02:25 Yes 17:02:26 yes 17:02:38 #info Colin Dixon (represent IBM on behalf of Vijoy) 17:02:43 #info Ed Warnicke 17:03:04 #info Rob Dolin proxy for Rajeev Nagar (Microsoft) 17:03:20 #chair colindixon RobDolin 17:03:20 Current chairs: RobDolin colindixon phrobb 17:03:52 RobDolin: are you on the webex call? 17:04:16 @ColinDixon, I'm waiting for WebEx to connect... 17:04:23 all good 17:04:48 RobDolin: dmm was asking if you are the designated proxy this week 17:04:50 we haven't seen mail 17:06:04 #link https://wiki.opendaylight.org/view/TSC:Main#Meeting_Agenda 17:06:42 #topic Agenda Bashings 17:06:50 #topic Agenda Bashing 17:07:22 #info dmm points people to the agenda mentioning that today's agenda has time boundaries 17:08:01 #link https://wiki.opendaylight.org/view/TSC:Main <- includes agenda for today 17:10:17 #info David Meyer asked if Colin is ready for creation review and Colin says he is. 17:11:21 #topic Release Manager Update 17:12:26 #info Phil Robb reports that Huawei is interested in helping to fulfill the Release Manager role 17:13:32 #info Ed Warnicke suggests it is healthy for leadership to emerge 17:14:01 RobDolin: let me know if you want me to pick up scribing any time except for my creation review 17:14:26 @ColinDixon, would you mind picking-up for this topic? 17:14:33 #topic Helium Release Plan 17:14:34 sure 17:16:01 Thanks :) 17:16:24 #info Chris Wright here (apologies for being late) 17:17:01 #link Ed brings up his concerns about helium release dates expressed here: https://lists.opendaylight.org/pipermail/tsc/2014-April/001074.html 17:18:32 #info edwarnicke___ would like to allow all projects that get their proposals in by 4/30/2014, to be allowed to participate in the Helium release 17:19:04 #info and also reviewed by the Thursday 5/15/2014 17:19:43 #link https://lists.opendaylight.org/pipermail/tsc/2014-April/001074.html the actual link to the e-mail Ed sent (messed up the #link) 17:20:39 #info dmm and colindixon express their support for Ed's proposal 17:21:35 folks - I'm around to help scribe now that I'm finished with lunch... 17:21:43 #info RobDolin expresses his support, and goes further than that saying that we should err on the side of inclusivity in allowing people that come possibly even later than 4/30 and 5/15 (for proposal and review) 17:25:06 this isn't that hard... 17:25:27 #info edwarnicke___ expresses some concern around making sure that there is enough time for projects to collaborate during the simultaneous release 17:25:33 yes, we are off by a couple days, we aren't hard-lined...so be it 17:25:52 * colindixon shuts up to allow edwarnicke___ to post his thing for the TSC to vote on 17:26:18 #info proposal is that the TSC commit to admitting projects to the Helium Simultaenous Release which bring their project proposals by 4/30/14 and have their creation review by 5/15/14 as long as they also have Release Plans in place for the M1 time frame (linked off their proposals) 17:26:58 #info +1 17:27:02 #info +1 17:27:02 #info +1 17:27:02 +1 17:27:08 #info +1 17:27:11 #info +1 17:27:20 #agreed TSC agrees to Ed Warnicke's proposal 17:27:25 thanks phrobb 17:28:37 #topic helium release plans and venues 17:28:38 um... 17:28:55 Don't you mean Lithium Release Plan Reviews? 17:28:58 Venues 17:29:00 colindixon can you chair me to help as well? 17:29:06 #chair regXboi 17:29:06 Current chairs: RobDolin colindixon phrobb regXboi 17:29:20 #topic lithium release plans and venues 17:29:43 thanks 17:29:44 #info phrobb points out that venues in the Bay area are filling up quickly 17:30:06 #link https://wiki.opendaylight.org/view/Simultaneous_Release:Lithium_Release_Plan#Schedule 17:31:09 Portland or Seattle ? 17:31:20 #info the problem is that there are no venues in the bay area between 5/15 and 5/25 17:31:27 Hawaii :)? 17:31:31 ooh... I like Denver! 17:31:44 Kentucky ? ;) 17:31:50 heh 17:32:00 networkstatic's house 17:32:06 everyone gets a kitty 17:32:11 hehe 17:32:15 yesss 17:32:25 have running water toos 17:32:25 can't - my wife is allergic 17:32:32 whaaaaat 17:32:38 :( 17:32:44 I have a choice - cat or wife - I choose wife ;) 17:32:57 tough call sir :) 17:33:30 #info edwarnicke__ points out that lithium planning is finalized between M1 and M2 of helium 17:33:40 #info phrobb points out that he *has* to pick a venue 17:33:49 For Helium, our schedule has last call for proposals on 4/30 and then Release and Summit five months later on 9/30 17:34:43 #info phrobb is looking for a sanity check on the dates so that we can plan a venue as the lead time is longer than the release cycle... 17:34:44 In the Lithium draft the schedule has last call for proposals on 10/17, Release on 4/20 (six months + 3 days) 17:35:02 it's a year+ 17:35:05 We'll likely lose 3 weeks for (USA) Thanksgiving and winter holidays 17:35:52 can't hear folks 17:37:18 #info Ed Warnicke suggests we should have an initial day of tutorials 17:37:34 I can +1 the day of tutorials 17:37:48 #info Ed Warnicke suggests we should have a design summit that doesn't conflict with other parts of program 17:37:57 #info phrobb says the current plan is for a full week 17:38:56 Robert Varga is speaking 17:39:21 #info Robert V. suggests we have a large number of developers from outside the bay area 17:39:29 beat me too it :) 17:39:33 and me 17:39:58 #info Phil Robb suggests moving from the bay area would drop attendance by about 40% 17:40:06 man he is fast! 17:40:47 #info Ed Warnicke points-out that many projects have an epicenter in Europe or Asia and a substantial portion of developer population there as well. 17:41:43 #info David Meyer suggests the issue of venues, time zones, etc. be taken to the discuss alias 17:42:12 #topic Preventing Eclipse Breakage 17:42:37 #info colindixon gives kudos to brocade folks for fixing eclipse breakade 17:43:09 #info but wants projects to "do no harm" in bringing in new languages and maven plugins that break eclipse 17:43:19 #info Ed Warnicke also cheers the folks who did the Eclipse work 17:43:26 #topic DLUX status 17:43:27 Thanks Devin and Kiran! 17:43:40 #topic DLUX Project Status 17:43:58 Sorry Ryan I wasn't fast enough that time ;) 17:44:09 no worries 17:46:13 I'm not sure what I can #info from that 17:46:37 Maybe this is a moot point now, but wasn't there also an outstanding question on the licensing? 17:46:47 #info core developers have stepped away from DLUX and it's future is not clear 17:46:48 #info several of the core resources have moved on and so the project is at best thinly staffed 17:46:57 you win that one! 17:47:47 tbachman: yes and I was working with the team on getting through that when they announced that they were stepping back 17:47:59 phrobb: thanks! 17:49:56 #info Chris Wright suggests that we have a process in-place for time-out 17:50:39 #info Madhu points out that there is no management around the UI presented by opendaylight 17:51:03 #info all that is there is from the controller and *that* is AD-SAL focused 17:52:16 #info Ryan Moats (regXboi) suggests a controller may often live under an orchestrator and the interface will be the NB APIs 17:52:36 #info Jan Medved suggests a controller has more uses than just living under an orchestrator 17:52:57 #agreed there is no current TSC action item for DLUX 17:53:11 #link http://www.opendaylight.org/project-lifecycle-releases 17:53:35 Thanks Ed. I was searching for that on the website. 17:54:06 #topic NDM Create Review 17:54:16 #link http://wiki.opendaylight.org/view/Project_Proposals:Negotiable_Datapath_Models 17:56:01 #info Colin Dixon walks people through the project proposal describing Table Type Patterns (TTPs), ... 17:56:40 ... project plans, hardware targets, ... 17:56:46 #info colindixon points out there are some interesting hardware targets for this 17:57:59 +1 for the slides 17:58:30 #link http://events.linuxfoundation.org/sites/events/files/slides/TTPs%20and%20NBIs%20for%20ods2014-final_0.pdf slides 18:17:54 ;) 18:18:27 colindixon: thanks...just wanted to make sure we get this part 18:21:37 http://wiki.osgi.org/wiki/Require-Capability — on MD-SAL have application require specific capabilities in their manifests (hardware case) 18:23:54 icbts: how does that help an app? (i.e. something using REST API only) 18:24:32 if the app is deployed on controller then it will or will not resolve deepending on if the controller host can provide the abstract capability 18:25:09 +1 capability profiles :) 18:25:10 right, that's why i asked about REST API only (not a bundle) 18:26:07 good question, thats where some form of service will have to know if the controller host can handle the job. 18:26:27 perhaps an unsupported operation or the like 18:26:31 cdub: While I can see the value in the suggestion for bundles to use Require-Capabilities.. I also dislike intensely locking us into any particular binding and so concur we want to make sure our other bindings (like REST) also have access to them. 18:26:36 ok, got it (means i was actually tracking what you were saying ;) 18:27:11 (and I would be stunned if REST was the last of the bindings folks wanted to build on us... I am expecting things like messaging bus bindings to come up at some point too :) ) 18:27:12 edwarnicke___: *nod* 18:32:37 #info dmm calls for questions before the vote on this project to incubation 18:38:01 @kent: get well! 18:38:21 #info kwatsen asks "is this a fundamental issue with OF1.3, and is this a proposal for how ODL will solve it? 18:39:40 #info colindixon notes that the options of OF1.3 need bounds. the TTPs are a method to do that from the ONF… Support for these in ODL is the essence of this proposal 18:41:01 #info dmm calls for the vote "does the TSC want to move NDM project to incubation"? 18:41:24 #topic vote on NDM project to incubation 18:41:25 #topic vote on NDM to Incubation 18:41:33 #info +1 18:41:36 #info +1 18:41:44 #info +1 18:41:50 #info +1 18:41:52 #info +1 18:41:56 #info +1 18:42:10 colindixon, you could have delegated somebody else as TSC for a moment :) 18:42:23 #agreed TSC approves the NDM project to incubation 18:42:23 #agreed NDM to incubation 18:42:34 this is becoming funny :) 18:42:38 :-) 18:42:46 and the peasants rejoiced? 18:42:52 colindixon: related question (not to review but to NDM) 18:42:59 where is the link to the NDM proposal on the wiki? 18:43:00 Duplicate notes is better than no notes :) 18:43:11 #info colindixon calls for all/any additional help on this project is welcome 18:43:16 colindixon: plan to attempt to include on helium 18:43:19 drizzt_: https://wiki.opendaylight.org/view/Project_Proposals:Negotiable_Datapath_Models 18:43:22 @drizzt_ https://wiki.opendaylight.org/view/Project_Proposals:Negotiable_Datapath_Models 18:43:24 #topic Stable Release Branch 18:43:40 cdub: our hope is to participate 18:43:41 thank you! 18:44:16 For some reason wasn't listed here: https://wiki.opendaylight.org/view/Project_Proposals:Main 18:44:22 #info cdub notes no substantial updates… effort moving forward, projects working on the effort, some projects are farther along than others. 18:44:59 #info dmm notes he will keep this as a standing agenda item 18:45:38 #info regXboi asks for the tag to follow the email - what to follow and post against 18:46:10 #info cdub notes the discussion on discuss and each project contact 18:46:53 +1 18:46:55 #info dmm asks for any last pressing issues before closing 18:47:01 +1 And the peasants rejoiced :) 18:47:10 #endmeeting