17:00:32 #startmeeting tsc 17:00:32 Meeting started Thu Apr 7 17:00:32 2016 UTC. The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html. 17:00:32 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:32 The meeting name has been set to 'tsc' 17:00:36 #topic agenda bashing and roll call 17:00:44 TSC members please #info in 17:00:45 #info Chris Price 17:00:46 #info rovarga proxy for jmedved 17:00:49 #info colindixon 17:00:54 #info gkaempfer 17:01:08 #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=45118#Agenda the agenda 17:01:10 #info Daniel Farrell 17:01:17 #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-03-31-17.00.html lat week's meeting minutes 17:01:43 #action colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron? 17:01:44 #action zxiiro will look more into maven central now that we're at least signing things 17:01:53 #undo 17:01:53 Removing item from minutes: 17:02:01 #link https://bugs.opendaylight.org/show_bug.cgi?id=5630 Releasing artifacts to Maven Central 17:03:03 #link https://lists.opendaylight.org/pipermail/tsc/2016-April/004994.html thread on a hackfest in June 17:03:22 #info LuisGomez 17:03:50 #link https://lists.opendaylight.org/pipermail/release/2016-April/006203.html mail about build failures in autorelease, but not in projects 17:03:58 #info mohnish anumala 17:04:19 #link https://lists.opendaylight.org/pipermail/project-proposals/2016-April/000477.html colin following up with cardinal after their creation review 17:04:55 #action tykeal or somebody else to write up and send an e-mail about signing commits in gerrit 17:05:25 tykeal: feel free to send that to me, too 17:05:30 tykeal, colindixon : my key should work too. I'll play test dummy 17:05:50 ah, yes colindixon you key is setup in a way that should work with it 17:06:38 #action ChrisPriceAB, phrobb, phrobb_, gzhao, CaseyODL and others to help coordinate a bit between ODL and OPNFV at the OpenStack summit to have better presence 17:06:43 #info waiting for a chance, after crazy travel schedules, to get everyone on the phone to sort this out. 17:07:02 jamoluhrsen: yours might work, but it's hard to say. You've got a signing key on your master, but you've also got a signing subkey. Depends upon how you use your keys... 17:07:32 rovarga: you're in the same camp as jamoluhrsen 17:07:36 #topic mailing list votes and discussions 17:08:28 #link https://lists.opendaylight.org/pipermail/tsc/2016-April/005007.html TSC elections for comitters-at-large for 5-months (throught the end of Boron) 17:08:41 #Info please nominate yourself if you'd like to run for one of the four committer-at-large seats we have 17:08:55 #Info it's worth noting there can only be one winner per unaffilated company 17:09:07 colindixon: as far as I know, we have 2 panels and 1 demo theater presentation for ODL at Openstack, current, there are 5 projects signed up for demo at ODL booth, but not all will have representative to present. 17:09:23 #info it will not displace platinum designates though 17:10:18 #link https://lists.opendaylight.org/pipermail/tsc/2016-March/004956.html MPLS-TP service creation review over e-mail (comments there would be appreciated) 17:10:44 #info there are two MPLS-TP projects under review, so be aware fo that 17:11:10 #link https://lists.opendaylight.org/pipermail/tsc/2016-March/004928.html thread on cleaner committer lists 17:12:12 #link https://lists.opendaylight.org/pipermail/tsc/2016-April/005002.html continued in April 17:14:06 We are at 7 TSC members. We have quorum 17:14:18 sounds good 17:14:43 #startvote shall the TSC ask projects to carry out keeping clean committer lists every six months as described here: https://lists.opendaylight.org/pipermail/tsc/2016-April/005002.html ? -1,0,+1 17:14:43 Begin voting on: shall the TSC ask projects to carry out keeping clean committer lists every six months as described here: https://lists.opendaylight.org/pipermail/tsc/2016-April/005002.html ? Valid vote options are -1, 0, +1. 17:14:43 Vote using '#vote OPTION'. Only your last vote counts. 17:14:50 #vote +1 17:14:52 #vote +1 17:14:52 #vote +1 17:14:52 #chair phrobb phrobb_ anipbu 17:14:52 Current chairs: anipbu colindixon phrobb phrobb_ 17:14:55 #vote +1 17:14:56 #vote +1 17:14:58 #vote +1 17:15:00 #vote +1 17:15:08 #endvote 17:15:08 Voted on "shall the TSC ask projects to carry out keeping clean committer lists every six months as described here: https://lists.opendaylight.org/pipermail/tsc/2016-April/005002.html ?" Results are 17:15:08 +1 (7): rovarga, LuisGomez, dfarrell07, ChrisPriceAB, gkaempfer, mohnish_, colindixon 17:15:25 #agreed the TSC asks projects to carry out keeping clean committer lists every six months as described here: https://lists.opendaylight.org/pipermail/tsc/2016-April/005002.html 17:15:47 #action colindixon to copy this into the TSC main page under processes and procedures: TSC ask projects to carry out keeping clean committer lists every six months as described here: https://lists.opendaylight.org/pipermail/tsc/2016-April/005002.html 17:16:09 #action anipbu or colindixon to send an announcement to the release@ list 17:16:15 #Undo 17:16:15 Removing item from minutes: 17:16:23 #action anipbu or colindixon to send an announcement to the release@ list about removing inactive committers 17:16:29 colindixon: thanks 17:16:34 rovarga: thank you 17:16:36 #topic events 17:16:43 #link https://www.opendaylight.org/global-events 17:16:57 #info SDN/NFV conference next week in Beijing, neela will be speaking 17:17:19 #info OpenStack in Austin at the end of the month, gzhao and CaseyODL are seekiing demos for the ODL booth (contact them) 17:17:36 #Info CFPs for opendaylight mini summit in late june 17:17:47 #info CPFs for opendaylight summit in september is open 17:18:23 in favour 17:18:31 but as an external stakeholder 17:18:36 +1 for hackfest 17:18:40 #link https://lists.opendaylight.org/pipermail/tsc/2016-April/004994.html planning a hackfest 17:18:53 June - folks are on a vacation - I am :) 17:19:01 #Info ChrisPriceAB, jamoluhrsen, LuisGomez, and others are in favor 17:20:07 #info colindixon notes that hackfests have been only OK in his experience, atttendance has been light, maybe we could get by with just DDFs? 17:20:59 #Info maybe just the integration team could set one up, phrobb_ notes that this was really for cross-project stuff originally, but that's been happening less than hoped 17:21:51 #info phrobb_ says that if it's really just the integration team getting value, do a smaller thing for just them might the right approach 17:22:21 #info maybe anipbu to poll projects if they would have people attend 17:23:22 #Info rovarga suggests if there was a way to put it between API freeze of offset 0 and offset 2, colindixon notes we've tried to do that in the past, it hasn't seemed to increase attendance 17:23:53 #info ChrisPriceAB asks if we had more cocrete foci would help, it's a good idea 17:23:58 #info clarification: June is in M4 land offset-0 is 6/2, offset-2 is 6/30 17:25:12 If rovarga suggestion of pre M3 is OK with me timing wise (May or May end) is fine with me timing wise 17:25:19 #action phrobb_ to poll projects about whether they would attend and what they would attend for with each project 17:25:45 hackfest could turn in to bugfest, or docfest or createtutorialsfest 17:26:04 #info phrobb_ asks if we're anticipating doing anyting w.r.t. doing fast-phased or sematic versionion for carbon, so we can get moving on it now, before Carbon 17:26:16 edwarnicke: 17:26:33 phrobb_: that would be a good topic for a hackfest? 17:27:19 #action colindixon to ping skitt and edwarnicke about carbon planning w.r.t. fast-phased and sematic version, dfarrell07 notes that it would be a good thing for a hackfest 17:27:25 #topic boron 17:27:44 #link https://wiki.opendaylight.org/view/Weather#Current_Weather_Report 17:27:50 +1 jamoluhrsen 17:28:23 #Info jamoluhrsen suggests hackfests turn into mabye bugfixfest or maketutorialsfest 17:28:50 +1 jamoluhrsen 17:29:29 #info we are currently tracking OpenFlow Plugin moving to lithium, we want all feedback on isuses by today (still waiting on 8 project ) 17:29:37 #info still waiting for M1 for 5 projects 17:29:49 #info today is boron M2 for offset 0 projects 17:30:00 #Info some autorelease breakages with OVSDB SB 17:30:13 #link https://lists.opendaylight.org/pipermail/tsc/2016-March/004963.html formally approve the boron release plan 17:30:59 #link https://lists.opendaylight.org/pipermail/release/2016-March/006121.html making features experimental unless they have fulfilled system test requiments 17:32:02 #info colindixon notes that his feeling is that we could approve the Boron release plan as-is given that it's had lots of opportunity for feedback and only one real discussion has happened (see above) 17:32:45 #Link https://lists.opendaylight.org/pipermail/release/2016-April/006166.html some clarifications around stable features 17:34:05 #action colindixon to make clarifications to the release plan per https://lists.opendaylight.org/pipermail/release/2016-April/006166.html 17:35:15 #info ChrisPriceAB asks who sets the bar for system tests? colindixon answers that it's written by the integration team, and approved by the TSC, Boron is identical to Beryllium at the moment. 17:35:47 #startvote shall the TSC formally adopt the Boron release plan here: https://wiki.opendaylight.org/view/Simultaneous_Release:Boron_Release_Plan ? -1,0,+1 17:35:47 Begin voting on: shall the TSC formally adopt the Boron release plan here: https://wiki.opendaylight.org/view/Simultaneous_Release:Boron_Release_Plan ? Valid vote options are -1, 0, +1. 17:35:47 Vote using '#vote OPTION'. Only your last vote counts. 17:35:57 #vote +1 17:35:59 #vote +1 17:35:59 #vote +1 17:36:02 #vote +1 17:36:02 #vote +1 17:36:05 #vote +1 17:36:07 #vote +1 17:36:10 #endvote 17:36:10 Voted on "shall the TSC formally adopt the Boron release plan here: https://wiki.opendaylight.org/view/Simultaneous_Release:Boron_Release_Plan ?" Results are 17:36:10 +1 (7): gkaempfer, LuisGomez, dfarrell07, ChrisPriceAB, colindixon, mohnish_, rovarga 17:36:35 #agree the TSC formally adopts the Boron release plan here: https://wiki.opendaylight.org/view/Simultaneous_Release:Boron_Release_Plan 17:37:20 #topic EPC OpenFlow Extension creation review 17:37:20 #link https://wiki.opendaylight.org/view/Project_Proposals:EPC_OpenFlow_Extension 17:37:31 #link https://lists.opendaylight.org/pipermail/project-proposals/2016-March/000436.html proposed on 3/16/2016 17:38:01 #info the idea is to extend OpenDayligtht to be able to control EPC infrastructure using OpenFlow via vendor-specific OpenFlow OXMs 17:38:28 #info this is mostly controlling GTP tunnels using the GTP-U protocol 17:38:49 #info they explored contributing them directly to the OpenFlow plugin project, the answer seemed to be no 17:40:15 #info in the future, we likely would like to have a simpler way to add openflow extensions than one project per openflow extension 17:40:39 #info colindixon notes that this should probably be called ofextensions/epc not epcofe 17:41:00 #info colindixon notest that the scope is impled, but mostly seems to be in the description 17:43:03 #info mohnish_ asks abhijitkumbhare if there's a mechanism if doing these kind of extensions is there, abhijitkumbhare says yes that mechanism exists, and it should be doable across git repositories as well 17:43:44 #Info rovarga suggests that maybe ofextensions should be openflow/extensions and we should also have openflow/plugin and openflow/java (or openflow/library) 17:44:28 can nobody hear me? 17:44:36 no 17:45:03 crap 17:45:12 so this is a good discussion, but we need to move on 17:45:56 agree colindixon 17:46:34 ofextensions/epc makes sense 17:47:00 #action kobyaizer to change the name from epcofe to ofextensions/epc 17:47:49 #actoin abhijitkumbhare, rovarga and others to schedule time (on the TWS) about openflow project reorganzation 17:47:57 #action abhijitkumbhare, rovarga and others to schedule time (on the TWS) about openflow project reorganzation 17:48:26 #startvote shall the TSC move the OpenFlow EPC project to incubation? -1,0,+1 17:48:26 Begin voting on: shall the TSC move the OpenFlow EPC project to incubation? Valid vote options are -1, 0, +1. 17:48:26 Vote using '#vote OPTION'. Only your last vote counts. 17:48:34 #vote +1 17:48:36 #vote +1 17:48:44 #vote +1 17:48:52 #vote +1 17:48:55 #Info rovarga notes that it woudl be good to have a plan ready for OF projects organization that before we get to Carbon 17:49:01 #vote +1 17:49:05 #vote +1 17:49:06 #vote +1 17:49:10 #endvote 17:49:10 Voted on "shall the TSC move the OpenFlow EPC project to incubation?" Results are 17:49:10 +1 (7): gkaempfer, rovarga, LuisGomez, dfarrell07, ChrisPriceAB, colindixon, mohnish_ 17:49:13 is there IPR needed? 17:49:26 #agreed OF EPC is a now an inbation project 17:50:16 #starvote shall the TSC allow the OF EPC project to join the boron release at offest 2? -1,0,+1 17:50:21 #startvote shall the TSC allow the OF EPC project to join the boron release at offest 2? -1,0,+1 17:50:21 Begin voting on: shall the TSC allow the OF EPC project to join the boron release at offest 2? Valid vote options are -1, 0, +1. 17:50:21 Vote using '#vote OPTION'. Only your last vote counts. 17:50:30 #vote +1 17:50:31 #vote +1 17:50:32 #vote +1 17:50:38 #vote +1 17:50:38 #vote +1 17:50:40 #Info colindixon notes that in later releases if others want to use it, it should really be offset 1 with the OF plugin 17:50:43 #vote +1 17:50:45 #endvote 17:50:45 Voted on "shall the TSC allow the OF EPC project to join the boron release at offest 2?" Results are 17:50:45 +1 (6): rovarga, dfarrell07, ChrisPriceAB, gkaempfer, colindixon, mohnish_ 17:50:55 #agree the OF EPC project can join boron at offest 2 17:51:00 #topic NetVirt creation review 17:51:11 #link https://wiki.opendaylight.org/view/Project_Proposals:NetVirt 17:51:25 #link https://lists.opendaylight.org/pipermail/project-proposals/2016-March/000455.html 3/24/2016 17:51:43 congrats kobyaizer and the OF EPC team! 17:52:11 phil feeling a little hussled 17:52:29 #action shague to post slides to the wiki so we can link to them later 17:52:46 colindixon: the slides are in the proposal 17:53:05 #link https://docs.google.com/presentation/d/16c-NT19x3dbPrTjPIV5WxKcKrFfURsTLBD4D5n-pOCo/edit#slide=id.g10faa1e6d3_1_16 17:53:07 #info OVSDB has had two halves since nearly the beginning of OpenDaylight, an OVSDB SB plugin and a Neutron OpenStack plugin using that SB plugin (and OpenFlow plugin) 17:53:12 rovarga: thanks 17:53:22 #und 17:53:24 #undo 17:53:24 Removing item from minutes: 17:53:25 #undo 17:53:25 Removing item from minutes: 17:53:26 #undo 17:53:26 Removing item from minutes: 17:53:34 #link https://docs.google.com/presentation/d/16c-NT19x3dbPrTjPIV5WxKcKrFfURsTLBD4D5n-pOCo/edit#slide=id.g10faa1e6d3_1_16 sldies 17:53:39 #info OVSDB has had two halves since nearly the beginning of OpenDaylight, an OVSDB SB plugin and a Neutron OpenStack plugin using that SB plugin (and OpenFlow plugin) 17:54:53 #info the main reason for the split is to separate the part that lots of other projects use (the SB) from the one that others mostly don't (NetVirt) this will fix offset issues and a dependency cycle with SFC 17:55:16 #info also OSVSDB said they'd do this when their scope was revised during Beryllium 17:56:55 #info rovarga says htanks for following up 17:57:20 +1 thanks for doing this. It'll make releasing much easier for releng. 17:58:27 #info colindixon asks how we can up with the list of committers, shague says the only difference is adding Andre and removing Flavio voluntarily from the list 17:58:48 #info colindixon notes that in the past there was contention over the project being named netvirt, asks if anyone has issues with that 17:58:54 #info nobody seems to 17:59:42 actually the name isn't ideal, but IMO it would be more confusing to change the name at this stage 18:00:20 #startvote shall the TSC create teh NetVirt project as an mature project as a spin out of the OVSDB project which is also mature? -1,0,+1 18:00:20 Begin voting on: shall the TSC create teh NetVirt project as an mature project as a spin out of the OVSDB project which is also mature? Valid vote options are -1, 0, +1. 18:00:20 Vote using '#vote OPTION'. Only your last vote counts. 18:00:26 #vote +1 18:00:27 #vote +1 18:00:27 #vote +1 18:00:28 #vote +1 18:00:31 #vote +1 18:00:33 #vote +1 18:00:33 #vote +1` 18:00:33 gkaempfer: +1` is not a valid option. Valid options are -1, 0, +1. 18:00:38 #vote +1 18:00:41 #endvote 18:00:41 Voted on "shall the TSC create teh NetVirt project as an mature project as a spin out of the OVSDB project which is also mature?" Results are 18:00:41 +1 (7): gkaempfer, rovarga, LuisGomez, ChrisPriceAB, dfarrell07, colindixon, mohnish_ 18:01:01 the only issue I have with making it mature is the committers are not the original committers. makes me wonder where the line is 18:01:03 congrats OVSDB, and thanks again for doing it 18:01:05 #agreed the NetVirt project is now a mature project 18:01:24 #info ChrisPriceAB notes that the only issue I have with making it mature is the committers are not the original committers. makes me wonder where the line is 18:01:27 Thanks! 18:01:48 colindixon: don't forget to endmeeting 18:01:58 colindixon: and cookies! 18:01:59 :) 18:02:06 #action colindixon to start a thread on how split out projects inherit or don't their parent project's lifecycle state, but notes in this case (OVSDB) when ediscussed it before we had agreed it would be done this way 18:02:09 #topic cookies 18:02:12 #endmeeting