#opendaylight-meeting: tsc

Meeting started by colindixon at 17:00:13 UTC (full logs).

Meeting summary

  1. roll call and agenda bashing (colindixon, 17:00:20)
    1. colindixon (colindixon, 17:00:30)
    2. regXboi (regXboi, 17:00:42)
    3. https://wiki.opendaylight.org/view/TSC:Main#Agenda agenda in it’s usual place (colindixon, 17:00:47)
    4. alagalah_ for Jan Medved (alagalah_, 17:00:48)
    5. https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-03-12-17.00.html Minutes from last week’s meeting (tbachman, 17:01:05)
    6. Chris Price (ChrisPriceAB, 17:01:24)
    7. edwarnicke (edwarnicke, 17:01:35)
    8. ACTION: colindixon to continue to follow AD-SAL deprecation between VTN, OVSDB, and controller (are ther others?) (colindixon, 17:01:52)
    9. ACTION: colindixon keep the thread on best practices alive (colindixon, 17:02:05)
    10. zxiiro sent an mail about setting up opt-in/opt-out automatic version bump patches and tags (tbachman, 17:02:39)
    11. gzhao sent e-mail the release list with a precise time at which we will cut the SR3 test artifacts (tbachman, 17:03:00)
    12. dlenrow (dlenrow, 17:03:45)
    13. https://bugs.opendaylight.org/show_bug.cgi?id=2826 <- bug for SingleFeatureTest warm cache issue (edwarnicke, 17:03:50)
    14. colindixon added use cases to the topic list for this week, and emailed list (tbachman, 17:04:11)
    15. ACTION: gzhao and phrobb to provide a summary of milestone status to release and tsc lists for M3 and M4 (offset 0 only) (colindixon, 17:04:22)
    16. ACTION: phrobb to escalate/follow up with AAA (colindixon, 17:04:43)
    17. regXboi sent list out things that would hugely help people and how they work with ODL in a dashboard, and sent an email to discuss (tbachman, 17:04:44)
    18. mohnish anumala (mohnish, 17:04:55)
    19. ACTION: phrobb and zxiiro to follow up with the 2 projects not yet in JJB: plugin2oc, defense4all (tbachman, 17:06:25)
    20. https://wiki.opendaylight.org/view/TSC:Vulnerability_Management <- draft security process (regXboi, 17:06:45)
    21. regXboi translated google md doc to wikipage (tbachman, 17:07:03)
    22. ACTION: rovarga (with help from Thanh) to work on tracking latency from merge to all CSIT (colindixon, 17:07:38)
    23. https://lists.opendaylight.org/pipermail/discuss/2015-March/004867.html <- thread on ODL dashboard in discuss (regXboi, 17:07:47)
    24. LuisGomez (LuisGomez, 17:08:07)
    25. ACTION: dlenrow to send mail to relase, persistence-dev, and tsc describing the issue and possible solutions for discussion (colindixon, 17:09:44)

  2. Updates (tbachman, 17:10:48)
    1. http://www.opendaylight.org/news/events << Events page on ODL Website (phrobb, 17:10:55)
    2. colindixon asks if the above is an issue for folks (deferring to email list for discussion potentially at next TSC) and silence is acquiescence. (alagalah_, 17:10:56)
    3. phrobb says hackfest has 37 people registered, but expects lots more to attend (urges folks to register) (tbachman, 17:11:28)
    4. phrobb says there’s an NFV World Congress on May 5th. CFP is out for that now (tbachman, 17:11:41)
    5. phrobb says they’ll be sending out a CFP for ONS in June (colindixon, 17:12:35)
    6. colindixon asks when speakers will be informed abuot talks at openstack summit (tbachman, 17:13:08)
    7. phrobb thinks it’s soon, but isn’t sure (tbachman, 17:13:16)
    8. regXboi makes a general request (not events) for projects to add list archive link to their main page (possibly in the project box)? (regXboi, 17:13:41)
    9. https://docs.google.com/spreadsheets/d/1PYxjiSYEks44uJByVO1P44rnI5xTJRulpKyrSsDQF9g/edit#gid=347238944 (gzhao, 17:13:53)

  3. Helium SR3 (colindixon, 17:13:59)
    1. : https://docs.google.com/spreadsheets/d/1PYxjiSYEks44uJByVO1P44rnI5xTJRulpKyrSsDQF9g/edit#gid=347238944 Spreadsheet for tracking bugs for SR3 (tbachman, 17:14:12)
    2. https://lists.opendaylight.org/pipermail/tsc/2015-March/002742.html LISP flow mapping is asking for a respin (regXboi, 17:15:06)
    3. colindixon asks whether the TSC should allow the respin (tbachman, 17:15:57)
    4. edwarnicke asks what are the counterbalancing things that go into the decision (tbachman, 17:16:06)
    5. lori says there’s a user that’s submitted this interoperability issue with external software (tbachman, 17:16:32)
    6. lori says this would significantly delay productization with ODL for this product (tbachman, 17:16:51)
    7. lori says the July time frame is too long for that (tbachman, 17:17:04)
    8. colindixon asks if there’s a mechanism to cherry pick that local patch (tbachman, 17:17:11)
    9. lori says there’s someone else in the company that’s brought this to ODL (tbachman, 17:17:23)
    10. edwarnicke asks what is the nature and severity of the bug (tbachman, 17:17:35)
    11. https://bugs.opendaylight.org/show_bug.cgi?id=2871 the bug in question (colindixon, 17:17:46)
    12. lori says LISP is providing the mapping service, and for that to happen, you can register mappings to the northbound or the southbound (tbachman, 17:17:54)
    13. https://git.opendaylight.org/gerrit/#/c/16798/ the patch (colindixon, 17:17:56)
    14. lori says the authentication on the southbound fails b/c they aren’t correctly serializing some of the data (tbachman, 17:18:09)
    15. lori says there’s a protocol extension that’s not an RFC yet but is widely used; when this extension is used, this bug occurs (tbachman, 17:18:35)
    16. colindixon asks for more input from TSC members (tbachman, 17:18:42)
    17. LuisGomez says from what he hears, this is not a critical bug (tbachman, 17:18:59)
    18. regXboi says +1 to LuisGomez (tbachman, 17:19:06)
    19. colindixon asks for more input, before putting this to a vote whether to bless the SR3 release (tbachman, 17:19:51)
    20. colindixon asks if there’s someone on the call who can speak as to why this patch can’t be cherry-picked for their release (tbachman, 17:20:42)
    21. Saurabh says the only reason is that when you go to the end-customer, they expect it to be a standard release, not one with a patch (tbachman, 17:21:41)
    22. colindixon asks if the TSC feels they have enough information to vote on the SR3 artifacts now, or delay a week (tbachman, 17:22:15)
    23. mohnish says this may be setting a precedent for future SR releases — if we find a bug, what will we do (tbachman, 17:23:33)
    24. ChrisPriceAB says that if we find a bug in a stable release, he usually asks if it blocks the release that stable is based on, and if not, they go for it (tbachman, 17:24:10)
    25. edwarnicke says one of our principles is that we like our stable releases to be more stable than past releases; asks if this is a new bug, or has it always been there (tbachman, 17:24:48)
    26. slight correction, if it blocks the functionality of the stable release we go ahead with it. (ChrisPriceAB, 17:24:54)
    27. lori says this bug has been there (tbachman, 17:25:14)
    28. VOTE: Voted on "Shall the TSC approve the release of Helium SR3?" Results are, 0: 1, +1: 7 (phrobb, 17:26:25)
    29. AGREED: The TSC has approved the release of Helium SR3 (phrobb, 17:26:40)
    30. edwarnicke says this is an existing bug, not introduced by Helium SR2 (gzhao, 17:27:00)
    31. colindixon offers Saurabh help for cherry-picking patches needed (tbachman, 17:27:07)
    32. LuisGomez asks if there’s a single place what are blockers for a release, so that people can search there and look to see blockers (tbachman, 17:27:33)
    33. ACTION: LuisGomez to start drafting a list of qualifiers for an issue for being a blocker to an SR - edwarnicke to assist (regXboi, 17:28:04)

  4. Lithium (tbachman, 17:28:54)
    1. gzhao says PCMM changed from yellow to green; only Maple is not green (tbachman, 17:29:26)
    2. last week 3 projects changed status, ALTO changed from red to green, packetcable changes from yellow to green (for M2 in both cases) (colindixon, 17:29:27)
    3. NeutronNorthbound changed from yellow to green for M3 (offset 1) (regXboi, 17:29:49)
    4. gzhao says there are 6 projects in yellow, with more to come after today’s M3 (tbachman, 17:30:44)
    5. gzhao says that currently we have 6 projects in yellow and he expects that to grow, he says many projects are 1-2 weeks behind, and 4 projects have yet to report (colindixon, 17:30:59)
    6. regXboi says there is a TON of documentation behind M3 (regXboi, 17:32:04)
    7. rovarga says some of the concerns coming from yangtools and controller are due to lack of resources; hope to make this up in the run-up to M5 (tbachman, 17:32:39)
    8. ttkacik1 says the problem wasn’t too much paperwork, but that it wasn’t obvious (“hidden”) what/how much needed to be done (tbachman, 17:33:53)
    9. colindixon urges projects to be honest in their reporting and do their best to get through this — TSC is willing to work with projects that are reasonable and are working towards these goals (tbachman, 17:34:22)
    10. zxiiro asks about stable/helium and Lithium (tbachman, 17:35:12)

  5. opt-out from auto version bumping (colindixon, 17:35:25)
    1. zxiiro says he sent the opt-out email earlier this week; no projects have responded, indicating opt-out; asks if we can version-bump now, or wait until M4 (tbachman, 17:35:47)
    2. rovarga says he’s seen the email, but hasn’t had time to address this yet; asks for another 2-3 days (tbachman, 17:36:02)
    3. https://lists.opendaylight.org/pipermail/release/2015-March/001652.html the mail asking people to opt-out if they want to (colindixon, 17:36:10)
    4. mohnish asks if projects should list “at-risk” features during M<n> milestones (tbachman, 17:37:05)
    5. colindixon says that’s what he hopes phrobb and gzhao will do with their summary in the next few days (colindixon, 17:38:18)

  6. lithium auto-release and super-pom-based building (colindixon, 17:38:58)
    1. ACTION: rovarga and zxiiro to work on this for another week and bring it to the TSC then if need be (colindixon, 17:40:24)
    2. https://lists.opendaylight.org/pipermail/release/2015-March/001626.html Thread for the super-pom-based building (tbachman, 17:41:04)
    3. phrobb asks when auto-release will be in jeapordy without a decision (tbachman, 17:41:20)
    4. zxiiro says they believed they’ve committed to M4 for being able to successfully build Lithium autorelease (tbachman, 17:42:02)
    5. colindixon asks what offset autorelease is (tbachman, 17:42:08)
    6. the line in the sand is 4/16 to have lithium auto-release working (colindixon, 17:42:22)
    7. phrobb asks zxiiro when there’s a decision, how long it will take to get autorelease up and running (tbachman, 17:43:25)
    8. zxiiro says this is hard to tell — if we have to change the way we’re doing it, and he has to create a script to dynamically determine relative paths, that may take a bit (tbachman, 17:44:06)
    9. LuisGomez asks that we have this worked out by the next TSC call (tbachman, 17:44:55)
    10. colindixon says he’d like to see an agreed-upon decision brought to the TSC (tbachman, 17:45:10)
    11. edwarnicke says this problem was solved in Helium — scaling may be an issue, but it’s a solvable issue (tbachman, 17:45:27)

  7. Security Process for ODL (tbachman, 17:45:36)
    1. https://lists.opendaylight.org/pipermail/tsc/2015-March/002688.html Email thread on security process (tbachman, 17:46:10)
    2. regXboi asks if we can start a vote on email (tbachman, 17:46:27)
    3. https://lists.opendaylight.org/pipermail/tsc/2015-March/002739.html please vote starting here (colindixon, 17:46:37)
    4. ACTION: ALL TSC MEMBERS vote on the secruity proces thread (colindixon, 17:47:02)

  8. Archiving the OSCP project (tbachman, 17:47:20)
    1. https://wiki.opendaylight.org/view/Archive_Proposals/OpenDaylight_SDN_Controller_Platform_%28OSCP%29 proposal to archive (colindixon, 17:47:33)
    2. https://lists.opendaylight.org/pipermail/tsc/2015-March/002682.html Email talking about archiving of OSCP (tbachman, 17:47:58)
    3. VOTE: Voted on "Shall the TSC Archive the OSCP Project?" Results are, +1: 8 (phrobb, 17:49:20)
    4. https://lists.opendaylight.org/pipermail/tsc/2015-March/002743.html (colindixon, 17:50:00)
    5. AGREED: The TSC has moved the OSCP project to the Archive lifecycle state. (tbachman, 17:50:07)

  9. Proposed Extended Lithium SR dates (tbachman, 17:50:17)
    1. https://lists.opendaylight.org/pipermail/tsc/2015-March/002743.html email describing proposed dates (tbachman, 17:50:34)
    2. LuisGomez says we polled the projects for supporting 1 or 2 releases; what was the result of that poll? (tbachman, 17:52:10)
    3. phrobb says most agreed to 1 release, less consensus on supporting 2 releases (tbachman, 17:52:24)
    4. AGREED: SR3/SR4 will happen no sooner than 12/17 and 3/24, and are targets for SR3/SR4 for the Lithium Release (tbachman, 17:55:26)
    5. AGREED: Lithium SR3 and SR4 will happen no sooner than the dates in https://lists.opendaylight.org/pipermail/tsc/2015-March/002743.html (regXboi, 17:55:26)
    6. ACTION: gzhao will add the two dates above to the Li release info (dfarrell07, 17:55:40)

  10. weather page (regXboi, 17:55:58)
    1. https://wiki.opendaylight.org/view/Weather wiki page describing proposed weather page (tbachman, 17:57:03)
    2. https://lists.opendaylight.org/pipermail/discuss/2015-March/004858.html mail suggsting the idea (regXboi, 17:57:09)
    3. regXboi notes that it would be nice if that page was factored into the dashboard, but I'm at a loss on how to do it (regXboi, 17:57:58)
    4. LuisGomez says we can start with the release list, referencing the weather page (tbachman, 17:59:28)

  11. cookies (tbachman, 18:03:07)


