17:00:05 #startmeeting OpenDaylight TSC Meeting 2014-05-08 17:00:05 Meeting started Thu May 8 17:00:05 2014 UTC. The chair is phrobb. Information about MeetBot at http://ci.openstack.org/meetbot.html. 17:00:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:05 The meeting name has been set to 'opendaylight_tsc_meeting_2014_05_08' 17:00:08 running late 17:00:24 dmm: I do not (as far as I know) have delegation today 17:01:45 #topic TSC members please #info in 17:02:13 * regXboi waits for webex 17:02:30 #info Rob Dolin proxy for Rajeev Nagar (Microsoft) 17:02:56 #info Chris Wright 17:03:04 #Info Chris O'Shea proxy for Chris Price (Ericsson) 17:04:04 @RobDolin: welcome 17:04:16 #info Kent Watsen 17:04:37 #info dmm 17:05:05 * regXboi now watches the spinning ball :( 17:05:14 regXboi: Its candy hitting a fan 17:05:30 I'm having some webex issues... still trying 17:07:17 #chair regXboi edwarnicke RobDolin 17:07:17 Current chairs: RobDolin edwarnicke phrobb regXboi 17:07:43 #topic Agenda Bashing 17:07:47 #link https://wiki.opendaylight.org/view/TSC:Main#Agenda_Summary (agenda) 17:08:06 #info Ed Warnicke 17:08:06 #info regXboi for IBM ( I *do* hold the proxy today) 17:08:19 * edwarnicke feels sorry for our poor beleaguered agenda 17:08:26 always being bashed ;) 17:08:35 edwarnicke: really? 17:08:51 #topic Event Updates 17:09:17 #link http://www.opendaylight.org/events/2014-05-12/openstack-summit-atlanta 17:09:37 could be ksh'ing, zsh'ing, dashing 17:09:46 #info dmm mentions that TSC members will be at OpenStack next week and hopes for running the call next week from the summit 17:09:47 #info Kent Watsen 17:10:03 cdub: Oh man. 17:10:05 #topic At-Large TSC member election update 17:10:17 phrobb: you get the topics, I'll take the info 17:10:18 * cdub hands dmm an airhorn 17:10:53 * edwarnicke breaks out his protective ear gear 17:11:23 #info board meeting was held last night and the "option 1" proposal was discussed (removing the "unless otherwise represented" language for platinum members). 17:11:38 #info board approved with the stipulation that this clause only applies to the forthcoming election 17:11:59 #info so by-laws return to the original form for the next election 17:13:17 #topic Committer Promotions 17:13:39 #link https://wiki.opendaylight.org/view/Group_Policy:Main (Group Policy) 17:13:50 phrobb: is it committer promotions or replacement ? 17:13:54 #info proposal: keith burns and rob adams to committer for group based policy 17:14:05 the email sounded like replacing committers due to unavailability of existing commiters 17:14:10 madhu: that is a good question 17:14:21 er Madhu: that is a good question 17:14:22 not sure.. just copied the agenda item 17:16:49 I don't see why we need to remove anyone 17:17:36 it is not about removing anyone actuallyy 17:17:40 #link https://lists.opendaylight.org/pipermail/tsc/2014-May/001172.html (relevant list thread) 17:17:47 cdub: thanks 17:17:57 the question was due to previous decisions to add committers 17:18:17 and questions raised earlier about contributions etc. 17:18:26 for existing projects 17:22:11 #info luis asks, can a committer voluntarily drop committer responsbility 17:22:29 * cdub was going to suggest that we add that to the charter 17:22:35 but it's offtopic for this 17:22:57 #startvote "Shall we promote Kieth Burns and Rob Adams to Committer of Group Based Policy Project? 1, 0, -1 17:22:57 Begin voting on: "Shall we promote Kieth Burns and Rob Adams to Committer of Group Based Policy Project? Valid vote options are 1, 0, -1. 17:22:57 Vote using '#vote OPTION'. Only your last vote counts. 17:23:07 #info we don't have charter mechanism for that, while could be useful, it's offtopic 17:23:07 #vote +1 17:23:07 RobDolin: +1 is not a valid option. Valid options are 1, 0, -1. 17:23:11 #vote +1 17:23:11 dmm: +1 is not a valid option. Valid options are 1, 0, -1. 17:23:12 #vote +1 17:23:12 cdub: +1 is not a valid option. Valid options are 1, 0, -1. 17:23:13 #vote +1 17:23:13 edwarnicke: +1 is not a valid option. Valid options are 1, 0, -1. 17:23:16 #vote 1 17:23:17 #vote 0 17:23:20 @vote 1 17:23:20 #vote 1 17:23:25 #vote 0 17:23:26 #vote 1 17:23:33 Sorry, I voted "+1" instead of "1" 17:23:35 turns out i can't read 17:23:35 #vote 1 17:23:49 #endvote 17:23:49 Voted on ""Shall we promote Kieth Burns and Rob Adams to Committer of Group Based Policy Project?" Results are 17:23:49 1 (4): cdub, ChrisOShea, dmm, edwarnicke 17:23:49 0 (2): kwatsen, regXboi 17:23:54 cdub: evidently my literacy is also questionable ;) 17:24:09 Thanks everyone! 17:24:10 It's 4-0-2 17:24:11 edwarnicke: maybe it's a prereq for this vote? 17:24:29 Thanks folks 17:24:40 Congratulations Keith Burns and Rob Adams 17:24:50 #agreed Keith Burns and Rob Adams are now Committers on the Group Based Policy Project 17:24:56 #info Ryan Moats (IBM) suggests this should be a special case and not a precedent 17:24:57 RobDolin: Thanks sir 17:25:01 regXboi: this is exactly what i was worried about :) 17:25:06 * edwarnicke suggestions we add #congratulations to meetbot :) 17:25:18 * regXboi hugs meetbot 17:25:23 #topic Creation Reviews 17:25:23 edwarnicke: or #suggestions ;) 17:25:38 tbachman: #happydance :) 17:25:41 lol 17:26:09 i'm sure meetbot has a #patchesaccepted policy 17:26:22 #topic Creation-Review: ODL-SDNi App 17:26:45 cdub: I'm sure it does... but the results may prove too... entertaining ;) 17:26:53 which code scan product? 17:27:10 dkehnx: Check in with Phil... he handles it 17:27:12 presentation that does not have a link does not exist 17:27:38 phrobb, which code scan product was being referred to? 17:27:45 #link https://wiki.opendaylight.org/view/Project_Proposals:ODL-SDNi_App (SDNi Project Proposal) 17:27:51 #link https://wiki.opendaylight.org/view/File:SDNiAppProposal1.ppt <-- slides 17:27:55 @dkehnx Combination of FOSSology and Sonatype Component LifeCycle Manager 17:28:17 phrobb, thx 17:30:12 #info question about whether this is hardcoded or user defined 17:32:49 phrobb: please scribe - I have some questions :) 17:33:00 regXboi: you got it 17:33:33 Q: regXboi asks "since this isn't clustering, are you assuming you are federating controllers in some way?" 17:33:58 #info Q:  regXboi asks "since this isn't clustering, are you assuming you are federating controllers in some way?" 17:34:49 #Info Q in particular what does this project add above existing clustering capabilities? 17:35:25 #info A We are trying to establish a federation of controllers - different controllers from different domains 17:38:49 I'm curious how you get "the best possible route" when network topology is in the "Extendable to:" section... 17:43:11 #info Q: Concern this is federation based on BGP - issues with securing the data flowing between the domains 17:43:33 #info Q what is the plan to secure the trust-path? 17:45:10 #info A: This is a known issue with BGP, with solutions being worked on 17:46:18 phrobb: thanks for scribing - as I said I had questions :) 17:46:41 #info I think sacurity of this is being handled in the sidr IETF working group 17:46:47 #info there are dependencies on existing ODL-BGPCEP project and those are being taken into account in the release plan 17:47:13 #link https://wiki.opendaylight.org/view/Simultaneous_Release:Helium_Release_Plan#Participating_Projects - place to list yourself and your release plan (by Monday 5/12) if you want to join Helium 17:48:10 #info Q: Is this the first proposal that has described cross-domain federation? 17:48:17 I’ll jump in after dmm 17:48:36 #info A: yes and for opendaylight, things are bottom up 17:49:00 #info A: This is the first federation type of proposal, everything before has been more clustering focused… 17:50:37 #info With a clustering datastore working, similar functionality is exists but having a more federation-view is also a valid methodology. 17:51:08 #info Is there any provision for different controllers having similar/compatible functionality? 17:53:21 #info Current plan is to share the data provided in this presentation. More information can be shared in the future 17:54:00 #startvote Shall SDNi be moved to Incubation? +1, 0 -1 17:54:00 Begin voting on: Shall SDNi be moved to Incubation? Valid vote options are +1, 0, -1. 17:54:00 Vote using '#vote OPTION'. Only your last vote counts. 17:54:08 #vote 1 17:54:08 regXboi: 1 is not a valid option. Valid options are +1, 0, -1. 17:54:09 #vote 1 17:54:09 edwarnicke: 1 is not a valid option. Valid options are +1, 0, -1. 17:54:13 #vote +1 17:54:14 #vote 1 17:54:14 dmm: 1 is not a valid option. Valid options are +1, 0, -1. 17:54:17 #vote +1 17:54:29 #vote +1 17:54:31 #vote +1 17:54:38 #vote +1 17:54:43 #vote +1 17:54:59 #endvote 17:54:59 Voted on "Shall SDNi be moved to Incubation?" Results are 17:54:59 +1 (6): ChrisOShea, regXboi, dmm, edwarnicke, cdub, kwatsen 17:55:18 Who is ChrisOShea? 17:55:21 congratulations! 17:55:28 Filling in for Chris Prices 17:55:29 edwarnicke: ChrisPrice's proxy 17:55:29 Oh :) 17:55:36 Apologies :) Missed that 17:55:38 #agreed ODL-SDNi is moved to Incubation 17:55:42 nice! 17:56:09 #topic Creation Review - South Bound Plugin To The OpenContrail Platform 17:57:22 we need a link for the slides 17:57:46 dmm: can we get a #link for slides? 17:58:42 dmm: thanks 17:58:50 #info I have to upload the slides to the wiki first 17:59:15 Here's the project proposal: 17:59:17 #link https://wiki.opendaylight.org/view/Project_Proposals:Southbound_plugin_to_the_OpenContrail_platform (Southbound plugin to the OpenContrail platform Proposal) 18:02:28 is it targeted for Virt edition only ? 18:03:04 for proposlas, there are no editions 18:03:20 heh, a new kind of sla, a proposla 18:04:12 #info LuisGomez notes that the proposal seems to propose a completely vertically integrated approach with calls going from the Neutron plugin to their SB plugin and then to OpenContrail, he asks if there are any plans for more integration in the future. 18:04:26 cdub: thanks 18:04:44 #info answer is that they may integrate more in the future, but for now the veritcal integration is the plan for the first release efforts 18:05:22 thanks colindixon 18:05:30 phrobb: no worries 18:10:23 #info Question raised on added value expected from including OpenContrail plugin within OpenDaylight? 18:10:28 thanks 18:11:39 #info A: there have been customers wanting to manage OpenContrail-manged networks along with other types of networks all from OpenDaylight 18:12:39 am confused on this policy 18:13:01 doesnt openDOVE or VTN fall under the same question ? 18:13:02 southbound REST_API sounds weird 18:13:16 #info Q: Given that Board has a Vendor-Neutral policy, can the TSC decide on this name? 18:14:13 #info A: dmm states that we will be only voting on the project. The name of the project is still TBD until the Board decides on OpenDaylight's "Vendor Neutral" policy 18:17:41 would like to know what else they are interested in contributing too. Would be sweet to see more then just the sbound driver. 18:18:06 #startvote "Shall the TSC give conditional approval the Southbound Plugin to the OpenContrail platform" to Incubation.. two conditions 1) the name to be used for the project not decided, and 2) a successful code scan? +1, 0, -1 18:18:06 Begin voting on: "Shall the TSC give conditional approval the Southbound Plugin to the OpenContrail platform" to Incubation.. two conditions 1) the name to be used for the project not decided, and 2) a successful code scan? Valid vote options are +1, 0, -1. 18:18:06 Vote using '#vote OPTION'. Only your last vote counts. 18:18:27 #vote 1 18:18:27 kwatsen: 1 is not a valid option. Valid options are +1, 0, -1. 18:18:28 #vote +1 18:18:28 #vote +1 18:18:33 #vote +1 18:18:33 #vote +1 18:18:34 #vote +1 18:18:39 #vote +1 18:19:11 #vote 0 18:19:16 #endvote 18:19:16 Voted on ""Shall the TSC give conditional approval the Southbound Plugin to the OpenContrail platform" to Incubation.. two conditions 1) the name to be used for the project not decided, and 2) a successful code scan?" Results are 18:19:16 0 (1): cdub 18:19:16 +1 (6): ChrisOShea, regXboi, edwarnicke, dmm, kwatsen, RobDolin 18:20:25 #agreed Conditional approval of project proposal 18:20:32 #topic Hydrogen Stable Release 18:21:14 #link https://wiki.opendaylight.org/view/CrossProject:Stable_Release 18:21:38 #link https://lists.opendaylight.org/pipermail/tsc/2014-May/001156.html <-- mail thread 18:24:22 #info discussion ongoing on list. Proposal made to not Cherrypick all changes to master. Instead pick a point in time and copy master to stable-branch then pull non-bug-fix patches from the stable copy. Discussion is ongoing 18:27:59 #info cdub suggests maybe getting the specific projects that are having the problem of cherrypickig bug-fixes from master to do the mass-copy. Other projects that have not had that much delta or cross-project-dependencies can just cherrypick the bug-fixes. 18:28:27 so I think the ask is to do this for yangtools and controller 18:30:22 rovarga: it's wider than that 18:30:49 rovarga: at least Abhijit replied effective +1 as well 18:32:28 cdub: yes, I know. yangtools and controller are the critical ones, as they are the ones blocking all others 18:32:36 Madhu: it looks like this: hydrogen->patch->pactch->patch->patch->patch[now] 18:33:10 now name them A and B (A==stable B==not), hydrogen->A->B->A->B-> 18:33:24 you can eityher start w/ dropping B's or applying A's 18:33:32 personally, makes no sense to drop B's 18:33:49 but the projects are saying this works 18:35:30 dmm: I'm good 18:36:21 #topic Developer Best Practices 18:36:32 #link https://wiki.opendaylight.org/view/Developer_Best_Practices 18:37:51 cdub: if that works for projects... thats fine. but end of the day it has to be stable. 18:38:01 Madhu: totally agree 18:38:04 Madhu: time will tell 18:38:09 but it is weird on the approach we are taking. 18:38:16 Madhu: shows the the modulraity is...not 18:38:17 maybe this learning is good for helium post 18:38:42 to start this stable/helium right away and never have to rewind or having this discussion half way 18:38:51 and many wasted efforts by many 18:39:08 cdub: i don't want to blame modularity :) 18:39:12 yes, it's in the release planning for helium 18:39:18 Madhu: why not? it's true 18:39:51 Agree. If we create the stable/helium concurrent with the helium release and require double commits for fixes, this should not be an issue 18:40:27 cdub: i was not clear. modularity will help if we follow that in practice. 18:41:24 Madhu: ah, yup. agree. and it's _always_ tough to do cross-service (interdependent) changes...bugs should capture that inter-dependency 18:41:46 #info request is for TSC to advocate/strongly-encourage all projects in OpenDaylight to comply with 2 recommendations: 1) Build Time Testing, and 2) Comments documenting the code 18:42:56 turns out it's not apple pie...it's a apple brown betty 18:43:41 #info comments made that this is "Motherhood and Apple pie", *but* we should probably look at a stylecheck rule that documentation is done with to succeed a build cycle 18:45:17 #info On commenting - not having comments is the exception not the norm… ie it must be explained why the comment is not there. 18:46:29 “Always code as if the person who ends up maintaining your code is a violent psychopath who knows where you live.” http://c2.com/cgi/wiki?CodeForTheMaintainer 18:46:42 heh 18:46:54 -> Austin ! 18:48:25 I don’t think the TSC *can* mandate these things, but this is the venue where we can raise the issue and put pressure on people in the ways that we can 18:50:13 ok...i mandate that we stop (ab)using "motherhood and apple pie" 18:50:20 colindixon: yes. or, as I tell my devs: "imagine you will come back to this pile in 5 years and try to make sense of it" 18:50:22 +1000 18:50:32 have never heard of so many times someone saying that :) 18:51:10 I’m 99% sure that devinavery wasn’t trying to say the TSC should mandate this, but should raise attention to the fact that, at least for some people, joining from the outside, we haven’t been doing as good a job as we should to make code accessible 18:51:25 and here are some concete suggestions 18:52:47 I think we need to create a 'cookbook' of recommendations on which committers agree 18:52:53 #link https://pad.opendaylight.org/p/DevelopmentBestPractices <-- here's what i wrote down as things to consider 18:52:57 #info devinavery to continue this discussion on the list 18:53:04 cookbook as in -- how do I do this easily 18:53:09 devinavery: How can I help you on getting some checkstyle stuff going? 18:53:15 action devinavery to continue this discussion on the list 18:53:15 and let committers enforce it how they feel it's appropriate 18:53:29 I have a checkstyle bundle that can be be included as a maven dependency 18:53:36 #action devinavery will send a mail out to start this discussion about code best practices 18:53:38 We could start from that 18:53:41 #topic ovsdb.neutron in SP edition 18:53:53 edwarnicke: checkstyle is busted for me, can you help me debug it? 18:54:39 #info madhu asks TSC " given the interest from the users, should we add ovsdb integration project to the SP edition?" 18:55:36 edwarnicke: I wasn't actually suggesting stylechecking. I believe the ball has to lie with the committers to encourage comments and unit tests. I believe at this point we would spend more time mandating and building controls instead of just commenting and testing. :) Will add more in e-mailto the lists 18:56:25 I would ask that the TSC review the "release vehicles" and their intentions for the release vehicles before Helium. 18:56:44 #info dmm notes that this request is also to add ovsdb to Hydrogen SP release 18:56:45 @ChrisPriceAB -- that's in the release plan 18:57:10 thanks, will check it. only able to follow on IRC today. :) 19:00:18 #info dmm suggests that we take this discussion to the List to further explore ovsdb inclusion into stable hydrogen release of the SP edition 19:00:33 #endmeeting