18:00:44 <colindixon> #startmeeting tsc 18:00:44 <odl_meetbot> Meeting started Thu Nov 10 18:00:44 2016 UTC. The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html. 18:00:44 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:44 <odl_meetbot> The meeting name has been set to 'tsc' 18:00:50 <colindixon> #topic agenda bashing and roll call 18:00:52 <colindixon> #info colindixon 18:00:57 <colindixon> TSC members please #info in 18:01:03 <dfarrell07> #info Daniel Farrell 18:01:18 <ChrisPriceAB> #info Chris Price 18:01:22 <abhijitkumbhare> #info abhijitkumbhare 18:01:40 <colindixon> #link https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=51746#Agenda the agenda (note that we already did the BIER creation review earlier) 18:01:56 <adetalhouet> #info adetalhouet 18:02:05 <ChrisPriceAB> if you're happy ad you know it #info in 18:02:12 <michal-cmarada> #info Michal Cmarada for GBP 18:02:13 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-11-03-17.00.html last week's meeting minutes 18:02:45 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-11-10-15.29.html this morning's meeting with the review of BIER 18:03:00 <colindixon> #undo 18:03:00 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x2949410> 18:03:02 <colindixon> #Undo 18:03:02 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x2a9c390> 18:03:03 <colindixon> #undo 18:03:03 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x2949c50> 18:03:06 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-11-10-15.29.html this morning's meeting with the review of BIER 18:03:09 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-11-03-17.00.html last week's meeting minutes 18:03:13 <rovarga> #info rovarga for jmedved 18:03:16 <colindixon> michal-cmarada: normally only TSC members #info in 18:03:20 <colindixon> to track attendance for quorum 18:03:21 <edwarnicke> #info edwarnicke 18:03:28 <michal-cmarada> sorry 18:03:41 <colindixon> michal-cmarada: all good 18:03:49 <colindixon> #action colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way 18:03:58 <colindixon> #action colindixon and zxiiro to work on trying to build tools to help with what's failing on failures in our jenkins jobs 18:04:04 <gkaempfer> #info gkaempfer 18:04:08 <colindixon> #action dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion 18:04:10 <colindixon> thanks gkaempfer 18:04:12 <colindixon> and sorry 18:04:24 <colindixon> #action phrobb to work on getting us better control of the events and downloads page to make his life less painful 18:04:29 <colindixon> #action phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better 18:04:44 <vishnoianil> #info Anil Vishnoi 18:05:06 <colindixon> #action colindixon to send a mail about projects with no active committers and how to manage them 18:05:13 <anipbu> https://docs.google.com/spreadsheets/d/1MufwajG-YwGU7dth97x07VVRznVx4UgPHkfRFk6-bQg/edit#gid=1265433317 18:05:22 <colindixon> #link we are all done with sfc with sfc version bump patches https://docs.google.com/spreadsheets/d/1MufwajG-YwGU7dth97x07VVRznVx4UgPHkfRFk6-bQg/edit#gid=1265433317 18:05:48 <colindixon> #topic TSC mailing list votes and discussions 18:05:58 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2016-November/006271.html vote on ALTO new committers 18:06:41 <colindixon> #link https://lists.opendaylight.org/pipermail/discuss/2016-November/006925.html TSC elections are ongoing, if you are a comitter or PTL you should have one e-mail + one e-mail per project on which you are PTL, if you don't please let us know, if you do pleaes vote 18:06:50 <colindixon> #undo 18:06:50 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x2aaf790> 18:07:14 <colindixon> #link https://lists.opendaylight.org/pipermail/discuss/2016-November/006925.html TSC elections are ongoing, if you are a committer or PTL you should have one e-mail + one e-mail per project on which you are PTL, if you don't please let us know, if you do please vote 18:07:26 <colindixon> #topic events 18:07:37 <colindixon> #link https://www.opendaylight.org/global-events 18:08:00 <colindixon> #info there is a MEF event going on as we speak in Baltimore, it's all over my twitter feed from @OpenDaylightSDN 18:08:30 <colindixon> #info the OpenDaylight Forum India is the end of next week 11/16-11/17 18:08:41 <dfarrell07> #link http://events.linuxfoundation.org/events/opnfv-plugfest OPNFV Plugfest in December 18:08:57 <colindixon> #topic boron 18:09:16 <anipbu> #link https://lists.opendaylight.org/pipermail/release/2016-November/008707.html <--- TOPOPROCESSING Boron Autorelease Build Failure. 18:09:23 <anipbu> #link https://git.opendaylight.org/gerrit/#/c/47980/ <--- Maybe related to patch 47980 but still currently being investigated. 18:09:41 <colindixon> #topic carbon 18:09:49 <anipbu> #link https://lists.opendaylight.org/pipermail/release/2016-November/008729.html <--- HONEYCOMB/VBD Carbon Autorelease Build Failure 18:10:22 <anipbu> #info As a part of Adding blueprint wiring for netconf-client, we remove netconf-config-dispatcher as moved to netconf-client. Impacts Yangpush. 18:10:35 <anipbu> #link https://git.opendaylight.org/gerrit/#/c/46623/ <--- We need YANGPUSH to merge patch to facilitate patch 47856. Otherwise builds will start failing in two weeks 18:12:04 <anipbu> https://docs.google.com/spreadsheets/d/1MufwajG-YwGU7dth97x07VVRznVx4UgPHkfRFk6-bQg/edit#gid=1265433317 18:13:11 <anipbu> #link https://wiki.opendaylight.org/view/Weather#target-ide.2F_instead_of_target.2F_as_output_folder_under_M2E_in_Eclipse <--- We will use target-ide/ instead of target/ as output folder under M2E in Eclipse. 18:13:28 <anipbu> #link https://lists.opendaylight.org/pipermail/release/2016-November/008701.html <--- No impact to any projects functionality. Only Impacts developers using eclipse. 18:13:46 <anipbu> #link https://wiki.opendaylight.org/view/Weather#Change_of_topology_id_in_openflow-plugin <--- There are plans to Change topology_id from "flow:1" to "openflow" 18:14:00 <anipbu> #link https://lists.opendaylight.org/pipermail/release/2016-November/008725.html <--- Some discussion on using a configurable knob in openflowplugin an select box in dlux so as not to impact all openflowplugin dependent projects. 18:15:06 <colindixon> #topic system integration and testing 18:15:30 <colindixon> #info some projects have been hit by a build image that was missing, that seems to be identified and working on a fix, affecting genius and lacp 18:15:41 <colindixon> #topic infrastructure 18:16:45 <colindixon> #link https://lists.opendaylight.org/pipermail/release/2016-November/008710.html long outage expected on 11/26 (the Saturday after Thanksgiving) 18:17:05 <colindixon> #link https://lists.opendaylight.org/pipermail/release/2016-November/008724.html reports of issues with Nexus again 18:18:17 <zxiiro> anipbu: this should be the fix for vbd https://git.opendaylight.org/gerrit/48231 18:18:30 <colindixon> #info tykeal has a ticket open with Rackspace, we are looking into it, but it's also possible that this is the issue with our current F5 device and we have pricing information around that 18:18:39 <anipbu> zxiiro: Thank you. 18:20:24 <colindixon> #info colindixon says that according to who he's talked to it's only been the last few days, tykeal says that he's not sure, which is why we have a ticket open with rackspace 18:21:09 <colindixon> #info tykeal says that the F5 device shouldn't be causing issues with internal jobs except CSIT 18:22:04 <colindixon> #topic Cluster Metrics creation review 18:22:30 <colindixon> #link https://wiki.opendaylight.org/view/Project_Proposals:Cluster_Metrics 18:22:41 <colindixon> #link https://lists.opendaylight.org/pipermail/project-proposals/2016-October/000555.html proposed on 10/18/2016 18:25:06 <colindixon> #info basically this gathers key metics from the various machines/controller instances, e.g., cpu, memory, raft state, etc. and then renders them in the DLUX UI 18:25:15 <colindixon> #Info dmalachovsky_ gives a demo showing it working in real time 18:25:53 <colindixon> #info it has dashboard widgets, set up tabs, and assign widgets to tabs, also history charts 18:28:03 <colindixon> dmalachovsky_: I have one question and one comment: does this need to be it's own project or should it be new code in controller, and new code in DluxApps? Also, this will need to go through income code IPR. 18:28:43 <colindixon> #info LuisGomez asks what the backend? is it Java application? Yes, it is. 18:31:09 <colindixon> #action dmalachovsky_ to send the tarball of the code to phrobb for IPR 18:31:50 <colindixon> #info colindixon asks if we can contribute the stats code to the controller project to go alongside clustering, and then the UI part goes into DluxApps 18:32:59 <ChrisPriceAB> please don't let Ed name your project!!! 18:33:13 <colindixon> #info jan medved says that this collects a lot more than just clustering metrics, so bundling it with clustering code doesn't make tons of sense 18:33:31 <colindixon> #info edwarnicke suggests clustermetrics might be wrong then, maybe it would be better systemmetrics is suggested 18:34:52 * adetalhouet agrees with that statement 18:35:06 <colindixon> #info dfarrell07 asks if this data would be available for integration to use in tests and things, answer is yes that you can use the stats reflector (backend) on it's own and then just use the RPCs 18:35:35 <colindixon> #info LuisGomez asks if there's going to be performance implications of collecting all this data, answer is that they shouldn't be, but it hasn't been testing 18:35:38 <colindixon> #undo 18:35:38 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x295cbd0> 18:35:42 <colindixon> #info LuisGomez asks if there's going to be performance implications of collecting all this data, answer is that they shouldn't be, but it hasn't been tested 18:36:29 <colindixon> #info LuisGomez asks if it's configurable how often to poll stats or what status to poll, answer is not this second, but it should be and would be easy to add 18:36:34 * ebrjohn_ gkaempfer is already thinking about using it in federation :) 18:36:47 * ebrjohn_ this is very cool stuff 18:36:52 <colindixon> #info gkaempfer asks if it can be used to monitor multiple clusters, answer is not this second, but it could be extended 18:37:32 <colindixon> #startvote shall the TSC approve the project proposal as it's renamed to system metrics? -1,0,+1 18:37:32 <odl_meetbot> Begin voting on: shall the TSC approve the project proposal as it's renamed to system metrics? Valid vote options are -1, 0, +1. 18:37:32 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts. 18:37:33 <abhijitkumbhare> yes - cool stuff 18:37:35 <gkaempfer> #vote +1 18:37:38 <adetalhouet> #vote +! 18:37:38 <odl_meetbot> adetalhouet: +! is not a valid option. Valid options are -1, 0, +1. 18:37:38 <colindixon> #vote 0 18:37:39 <abhijitkumbhare> #vote +1 18:37:39 <edwarnicke> #vote +1 18:37:40 <vishnoianil> #vote +1 18:37:42 <adetalhouet> #vote +1 18:37:43 <dfarrell07> #vote +1 18:37:49 <ChrisPriceAB> #vote +1 18:37:49 <rovarga> #vote +1 18:37:53 <colindixon> #endvote 18:37:53 <odl_meetbot> Voted on "shall the TSC approve the project proposal as it's renamed to system metrics?" Results are 18:37:53 <odl_meetbot> 0 (1): colindixon 18:37:53 <odl_meetbot> +1 (8): gkaempfer, adetalhouet, ChrisPriceAB, dfarrell07, edwarnicke, rovarga, abhijitkumbhare, vishnoianil 18:37:57 <rovarga> (jan has not pounded in) 18:38:10 <colindixon> #agreed the system metrics project is now an incubation 18:38:32 <colindixon> #startvote shall the TSC allow the system metrics project to join the carbon release as an offset 2 project? -1,0,+1 18:38:32 <odl_meetbot> Begin voting on: shall the TSC allow the system metrics project to join the carbon release as an offset 2 project? Valid vote options are -1, 0, +1. 18:38:32 <odl_meetbot> Vote using '#vote OPTION'. Only your last vote counts. 18:38:34 <colindixon> #vote +1 18:38:43 <vishnoianil> #vote +1 18:38:46 <dfarrell07> #vote +1 18:38:48 <rovarga> #vote +1 18:38:49 <abhijitkumbhare> #vote +1 18:38:49 <ChrisPriceAB> #vote +1 18:38:51 <gkaempfer> #vote +1 18:39:11 <colindixon> #endvote 18:39:11 <odl_meetbot> Voted on "shall the TSC allow the system metrics project to join the carbon release as an offset 2 project?" Results are 18:39:11 <odl_meetbot> +1 (7): gkaempfer, rovarga, ChrisPriceAB, dfarrell07, colindixon, abhijitkumbhare, vishnoianil 18:39:14 <adetalhouet> #vote +1 18:39:21 <abhijitkumbhare> adetalhouet liked the proposal so much that he voted with a “+!” - we should have that option in the vote 18:39:28 <colindixon> #agreed the system metrics project can join carbon at offset 2 18:39:36 <abhijitkumbhare> the prev vote I mean 18:39:41 <adetalhouet> abhijitkumbhare is reading my mind :) 18:39:49 <abhijitkumbhare> :) 18:39:56 <colindixon> #topic possibly sharing resources with other LF projects 18:40:55 <colindixon> dmalachovsky_ and others, fwiw, I just feel like this would be best done as new code in the controller and dluxapps projects rather than yet another project especially as we see so many projects that "do one thing and do it well" end up being hard to keep maintained over time 18:41:40 <colindixon> #info ChrisPriceAB says that there have been lots of discussions around ways we could maybe share resources between very closely-related related projects, e.g., ODL, OPNFV, and FD.io 18:41:51 <abhijitkumbhare> good point colindixon 18:42:04 <adetalhouet> I echo colindixon thoughts, but either it will converge in a clustering project, if as a fact, it's only about clustering. Else if the argument that it is really gathering system metrics, then it's fine having it living on its side 18:43:17 <colindixon> #info it's also the case that roughly speaking the same people are having to create multiple accounts—one for each project—and then we have silos where we have different sysadmins using slightly different tools and not sharing expertise and time 18:43:28 <abhijitkumbhare> if cigars - we would all join :) 18:43:51 * ebrjohn_ did he say cigars?!?!? 18:43:56 <colindixon> #info ChrisPriceAB note that the boards of Open-O, OPNFV, FD.io and OpenDaylight boards have all started some investigation around this 18:44:13 <colindixon> #info there are representatives from each project, so far for OpenDaylight that is LuisGomez and dfarrell07 18:44:40 <colindixon> #info but it's all intended to be very open and more of dialog of what we could do better than any forcing of anything 18:45:14 <colindixon> #info examples of what we could do better: get better around the globe support, get more reliable infrastructure as we have more of it 18:45:50 * rovarga hopes that issue tracking will be shared... :) 18:46:37 <colindixon> #info rovarga points out that this might also make issue tracking across these different projects easier 18:46:57 <ebrjohn_> edwarnicke: good idea, you're it! 18:47:05 <ChrisPriceAB> rovarga it is one of the issue-friuts people are pointing at saying how low it seems to be hanging. 18:47:09 <colindixon> #info edwarnicke suggests that having rotating members of each TSC attend the various other TSCs to do information exchanges and get to know each other a little better 18:47:49 <colindixon> #info ChrisPriceAB says that whatever happens will be brought back and shared with relevant communities and TSC calls 18:48:19 <colindixon> #info dfarrell07 says that things are just getting started, but there is every intent to have open places to contribute ideas 18:51:06 * ebrjohn_ yes!! 18:51:10 <colindixon> #action colindixon and/or ChrisPriceAB to work on how to manage cross-release issues with ODL/OPNFV 18:52:12 <colindixon> #topic cookies 18:52:13 * ChrisPriceAB wants his cookies 18:52:14 <colindixon> #endmeeting