Meeting ended at 18:03:10 UTC (full logs).

Action items

  1. colindixon to continue to follow AD-SAL deprecation between VTN, OVSDB, and controller (are ther others?)
  2. colindixon keep the thread on best practices alive
  3. gzhao and phrobb to provide a summary of milestone status to release and tsc lists for M3 and M4 (offset 0 only)
  4. phrobb to escalate/follow up with AAA
  5. phrobb and zxiiro to follow up with the 2 projects not yet in JJB: plugin2oc, defense4all
  6. rovarga (with help from Thanh) to work on tracking latency from merge to all CSIT
  7. dlenrow to send mail to relase, persistence-dev, and tsc describing the issue and possible solutions for discussion
  8. LuisGomez to start drafting a list of qualifiers for an issue for being a blocker to an SR - edwarnicke to assist
  9. rovarga and zxiiro to work on this for another week and bring it to the TSC then if need be
  10. ALL TSC MEMBERS vote on the secruity proces thread
  11. gzhao will add the two dates above to the Li release info


Action items, by person

  1. colindixon
    1. colindixon to continue to follow AD-SAL deprecation between VTN, OVSDB, and controller (are ther others?)
    2. colindixon keep the thread on best practices alive
  2. dlenrow
    1. dlenrow to send mail to relase, persistence-dev, and tsc describing the issue and possible solutions for discussion
  3. edwarnicke
    1. LuisGomez to start drafting a list of qualifiers for an issue for being a blocker to an SR - edwarnicke to assist
  4. gzhao
    1. gzhao and phrobb to provide a summary of milestone status to release and tsc lists for M3 and M4 (offset 0 only)
    2. gzhao will add the two dates above to the Li release info
  5. LuisGomez
    1. LuisGomez to start drafting a list of qualifiers for an issue for being a blocker to an SR - edwarnicke to assist
  6. phrobb
    1. gzhao and phrobb to provide a summary of milestone status to release and tsc lists for M3 and M4 (offset 0 only)
    2. phrobb to escalate/follow up with AAA
    3. phrobb and zxiiro to follow up with the 2 projects not yet in JJB: plugin2oc, defense4all
  7. UNASSIGNED
    1. rovarga (with help from Thanh) to work on tracking latency from merge to all CSIT
    2. rovarga and zxiiro to work on this for another week and bring it to the TSC then if need be
    3. ALL TSC MEMBERS vote on the secruity proces thread


People present (lines said)

  1. tbachman (133)
  2. colindixon (55)
  3. regXboi (38)
  4. odl_meetbot (26)
  5. alagalah_ (24)
  6. ChrisPriceAB (12)
  7. edwarnicke (11)
  8. dfarrell07 (10)
  9. tykeal (10)
  10. phrobb (9)
  11. dlenrow (6)
  12. dneary (5)
  13. mohnish (5)
  14. gzhao (5)
  15. LuisGomez (3)
  16. abhijitkumbhare (3)
  17. snoble (1)


Generated by MeetBot 0.1.4.