#opendaylight-meeting: tsc

Meeting started by colindixon at 18:00:44 UTC (full logs).

Meeting summary

  1. agenda bashing and roll call (colindixon, 18:00:50)
    1. colindixon (colindixon, 18:00:52)
    2. Daniel Farrell (dfarrell07, 18:01:03)
    3. Chris Price (ChrisPriceAB, 18:01:18)
    4. abhijitkumbhare (abhijitkumbhare, 18:01:22)
    5. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=51746#Agenda the agenda (note that we already did the BIER creation review earlier) (colindixon, 18:01:40)
    6. adetalhouet (adetalhouet, 18:01:56)
    7. 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 (colindixon, 18:03:06)
    8. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-11-03-17.00.html last week's meeting minutes (colindixon, 18:03:09)
    9. rovarga for jmedved (rovarga, 18:03:13)
    10. edwarnicke (edwarnicke, 18:03:21)
    11. ACTION: colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way (colindixon, 18:03:49)
    12. ACTION: colindixon and zxiiro to work on trying to build tools to help with what's failing on failures in our jenkins jobs (colindixon, 18:03:58)
    13. gkaempfer (gkaempfer, 18:04:04)
    14. ACTION: dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion (colindixon, 18:04:08)
    15. ACTION: phrobb to work on getting us better control of the events and downloads page to make his life less painful (colindixon, 18:04:24)
    16. ACTION: phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better (colindixon, 18:04:29)
    17. Anil Vishnoi (vishnoianil, 18:04:44)
    18. ACTION: colindixon to send a mail about projects with no active committers and how to manage them (colindixon, 18:05:06)
    19. https://docs.google.com/spreadsheets/d/1MufwajG-YwGU7dth97x07VVRznVx4UgPHkfRFk6-bQg/edit#gid=1265433317 (anipbu, 18:05:13)
    20. we are all done with sfc with sfc version bump patches https://docs.google.com/spreadsheets/d/1MufwajG-YwGU7dth97x07VVRznVx4UgPHkfRFk6-bQg/edit#gid=1265433317 (colindixon, 18:05:22)

  2. TSC mailing list votes and discussions (colindixon, 18:05:48)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-November/006271.html vote on ALTO new committers (colindixon, 18:05:58)
    2. 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 (colindixon, 18:07:14)

  3. events (colindixon, 18:07:26)
    1. https://www.opendaylight.org/global-events (colindixon, 18:07:37)
    2. there is a MEF event going on as we speak in Baltimore, it's all over my twitter feed from @OpenDaylightSDN (colindixon, 18:08:00)
    3. the OpenDaylight Forum India is the end of next week 11/16-11/17 (colindixon, 18:08:30)
    4. http://events.linuxfoundation.org/events/opnfv-plugfest OPNFV Plugfest in December (dfarrell07, 18:08:41)

  4. boron (colindixon, 18:08:57)
    1. https://lists.opendaylight.org/pipermail/release/2016-November/008707.html <--- TOPOPROCESSING Boron Autorelease Build Failure. (anipbu, 18:09:16)
    2. https://git.opendaylight.org/gerrit/#/c/47980/ <--- Maybe related to patch 47980 but still currently being investigated. (anipbu, 18:09:23)

  5. carbon (colindixon, 18:09:41)
    1. https://lists.opendaylight.org/pipermail/release/2016-November/008729.html <--- HONEYCOMB/VBD Carbon Autorelease Build Failure (anipbu, 18:09:49)
    2. As a part of Adding blueprint wiring for netconf-client, we remove netconf-config-dispatcher as moved to netconf-client. Impacts Yangpush. (anipbu, 18:10:22)
    3. 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 (anipbu, 18:10:35)
    4. https://docs.google.com/spreadsheets/d/1MufwajG-YwGU7dth97x07VVRznVx4UgPHkfRFk6-bQg/edit#gid=1265433317 (anipbu, 18:12:04)
    5. 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. (anipbu, 18:13:11)
    6. https://lists.opendaylight.org/pipermail/release/2016-November/008701.html <--- No impact to any projects functionality. Only Impacts developers using eclipse. (anipbu, 18:13:28)
    7. 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" (anipbu, 18:13:46)
    8. 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. (anipbu, 18:14:00)

  6. system integration and testing (colindixon, 18:15:06)
    1. 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 (colindixon, 18:15:30)

  7. infrastructure (colindixon, 18:15:41)
    1. https://lists.opendaylight.org/pipermail/release/2016-November/008710.html long outage expected on 11/26 (the Saturday after Thanksgiving) (colindixon, 18:16:45)
    2. https://lists.opendaylight.org/pipermail/release/2016-November/008724.html reports of issues with Nexus again (colindixon, 18:17:05)
    3. 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 (colindixon, 18:18:30)
    4. 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 (colindixon, 18:20:24)
    5. tykeal says that the F5 device shouldn't be causing issues with internal jobs except CSIT (colindixon, 18:21:09)

  8. Cluster Metrics creation review (colindixon, 18:22:04)
    1. https://wiki.opendaylight.org/view/Project_Proposals:Cluster_Metrics (colindixon, 18:22:30)
    2. https://lists.opendaylight.org/pipermail/project-proposals/2016-October/000555.html proposed on 10/18/2016 (colindixon, 18:22:41)
    3. 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 (colindixon, 18:25:06)
    4. dmalachovsky_ gives a demo showing it working in real time (colindixon, 18:25:15)
    5. it has dashboard widgets, set up tabs, and assign widgets to tabs, also history charts (colindixon, 18:25:53)
    6. LuisGomez asks what the backend? is it Java application? Yes, it is. (colindixon, 18:28:43)
    7. ACTION: dmalachovsky_ to send the tarball of the code to phrobb for IPR (colindixon, 18:31:09)
    8. 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 (colindixon, 18:31:50)
    9. 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 (colindixon, 18:33:13)
    10. edwarnicke suggests clustermetrics might be wrong then, maybe it would be better systemmetrics is suggested (colindixon, 18:33:31)
    11. 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 (colindixon, 18:35:06)
    12. 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 (colindixon, 18:35:42)
    13. 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 (colindixon, 18:36:29)
    14. gkaempfer asks if it can be used to monitor multiple clusters, answer is not this second, but it could be extended (colindixon, 18:36:52)
    15. VOTE: Voted on "shall the TSC approve the project proposal as it's renamed to system metrics?" Results are, 0: 1, +1: 8 (colindixon, 18:37:53)
    16. AGREED: the system metrics project is now an incubation (colindixon, 18:38:10)
    17. VOTE: Voted on "shall the TSC allow the system metrics project to join the carbon release as an offset 2 project?" Results are, +1: 7 (colindixon, 18:39:11)
    18. AGREED: the system metrics project can join carbon at offset 2 (colindixon, 18:39:28)

  9. possibly sharing resources with other LF projects (colindixon, 18:39:56)
    1. 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 (colindixon, 18:41:40)
    2. 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 (colindixon, 18:43:17)
    3. ChrisPriceAB note that the boards of Open-O, OPNFV, FD.io and OpenDaylight boards have all started some investigation around this (colindixon, 18:43:56)
    4. there are representatives from each project, so far for OpenDaylight that is LuisGomez and dfarrell07 (colindixon, 18:44:13)
    5. but it's all intended to be very open and more of dialog of what we could do better than any forcing of anything (colindixon, 18:44:40)
    6. examples of what we could do better: get better around the globe support, get more reliable infrastructure as we have more of it (colindixon, 18:45:14)
    7. rovarga points out that this might also make issue tracking across these different projects easier (colindixon, 18:46:37)
    8. 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 (colindixon, 18:47:09)
    9. ChrisPriceAB says that whatever happens will be brought back and shared with relevant communities and TSC calls (colindixon, 18:47:49)
    10. dfarrell07 says that things are just getting started, but there is every intent to have open places to contribute ideas (colindixon, 18:48:19)
    11. ACTION: colindixon and/or ChrisPriceAB to work on how to manage cross-release issues with ODL/OPNFV (colindixon, 18:51:10)

  10. cookies (colindixon, 18:52:12)


