#opendaylight-meeting: tsc

Meeting started by colindixon at 18:04:48 UTC (full logs).

Meeting summary

  1. agenda bashing and roll call (colindixon, 18:04:49)
    1. edwarnicke (edwarnicke, 18:04:52)
    2. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=52461#Agenda (colindixon, 18:04:53)
    3. Vratko Polak proxying for Luis Gomez (vrpolak, 18:04:54)
    4. skitt (skitt, 18:04:54)
    5. Thanh (zxiiro, 18:04:54)
    6. colindixon (colindixon, 18:04:55)
    7. jamoluhrsen (jamoluhrsen, 18:04:56)
    8. anipbu (anipbu, 18:04:57)
    9. Hideyuki (hideyuki, 18:04:57)
    10. abhijitkumbhare (abhijitkumbhare, 18:04:57)
    11. shague (shague, 18:04:58)
    12. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-12-23-04.30.html last week's meeting minutes (colindixon, 18:05:16)
    13. ACTION: phrobb to follow up with LF folks about a TSC mixer at the Leadership Summit (colindixon, 18:05:55)
    14. ACTION: colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way (colindixon, 18:06:08)
    15. 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:06:08)
    16. ACTION: colindixon to try to drive some/all of the ongoing TSC discussions to completion (colindixon, 18:06:10)
    17. ACTION: phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better (colindixon, 18:06:11)
    18. ACTION: colindixon, vishnoianil, gzhao, anipbu and others to work to advertise APAC-friendly TSC calls to the India and China communities, as well as projects/PTLs in Asia (colindixon, 18:06:11)

  2. TSC mailing list votes and discssions (colindixon, 18:06:43)
    1. rovarga (rovarga, 18:06:45)
    2. https://lists.opendaylight.org/pipermail/tsc/2016-November/006368.html projects with few/no active committers (colindixon, 18:06:54)
    3. https://lists.opendaylight.org/pipermail/tsc/2016-November/006298.html Delivering to consumer project off-cadence (ODP & OPNFV collaboration) (colindixon, 18:07:11)
    4. https://lists.opendaylight.org/pipermail/release/2017-January/009034.html flagship features in Carbon (colindixon, 18:07:42)
    5. ACTION: colindixon to try to close the loop with OPNFV on what they need for their next release to figure out what they actually need from us for that (colindixon, 18:09:13)
    6. dfarrell07 notes that there was a poll about what version of OpenStack OPNFV was going to use and so that might be useful input for how ODL/OPNFV interact (colindixon, 18:11:39)
    7. https://lists.opendaylight.org/pipermail/tsc/2016-December/006485.html Carbon hackfest date/location (colindixon, 18:13:34)
    8. unless something else happens, the plan is to have no big, formal mid-cycle hackfest, there is a resonable chance that a member organziation will host one (colindixon, 18:14:09)

  3. events (colindixon, 18:14:28)
    1. https://wiki.opendaylight.org/view/Events:Main <-- link to updated events wiki page where info will be posted ongoing (phrobb, 18:14:32)
    2. https://www.opendaylight.org/global-events (colindixon, 18:14:37)
    3. the wiki page above is the more TSC and ODL-internal useful calendar, with lots of events listed and where it's easy to edit (colindixon, 18:16:35)
    4. open source leadership summit at lake tahoe Feb 14-16 (colindixon, 18:17:06)
    5. possible ODL carbon hackfest being planned (colindixon, 18:17:15)
    6. ONS 2017 CF closes 1/21, please submit, lots of work being done to make this more truly about open networking in general and not all ON.lab all the time (colindixon, 18:17:44)
    7. NFV world congress, OpenStack summit, OPNFV summit, Containercon/Linuxcon/cloudopen, all listed there with more details (colindixon, 18:18:37)

  4. boron (colindixon, 18:19:21)
    1. nothing this week (colindixon, 18:19:26)

  5. carbon (colindixon, 18:19:29)
    1. https://lists.opendaylight.org/pipermail/release/2016-December/009011.html <--- Autorelease issues with VTN has beenn resolved. (anipbu, 18:20:02)
    2. https://lists.opendaylight.org/pipermail/release/2017-January/009023.html <--- Autorelease issues with BIER has beenn resolved. (anipbu, 18:20:08)
    3. https://lists.opendaylight.org/pipermail/release/2017-January/009032.html <--- Autorelease Build Job currently failing on OF-CONFIG. Currently waiting on folks from ZTE to identify a fix. (anipbu, 18:20:14)
    4. https://lists.opendaylight.org/pipermail/release/2016-December/008994.html <--- Still waiting on M3 Status from 4 Projects: aaa, controller, mdsal, netconf (anipbu, 18:20:31)
    5. https://lists.opendaylight.org/pipermail/release/2017-January/009022.html <--- Periodic Jobs Removed (anipbu, 18:20:50)
    6. https://lists.opendaylight.org/pipermail/tsc/2017-January/006498.html <--- Long Job Queues (anipbu, 18:20:55)
    7. Mostly impact netvirt. Waiting to see if other projects have been affected and if any impact on release. (anipbu, 18:21:09)
    8. https://lists.opendaylight.org/pipermail/release/2017-January/009024.html <--- Karaf 4 Migration Effort. (anipbu, 18:21:21)
    9. Karaf 4 migration effort will be a critical endeaver in Carbon. Need to identify if Karaf 4 is a REQUIREMENT to remain in the Carbon Simultaneous Release Plan. (anipbu, 18:22:00)
    10. If Karaf 4 is a requirement, we need to identify the timeline (M4/M5/RC0?), support documentation (step-by-step wiki page), and TWS recording (anipbu, 18:22:21)
    11. Two Migration: migration to singlefeaturetest, migration to karaf 4 (anipbu, 18:22:32)
    12. We need to poll projects on available resources. If no resources available, what are the options? 2 distributions, drop from release, communnity generates patches? (anipbu, 18:22:39)
    13. colindixon says that we really have to get away from Karaf 3 and onto Karaf 4 for, at the very least, security reasons (colindixon, 18:25:29)
    14. this would also get us on the current Karaf timeline, which means we get features faster from them (colindixon, 18:26:42)
    15. VOTE: Voted on "shall the TSC move that we will produce _only_ a Karaf 4 distribution for Carbon and deal with how to get us across that line?" Results are, +1: 10 (colindixon, 18:32:50)
    16. AGREED: the Carbon release of OpenDaylight will ship with Karaf 4 only, mostly for security reasons, the TSC takes ownership for getting us across that line (colindixon, 18:33:18)
    17. ACTION: skitt and others to create a step-by-step guide and minimum required steps on th wiki (colindixon, 18:34:42)
    18. https://git.opendaylight.org/gerrit/49550 <-- yangtools patch (skitt, 18:35:11)
    19. vishnoianil asks if it has to be done all at once (colindixon, 18:36:39)
    20. as skitt explained in the e-mail, the only requirment is that we move in dependency order and nobody should have to be broken ever, we have a wave of karaf3+4 patches cascade through and then remove karaf3 as a wave going backward if we want (colindixon, 18:37:50)
    21. skitt notes that Karaf 4.0.9, which is the starting point is supposed to be released this weekend (colindixon, 18:39:49)
    22. skitt notes that if 4.0.9 doesn't ship this weekend, we'll start working against our own pre-release version of Karaf 4.0.9 (colindixon, 18:40:40)

  6. Nitrogen DDF timing (colindixon, 18:42:14)
    1. our current release plan has 5/11 as a target, and there are other events coming around that time with OpenStack and memorial day (colindixon, 18:43:36)
    2. phrobb earlier in the week of the 22nd (which is tight against our current release epsecially given that we current release during the OpenStack summit) and around May 31st/June 1st would be OK as well, but then it comes up against the OPNFV summit pretty quickly (colindixon, 18:44:53)
    3. ACTION: phrobb to send mail about Nitrogen DDF timing (colindixon, 18:45:22)

  7. jenkins queue issues (colindixon, 18:45:47)
    1. https://lists.opendaylight.org/pipermail/tsc/2017-January/006498.html shague bring up current issues (colindixon, 18:46:39)
    2. zxiiro is looking at using OpenStack Heat instead of JClouds, which might help (colindixon, 18:47:03)
    3. tykeal notes that it's really just CSIT jobs that are the problem, so projects that gate on CSIT jobs are being hit hard (colindixon, 18:47:52)
    4. a lot of discussion about CSIT jobs and how we might help to fix this (colindixon, 18:54:42)

  8. Container Orchestration Proposal (colindixon, 18:55:40)
    1. https://wiki.opendaylight.org/view/Project_Proposals:COE_integration (colindixon, 18:55:52)
    2. https://lists.opendaylight.org/pipermail/project-proposals/2016-December/000563.html proposed on 12/15 (colindixon, 18:56:01)
    3. Prem_ presents the project for providing interfaces for OpenDaylight to be able to provide networking features for container orchestration systems, e.g., Kubernetes (colindixon, 18:59:42)
    4. the approach is to integrate with Kubernetes CNI directly and also via Kuryr (colindixon, 19:01:49)
    5. developers from ericsson, redhat, intel, cienna, HPE and inocybe committed (colindixon, 19:02:57)
    6. Prem_ notes that the intent is to map everythning onto existing networking virtualization components, not create new ones, it will use existing Neutron implementations as the base (colindixon, 19:05:35)
    7. colindixon asks if the project really needs 15 committers? Prem_ says he'll update that with something more reasable (colindixon, 19:05:58)
    8. vishnoianil asks if it it will be in Carbon? Prem_ says they would like to be, but that's up to the TSC (colindixon, 19:06:53)
    9. Prem_ adds that the simple integration with Kuryr is probably pretty easy to get done in Carbon (colindixon, 19:07:41)
    10. colindixon and edwarnicke ask Prem_ if this is the right committer list? (colindixon, 19:10:18)
    11. Prem_ notes that the large committer list is mostly because this is moving a lot of different parts and integrating them (colindixon, 19:12:02)
    12. VOTE: Voted on "shall the TSC approve the COE project as an incubation project?" Results are, 0: 2, +1: 10 (colindixon, 19:13:19)
    13. AGREED: CoE is an incubtion project (colindixon, 19:13:30)

  9. cookies (colindixon, 19:13:33)


