17:00:19 #startmeeting TSC 17:00:19 Meeting started Thu Mar 24 17:00:19 2016 UTC. The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html. 17:00:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:19 The meeting name has been set to 'tsc' 17:00:33 #topic agenda bashing and roll call 17:00:38 #info mohnish anumala 17:00:38 TSC members please #info in 17:00:53 #info colindixon 17:01:00 #info edwarnicke 17:01:00 #info Chris Price 17:01:18 #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=44540#Agenda the agenda for today it's usual place 17:01:26 #info Daniel Farrell 17:01:28 #info gkaempfer 17:01:32 #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-03-17-17.00.html last week's meeting minutes 17:01:35 6 17:01:52 #action colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron? 17:02:37 #info LuisGomez 17:02:44 #Link https://lists.opendaylight.org/pipermail/tsc/2016-March/004899.html maintaining cleaner committer lists 17:03:01 #link https://lists.opendaylight.org/pipermail/tsc/2016-March/004933.html thread on openflow plugin lessons learned 17:03:07 * ChrisPriceAB is still fighting with webex... 17:03:16 #action zxiiro will look more into maven central now that we're at least signing things 17:03:36 #action ChrisPriceAB and phrobb_ have heather come and talk to the ODL community about how to have a bigger presence at OpenStack 17:03:56 #topic TSC mailling list votes and discussions 17:03:56 :D 17:04:27 #link https://lists.opendaylight.org/pipermail/tsc/2016-February/004633.html tsc election discussion 17:04:55 #link https://lists.opendaylight.org/pipermail/tsc/2016-March/004922.html meeting minutes from the Board-tech commmunity 17:04:59 #undo 17:04:59 Removing item from minutes: 17:05:04 #link https://lists.opendaylight.org/pipermail/tsc/2016-March/004922.html meeting minutes from the Board-tech commmunity regarding TSC elections 17:05:21 #info after some time for that to quiesce, phrobb will start a movement to makre progress 17:05:29 #action phrobb to drive progress on TSC elections 17:06:08 sounds liker rain... 17:06:09 #link https://lists.opendaylight.org/pipermail/tsc/2016-March/004881.html MPLS-TP project has asked for a creation review over e-mail because of time zone differences 17:07:39 #Info colindixon's inclination is to start a creation review thread to ask for feedback by next week, and the vote in person next week or over e-mail next week 17:07:48 #action colindixon to start creation review thread for MPLS-TP 17:08:06 #link https://lists.opendaylight.org/pipermail/project-proposals/2016-March/000447.html second MPLS-TP-related project proposal 17:08:34 #link https://lists.opendaylight.org/pipermail/project-proposals/2016-March/000454.html some discussion about commonality between the two MPLS-TP project prooposals 17:09:35 #topic events 17:10:12 #action colindixon to figure out when we're willing to make the Boron release plan as something that's not tentative 17:10:20 that would be the week after OPNFV Summint in Berlin 17:10:25 #link https://www.opendaylight.org/global-events 17:10:27 s/Summint/Summit/ 17:10:33 +1 for a hackfest 17:10:38 #Info phrobb asks when we'd like to do a hackfest for Boron, right now that would be at the end of June 17:10:48 #info colindixon, jamoluhrsen, and dfarrell07 say they'd like to have one 17:11:03 #action phrobb to send out a thread about a hackfest at the end of june 17:11:23 #info tykeal notes that the last week in june is the week after the OPNFV summit in berlin 17:11:39 #info OpenStack is the last week in April, peoople make be reaching out for demos at the booth 17:11:53 #info there's a mini-summit for ODL at the OPNFV summit in Berlin 17:12:25 #link https://docs.google.com/forms/d/1hfYPBqK4B6vtSRdhyT5Gbq7aMRjJs7fPzbVl31OEL7M/viewform CFP for ODL mini-summit at the OPNFV summit in Berlin 17:12:30 need more summits in that statement ;) 17:13:12 #link http://events.linuxfoundation.org/events/opnfv-summit/program/cfp OPNFV Summit CFP, closes end of the month 17:13:41 #topic boron 17:13:59 #info Please provide feedback to OpenFlowPlugin by April 7. Meeting on April 4 during TWS to discuss issues/concerns/bugs with OpenFlowPlugin migration efforts. 17:14:05 #link https://wiki.opendaylight.org/view/Weather#Unmerged_Patch_for_projects_to_test_OpenFlow_Plugin_default_design_to_Lithium 17:14:12 #info We are missing the M1 status report from l2switch, snmp, tcpmd5. These projects have been notified. 17:14:18 #info Boron M1 Offset 2 Status is due Today 3/24. This is assuming that we keep with the provisional 17:14:27 #topic stable/beryllium 17:14:39 #info Beryllium-SR1 was shipped, the branch is unlocked, versions were bumped 17:14:54 #info next release is on 4/28 with a cutoff of the sunday before at 11:59p UTC 17:15:03 #topic system integration and test 17:15:26 #info integration/distribution has a new PTL vrpolak (Vratko), congrats! 17:16:12 #info there seems to be some differences between normal tests and the autorelease distributions, e.g., the port conflict issue between NetIDE and VPN service 17:16:29 #info the TWS on Monday will cover (at least for part of it) the changing use of experimental features 17:16:48 #Info jamoluhrsen would like to ask for test contacts to attend 17:17:14 #info abhijitkumbhare notes that Monday is a holiday in europe 17:17:19 #action colindixon jamoluhrsen to work on finding the best time/place to talk about experiemntal features and testing 17:17:25 colindixon, link for Port wiki https://wiki.opendaylight.org/view/Ports 17:17:42 #link https://wiki.opendaylight.org/view/Ports the ports we use for refernece 17:17:48 #topic infrastructure 17:18:03 #info the first things are moving to to the private cloud, things are going well 17:18:15 #info there will be some outages on Saturday, expect flakiness 17:19:02 #action tykeal to forward the outage information to release@lists.opendaylight.org 17:20:25 #info this will be the last jenkins blip for a while, there will be some other outages as we upgrade our infra while we're not near the end of the release, e.g., nexus, sonar 17:20:36 #Info after that, we'll be bringing up the sandbox inside the private cloud and test things 17:20:50 #Info after that we'll start to plan our outage to bring jenkins into the private cloud 17:21:03 #info after that, zuul and nodepool 17:21:22 #topic genius creation review 17:21:31 #link https://wiki.opendaylight.org/view/Project_Proposals:Genius 17:21:42 #link https://lists.opendaylight.org/pipermail/project-proposals/2016-March/000415.html proposed on 3/4/2016 17:22:19 #link http://events.linuxfoundation.org/sites/events/files/slides/ODDF_Generic_Network_functions.pdf 17:23:44 #info this project tries to tackle application co-existences with a focus on OpenFlow 17:24:47 #info colindixon thinks the scope isn't really a scope statement, which should probably be fixed, the description comes a lot closer, so maybe just flopping the two would work? 17:24:51 edwarnicke: ^^^^^^^ 17:24:52 need to ensure SFC is included too as well as the on-going multi writer work 17:25:12 uri_: from scope "generic network services to applications like VPNService, SFC, Netvirt... " 17:25:43 so not OF only... 17:25:57 uri_: I'm going to ask that quetion 17:26:21 committer list -> "The above list is not complete and work in progress as the committers would be from other dependent projects and the discussions are ongoing." 17:26:57 #Info daya_k says that the key goal is to try to minimize the design time interactions required to co-exist and instead push it to run-time 17:28:23 #info mostly focuses on OpenFlow so far, solving 3 different problems (1) the table-0 demuxing problem, (2) partitioning other resources for openfow, (3) try to allow applicattions to interact, e.g., GOTO TABLE for another app and or via MD-SAL in the control plane 17:29:26 vina_ermagan: I'm expecting the lfm graduation review to be short, is that also your expectaiton? 17:29:34 vina_ermagan: just trying to manage time 17:30:09 dfarrell07: good catch, so far we have scope and that 17:30:15 edwarnicke: I'd love to hear your thoughts on the scope 17:30:21 since you're usually the most careful there 17:30:32 colindixon: Looking more closely 17:30:36 colindixon: Our proposal page should be complete, not sure what else the discussion should include 17:30:48 edwarnicke: I think basically if you flop description and scope, it *might* work 17:31:18 #info daya_k talks about the interface manager (talking about network interfaces, not java interfaces) to handle port like things with tunnels, VLANs and the like 17:31:21 colindixon: I think it should be short :) 17:31:25 colindixon: At first scan I would tend to agree 17:32:05 #info colindixon suggests maybe considering a different word than interface manager since that's going to (maybe) cause havoc because of the java keyword interface? 17:33:07 #info edwarnicke asks how this interacts with topology model, daya_k says it doesn't for right now 17:33:53 #info daya_k says that it uses the ietf-interfaces YANG data model, edwarnicke note that he has concerns about this because it's really meant for device control 17:34:00 #Info Prem_ and daya_k say they'll look into this 17:34:40 #Info colindixon says that he thinks moving the augmentations from ietf-interfaces to the topology model will be pretty easy 17:35:48 #info vina_ermagan asks if this is going to be speciifcally for OpenFlow devices or more generic? 17:36:07 #Info daya_k sasy for now it's built on OpenFlow, but the plan is to make it so that it can have more southbounds for this 17:36:51 colindixon: you might want to undo last & correct spelling 17:37:02 of daya_k “says" 17:37:15 :p 17:37:16 #Undo 17:37:16 Removing item from minutes: 17:37:16 #Info daya_k says for now it's built on OpenFlow, but the plan is to make it so that it can have more southbounds for this 17:37:17 ooops 17:38:22 #Info daya_k aslso talks about partitionion (at least virtual) OpenFlow swtiches tables into pipelines with applications having their own pipelines 17:40:09 #info shared overlay tunnel service will try to avoid each project maintaining it's own tunnels 17:40:39 #info shared aliveness monitoring to test health of tunnels 17:41:05 #info ID manager to get unique IDs in ODL, why not use UUIDs? 17:43:34 #Info colindixon note that the scope and description will be flopped (buleleted list is the scope) 17:44:20 #info daya_k and other say the committer list and resources and commited resoureces are complete 17:46:54 #startvote shall the TSC approve the genius project as an incubation project assuming that they make the above changes? -1, 0, +1 17:46:54 Begin voting on: shall the TSC approve the genius project as an incubation project assuming that they make the above changes? Valid vote options are -1, 0, +1. 17:46:54 Vote using '#vote OPTION'. Only your last vote counts. 17:47:21 #vote +1 17:47:23 #vote +1 17:47:24 #vote +1 17:47:26 #info +1 17:47:26 #vote +1 17:47:28 #vote +1 17:47:33 #vote +1 17:47:34 #vote +1 17:47:36 #vote +1 17:47:55 edwarnicke: was there a TSC sub I wasn't ware of? 17:48:02 #vote +1 17:48:05 #endvote 17:48:05 Voted on "shall the TSC approve the genius project as an incubation project assuming that they make the above changes?" Results are 17:48:05 +1 (9): eshuvka_, gkaempfer, ChrisPriceAB, LuisGomez, edwarnicke, dfarrell07, uri_, colindixon, mohnish_ 17:48:07 #info rovarga proxy for jmedved 17:48:18 rovarga_tmp: hey 17:48:37 #info colindixon doesn't know if eshuvka_ is a TSC member or delegate, so he things that's 8 +1s 17:48:47 colindixon: sorry for being late, the CET/US shift is killing me (and my new desktop is killing my usual nick) 17:49:02 #info phrobb says that he notes that daya_k and Prem_ aren not committers, daya_k says yes 17:49:39 #info mohnish_ asks if being offset 1 is right, colindixon says (a) he thinks it is and (b) it's not permanent in either event 17:49:40 eshuvka_: is Shuva, strong support from him :). But - it was a mistake :) 17:49:56 #info vishnoianil asks if Yi is invovled, he is 17:50:21 congrats Genius :) 17:50:34 #agree Genius is now an incubation project 17:50:38 congrats 17:50:40 #topic NATApp creation review 17:50:44 #Link https://wiki.opendaylight.org/view/Project_Proposals:NATApp_Plugin 17:50:57 #link https://lists.opendaylight.org/pipermail/project-proposals/2016-February/000402.html proposed on 2/23/2016 17:51:15 #info oops no i am not 17:51:28 edwarnicke: how do you feel about the scope's use of "mostly" 17:51:29 daya_k, Prem_ congratulations to Genius 17:51:35 edwarnicke: I'd tend to think its fine 17:51:50 congrats daya_k,Prem_ 17:52:03 congrats all 17:52:17 I think it's mostly fine colindixon; edwarnicke ;) 17:52:36 #Info colindixon worries a bit about the use of the word "mostly" in the scope 17:52:41 Thanks vishnoianil ehuvka_ 17:52:46 Thanks all! 17:52:51 colindixon: It falls into the category of things about which I have an opinion, but not one that rises to the level of a complaint ;) 17:53:36 #startvote shall the TSC allow the genius project to join Boron at offest 1 even though it's technically too late? -1, 0, +1 17:53:36 Begin voting on: shall the TSC allow the genius project to join Boron at offest 1 even though it's technically too late? Valid vote options are -1, 0, +1. 17:53:36 Vote using '#vote OPTION'. Only your last vote counts. 17:53:38 #vote +1 17:53:43 forgot this 17:53:43 #vote +1 17:54:13 #vote +1 17:54:13 #vote +1 17:54:16 #vote +1 17:54:16 #vote +1 17:54:17 #vote +1 17:54:27 #vote +1 17:54:40 #endvote 17:54:40 Voted on "shall the TSC allow the genius project to join Boron at offest 1 even though it's technically too late?" Results are 17:54:40 +1 (8): gkaempfer, rovarga_tmp, ChrisPriceAB, LuisGomez, dfarrell07, edwarnicke, colindixon, mohnish_ 17:54:46 That is why I was asking about offet 1 17:54:55 mohnish_: thanks! I missed that 17:54:57 sorry 17:55:14 #agree the NATApp project will be allowed to join boron at offset 1 17:55:48 colin: did you mean Genius? not NATapp 17:56:05 colindixon: I think you meant Genius not NATapp 17:56:10 #Undo 17:56:10 Removing item from minutes: 17:56:15 #agree the Genius project will be allowed to join boron at offset 1 17:56:21 #Info edwarnicke points out that having a complex external dependency (like MySQL) tend to get adoped less, having it also work with easier to deploy things, e.g., sqlite might help 17:56:26 #info they say they'll look at it 17:56:58 #info further points out that sqllite itself has been problematic in the past... would counsel something like derby etc that work well portably ;) 17:57:13 #Info rovarga_tmp asks if they plan to support things other than openflow pluging, the answer is not for right now, but they might do other things 17:57:40 #Info vivek says there are plans to add NAT to the VPN service in boron as well 17:59:09 #info abhijitkumbhare says that they should be aware that they will use the lithium plugin, they will be 17:59:37 #info rovarga_tmp asks if the REST APIS will be RESTCONF, they say yes 18:00:24 #info gkaempfer encourages them to use external databases that are consitent with clustering 18:00:40 #info colindixon says they might look at TSDR, Centinel or persitence for ideas 18:00:41 #startvote shall the TSC approve the NATApp project as an incubation project? -1,0,+1 18:00:41 Begin voting on: shall the TSC approve the NATApp project as an incubation project? Valid vote options are -1, 0, +1. 18:00:41 Vote using '#vote OPTION'. Only your last vote counts. 18:01:08 #vote +1 18:01:18 #vote +1 18:01:21 #vote +1 18:01:31 #vote +1 18:01:34 #vote +1 18:01:55 #vote +1 18:01:56 #vote +1 18:01:57 #vote +1 18:01:58 #vote +1 18:02:00 #endvote 18:02:00 Voted on "shall the TSC approve the NATApp project as an incubation project?" Results are 18:02:00 +1 (9): dfarrell07, gkaempfer, rovarga_tmp, LuisGomez, edwarnicke, ChrisPriceAB, uri_, colindixon, mohnish_ 18:02:17 will need to go in 10... 18:02:21 sharp 18:02:23 #agree NATApp plugin is now an incubation project 18:02:31 https://wiki.opendaylight.org/view/OpenDaylight_Lisp_Flow_Mapping:Graduation_Proposal 18:02:38 #link https://wiki.opendaylight.org/view/OpenDaylight_Lisp_Flow_Mapping:Graduation_Proposal 18:02:47 #topic LISP Flow mapping graduation review 18:02:51 #link https://wiki.opendaylight.org/view/OpenDaylight_Lisp_Flow_Mapping:Graduation_Proposal 18:03:11 #link https://lists.opendaylight.org/pipermail/tsc/2016-March/004858.html asekd for it on 3/10/2016 18:03:21 #Info been in ODL since Hydrogen 18:03:30 #info colindixon notes that they've had some of the best docs of anyone 18:03:45 #startvote shall the TSC allow the NATApp plugin to join Boron? -1,0,+1 18:03:45 Begin voting on: shall the TSC allow the NATApp plugin to join Boron? Valid vote options are -1, 0, +1. 18:03:45 Vote using '#vote OPTION'. Only your last vote counts. 18:03:49 #vote +1 18:03:51 #vote +1 18:03:51 #vote +1 18:03:53 #vote +1 18:03:56 #vote +1 18:04:05 #vote +1 (assuming offset-2) 18:04:05 rovarga_tmp: +1 (assuming offset-2) is not a valid option. Valid options are -1, 0, +1. 18:04:11 #vote +1 18:04:16 #endvote 18:04:16 Voted on "shall the TSC allow the NATApp plugin to join Boron?" Results are 18:04:16 +1 (6): gkaempfer, rovarga_tmp, ChrisPriceAB, dfarrell07, edwarnicke, colindixon 18:04:27 #agree NATApp project can join boron 18:04:43 #startvote shall the TSC graduate the LISP flow mapping project to mature? -1,0,+1 18:04:43 Begin voting on: shall the TSC graduate the LISP flow mapping project to mature? Valid vote options are -1, 0, +1. 18:04:43 Vote using '#vote OPTION'. Only your last vote counts. 18:04:47 #vote +1 18:04:49 #vote +1 18:04:51 #vote +1 18:04:55 #vote +1 18:05:02 #vote +1 18:05:04 LuisGomez, uri_ 18:05:04 #vote +1 18:05:06 #vote +1 18:05:10 #endvote 18:05:10 Voted on "shall the TSC graduate the LISP flow mapping project to mature?" Results are 18:05:10 +1 (7): gkaempfer, rovarga_tmp, LuisGomez, dfarrell07, ChrisPriceAB, edwarnicke, colindixon 18:05:28 #agree LISP Flow Mapping is now a mature project 18:05:40 * ChrisPriceAB congratulates the LFM team! 18:05:44 #topic cookies 18:06:03 #endmeeting