Meeting ended at 18:52:14 UTC (full logs).

Action items

  1. colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way
  2. colindixon and zxiiro to work on trying to build tools to help with what's failing on failures in our jenkins jobs
  3. dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion
  4. phrobb to work on getting us better control of the events and downloads page to make his life less painful
  5. phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better
  6. colindixon to send a mail about projects with no active committers and how to manage them
  7. dmalachovsky_ to send the tarball of the code to phrobb for IPR
  8. colindixon and/or ChrisPriceAB to work on how to manage cross-release issues with ODL/OPNFV


Action items, by person

  1. ChrisPriceAB
    1. colindixon and/or ChrisPriceAB to work on how to manage cross-release issues with ODL/OPNFV
  2. colindixon
    1. colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way
    2. colindixon and zxiiro to work on trying to build tools to help with what's failing on failures in our jenkins jobs
    3. dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion
    4. colindixon to send a mail about projects with no active committers and how to manage them
    5. colindixon and/or ChrisPriceAB to work on how to manage cross-release issues with ODL/OPNFV
  3. dfarrell07
    1. dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion
  4. zxiiro
    1. colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way
    2. colindixon and zxiiro to work on trying to build tools to help with what's failing on failures in our jenkins jobs
  5. UNASSIGNED
    1. phrobb to work on getting us better control of the events and downloads page to make his life less painful
    2. phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better
    3. dmalachovsky_ to send the tarball of the code to phrobb for IPR


People present (lines said)

  1. colindixon (84)
  2. odl_meetbot (18)
  3. anipbu (12)
  4. abhijitkumbhare (9)
  5. adetalhouet (7)
  6. ChrisPriceAB (7)
  7. rovarga (5)
  8. ebrjohn_ (5)
  9. dfarrell07 (4)
  10. gkaempfer (3)
  11. vishnoianil (3)
  12. edwarnicke (2)
  13. michal-cmarada (2)
  14. zxiiro (1)


Generated by MeetBot 0.1.4.