Meeting ended at 19:13:35 UTC (full logs).

Action items

  1. phrobb to follow up with LF folks about a TSC mixer at the Leadership Summit
  2. colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way
  3. colindixon and zxiiro to work on trying to build tools to help with what's failing on failures in our jenkins jobs
  4. colindixon to try to drive some/all of the ongoing TSC discussions to completion
  5. phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better
  6. colindixon, vishnoianil, gzhao, anipbu and others to work to advertise APAC-friendly TSC calls to the India and China communities, as well as projects/PTLs in Asia
  7. colindixon to try to close the loop with OPNFV on what they need for their next release to figure out what they actually need from us for that
  8. skitt and others to create a step-by-step guide and minimum required steps on th wiki
  9. phrobb to send mail about Nitrogen DDF timing


Action items, by person

  1. anipbu
    1. colindixon, vishnoianil, gzhao, anipbu and others to work to advertise APAC-friendly TSC calls to the India and China communities, as well as projects/PTLs in Asia
  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. colindixon to try to drive some/all of the ongoing TSC discussions to completion
    4. colindixon, vishnoianil, gzhao, anipbu and others to work to advertise APAC-friendly TSC calls to the India and China communities, as well as projects/PTLs in Asia
    5. colindixon to try to close the loop with OPNFV on what they need for their next release to figure out what they actually need from us for that
  3. phrobb
    1. phrobb to follow up with LF folks about a TSC mixer at the Leadership Summit
    2. colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way
    3. phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better
    4. phrobb to send mail about Nitrogen DDF timing
  4. skitt
    1. skitt and others to create a step-by-step guide and minimum required steps on th wiki
  5. tykeal
    1. phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better
  6. vishnoianil
    1. colindixon, vishnoianil, gzhao, anipbu and others to work to advertise APAC-friendly TSC calls to the India and China communities, as well as projects/PTLs in Asia
  7. 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


People present (lines said)

  1. colindixon (87)
  2. anipbu (16)
  3. odl_meetbot (15)
  4. jamoluhrsen (8)
  5. rovarga (7)
  6. tykeal (7)
  7. abhijitkumbhare (6)
  8. shague (5)
  9. vrpolak (4)
  10. zxiiro (4)
  11. skitt (4)
  12. hideyuki (3)
  13. Prem_ (3)
  14. edwarnicke (2)
  15. phrobb (1)
  16. vishnoianil (1)


Generated by MeetBot 0.1.4.