#opendaylight-meeting: tsc

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

Meeting summary

  1. roll call and agenda bashing (colindixon, 17:00:07)
    1. https://wiki.opendaylight.org/view/TSC:Main#Agenda the agenda in it’s usual place (colindixon, 17:00:42)
    2. colindixon (colindixon, 17:01:01)
    3. regXboi (regXboi, 17:01:09)
    4. Chris Price (ChrisPriceAB, 17:01:20)
    5. https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-03-26-17.00.html last week’s minutes (mostly for action items) (colindixon, 17:02:02)
    6. dlenrow (dlenrow, 17:02:16)
    7. jmedved (jmedved, 17:02:37)
    8. mohnish anumala (mohnish, 17:02:39)
    9. Eric Multanen on the phone for Uril (https://lists.opendaylight.org/pipermail/tsc/2015-April/002826.html) (colindixon, 17:02:57)
    10. Chris Wright (cdub, 17:04:05)
    11. edwarnicke (edwarnicke, 17:04:15)
    12. ACTION: LuisGomez to start drafting a list of qualifiers for an issue for being a blocker to an SR - edwarnicke to assist (colindixon, 17:04:32)
    13. ACTION: regXboi, Wojciech. edwarnicke, and Mahesh to organize meeting to talk about AAA keystone federation (colindixon, 17:05:07)
    14. ttkacik1 says that he has talked to Wojciech about how to boostrap AAA from the MD-SAL (action item from last week) (colindixon, 17:06:04)
    15. ACTION: LuisGomez to start a thread about how to unblock integration testing until patches are merged (colindixon, 17:06:20)

  2. Events (colindixon, 17:07:24)
    1. the hackfest is coming in 2 weeks, so projects please try to figure out what to dover (colindixon, 17:08:05)
    2. https://lists.opendaylight.org/pipermail/dev/2015-March/000409.html <- GPG keysigning party for hackfest information (tykeal, 17:08:05)
    3. the india forum is foign to happen the week of 4/21 (colindixon, 17:08:23)
    4. http://www.opendaylight.org/news/events/ events on the ODL page (colindixon, 17:08:36)
    5. OpenDaylight activities are planned at the OpenStack summit as well (ChrisPriceAB, 17:08:48)
    6. mini-summit (and cfp) for NFV world (colindixon, 17:09:45)
    7. mini-summit (and cfp) for the Open networking Summit (colindixon, 17:09:58)
    8. there’s our summit and design forum (we will call for topics for the design forum after Li releases) (colindixon, 17:10:34)
    9. regXboi asks if the hackfest would be virtual-friendly again? (regXboi, 17:10:53)
    10. phrobb says we’ll do the same as we’ve done in the past, but no more unless we have other ideas (colindixon, 17:11:11)
    11. answer is that what was is done in the past would be done again, but no more (regXboi, 17:11:12)
    12. Eric Multanen in attendance for Uri Elzur (snackewm, 17:11:38)
    13. there is an ONF app-fest planned in may. (ChrisPriceAB, 17:11:41)
    14. https://www.opennetworking.org/?p=1695&option=com_wordpress&Itemid=471 the ONF Appfest (nee Plugfest) is May 18-22 (colindixon, 17:11:53)
    15. abhijit adds that the event has extended to include applications and non-ONF members (ChrisPriceAB, 17:12:10)
    16. https://www.eventbrite.com/e/onf-appfest-registration-16131345288 registration closes on 4/10 (colindixon, 17:12:11)
    17. ODL hasn’t been there in the past, but in the last one HP used ODL to participate (colindixon, 17:13:13)
    18. ColinDixon asks if anyone is interested in participating (ChrisPriceAB, 17:13:54)
    19. ChrisPriceAB says Ericsson is hosting it and will be testing/presenting the ODL controller (colindixon, 17:14:01)
    20. ACTION: ChrisPriceAB to mail discuss/tsc (and others) to see if others are going to participate (colindixon, 17:14:31)
    21. mlemay will also be there (colindixon, 17:14:37)
    22. ACTION: abhijitkumbhare to pick up the action on to e-mail the lists. (ChrisPriceAB, 17:15:20)
    23. note it’s actualy the same dates as the OpenStack summit (colindixon, 17:15:26)
    24. ACTION: catohornet will send mail to Integration team about helping with app-fest (dfarrell07, 17:16:42)

  3. sytem integration & test (colindixon, 17:17:24)
    1. catohornet reports for Luis (away for week) on Integration (dfarrell07, 17:17:36)
    2. catohornet would like to encourage projects to get their system tests in as soon as possible (colindixon, 17:17:44)

  4. Lithium update (colindixon, 17:18:51)
    1. regXboi suggests having M* dates on Wednesdays (dfarrell07, 17:19:10)
    2. https://docs.google.com/spreadsheets/d/1KPpO9LH539Vlcoa4RvLa6PPCdLifi5JD-ihRhlybqeo/edit#gid=1196332566 Lithium tracking spreadsheet (colindixon, 17:20:07)
    3. phrobb says that there are 3 projects which are at risk of having to drop out of Lithium (colindixon, 17:21:31)
    4. Maple with Yale-related IPR issues is at risk fo getting no conent in (colindixon, 17:21:47)
    5. Plugin2OC has been effectively non-responsive for weeks now (colindixon, 17:22:01)
    6. https://lists.opendaylight.org/pipermail/plugin2oc-dev/2015-March/000069.html (zxiiro, 17:22:17)
    7. the SXP projec has also be non-responsive, but jmedved is working inside Cisco to try to revive them (colindixon, 17:22:27)
    8. phrobb et al have been very accommodating with non-responsive projects (dfarrell07, 17:23:25)
    9. phrobb says from his perspective that we have been as bend-over-backward willing to work with projects and they haven’t particpated at all (colindixon, 17:23:29)
    10. Plugin2OC non-merges/responses are blocking zxiiro's tagging efforts (dfarrell07, 17:24:51)
    11. edwarnicke suggests giving a (final, I think) warning to non-responsive projects about being dropped from Li (dfarrell07, 17:25:47)
    12. ACTION: phrobb to send mail to Plugin2OC saying that barring an objection from them, they are likely going to be dropped from Lithium at the next TSC meeting (colindixon, 17:27:22)
    13. ACTION: colindixon to send mail to the TSC list to start a conversation about how to deal with projects that have no remaining active committers (colindixon, 17:28:35)
    14. there are a few projects where the original committers are stepping down without new ones being promoted in their place (regXboi, 17:28:39)
    15. so how do we want to deal with projects where all committers are gone (regXboi, 17:28:56)
    16. New contributors have joined these non-responsive projects, but aren't committers, need a way to deal with this (dfarrell07, 17:29:02)
    17. jmedved has people to replace the committers on SXP, but we need to figure out the committer issue there (colindixon, 17:29:42)
    18. the problem is that the other three committers in SXP are unresponsive (regXboi, 17:29:58)
    19. colindixon and edwarnicke point out that obvious solutions to problems described above (terminate, force-add new committers, contact old committers) are painful or not working, looking for better ones (dfarrell07, 17:31:35)
    20. colindixon suggests moving this to the mailing list (dfarrell07, 17:33:19)
    21. zxiiro says he submitted a variety of patches around auto-release, and a working prototype of the auto-release builder based on that (colindixon, 17:34:16)
    22. ACTION: zxiiro to e-mail release to get people to merge patches with a list of patches (colindixon, 17:34:37)

  5. infrastructure (colindixon, 17:34:55)
    1. tykeal says sandbox has been moved to it’s own resources as of Tuesday to avoid contention with the releng/builder (colindixon, 17:35:18)
    2. tykeal says the releng/silo has been “gumming up” where it loses slaves and won’t bring new ones, the only current solution is to reset jenkings (colindixon, 17:35:48)
    3. they are detecting it and fixing when they can, but if you see it bring it to their attention (colindixon, 17:36:02)
    4. yesterday, people noted that people noted that gerrit pushes/patches were taking a long time, and they noted that there were queued jobs when it happened (colindixon, 17:36:46)
    5. possible solutions include moving to a machine with more RAM (colindixon, 17:36:58)
    6. ACTION: tykeal to add some of these issues to the Weather page: https://wiki.opendaylight.org/view/Weather (colindixon, 17:37:57)
    7. tykeal notes that we will likely get a dashboard and less issues that we have now as we move to nodepool and zuul (colindixon, 17:39:00)
    8. People should follow up with tykeal about key signing (dfarrell07, 17:40:19)

  6. Committer promotion of Martin Sunal for GBP (dfarrell07, 17:40:24)
    1. https://lists.opendaylight.org/pipermail/groupbasedpolicy-dev/2015-April/001039.html Nomination email thread (dfarrell07, 17:40:35)
    2. http://spectrometer.opendaylight.org/?metric=loc&release=all&user_id=msunal Spectrometer report for Martin Sunal (dfarrell07, 17:40:42)
    3. 4 (of 6) committters gave a +1 with no -1s (colindixon, 17:41:05)
    4. GBP issues with Spec reports, but has been contributing tons says alagalah (dfarrell07, 17:41:31)
    5. https://git.opendaylight.org/gerrit/#/q/project:groupbasedpolicy+owner:%22Martin+Sunal+%253Cmsunal%2540cisco.com%253E%22 patches on GBP (colindixon, 17:42:03)
    6. GBP only has two active committers, needs more (dfarrell07, 17:42:09)
    7. a major patch will come in the next week and we can review this again then (colindixon, 17:43:41)

  7. Beryllium Planning (dfarrell07, 17:44:35)
    1. colindixon suggests everyone chime in on mailing list thread (dfarrell07, 17:44:58)
    2. https://lists.opendaylight.org/pipermail/tsc/2015-April/002829.html Relevant mailing list thread (dfarrell07, 17:45:08)
    3. edwarnicke points out that everyone is very heads-down at the moment, will be hard to get input between now and Li (dfarrell07, 17:45:37)
    4. ChrisPriceAB says he feels it’s worth having the Beryllium discussion now (tbachman, 17:49:19)
    5. colindixon and cdub point out that people likely can find time to contribute to Be release discussion, even while heads-down (dfarrell07, 17:49:56)
    6. rovarga says that he wants to avoid what happened with Lithium where everyone vanished after Helium and did nothing and we rushed the Lithium plan out the door (colindixon, 17:50:31)
    7. rovarga points out that some projects are going to M5, which is only bug fixing (tbachman, 17:51:20)
    8. cdub agrees with rovarga — we have a history of doing the release and taking a long break/vacation (tbachman, 17:51:38)
    9. colindixon says we need to have the discussion on don’t change vs. meaningful change (tbachman, 17:52:06)
    10. ACTION: colindixon to add “consolidate requirements” to lesseons learned from Helium (colindixon, 17:52:55)
    11. edwarnicke says one of the major complaints he heard was what they had to do was scattered all over the place — a simple attempt to consolidate everything in to one place would help (tbachman, 17:52:58)
    12. colindixon elaborates on edwarnicke’s comment — testing requirements, doc requirements, and baseline release requirements were in different places (tbachman, 17:53:48)

  8. Board requests to the TSC (colindixon, 17:54:46)
    1. regXboi says he hopes to take time today to answer that (tbachman, 17:55:03)
    2. https://lists.opendaylight.org/pipermail/tsc/2015-March/002806.html board requests (colindixon, 17:55:23)
    3. https://lists.opendaylight.org/pipermail/tsc/2015-March/002818.html some of colindixon’s ideas for how to respond (colindixon, 17:55:35)
    4. https://lists.opendaylight.org/pipermail/tsc/2015-March/002740.html use case pipeline thread (started before) (colindixon, 17:55:49)
    5. ACTION: everyone please contribute to both the Be release planning and Board requests (colindixon, 17:56:32)
    6. on the previous topic, rovarga is fine with a 2 month preparation; but if that is to happen, we need to know now in order to plan for it (tbachman, 17:56:37)
    7. on the previous topic (release planning), regXboi brings up the possibility of using isotope type releases (tbachman, 17:57:41)
    8. colindixon would like to see the Beryllium release timeboxed (tbachman, 17:58:12)
    9. colindixon asks folks to chime in on the mailing list on Beryllium release planning for next week’s TSC (tbachman, 17:58:39)
    10. if you care about the Be relese plan try to chime in in the next week, as I’d like to be able to have sombody (phrobb?) create a draft release plan (colindixon, 17:58:47)
    11. even if only to say that you can’t afford time right now (colindixon, 17:59:24)

  9. performance isseus in the Lithium release (colindixon, 18:00:30)
    1. There are perf existing bugs, known and documented and bugs raised that need attention. (dfarrell07, 18:00:46)
    2. I actually wanted to imply that there are three topics wrestling for attention: getting Li out, getting Be planned, discussing the response to the Board. getting all done at the same time will prove ... challenging. (rovarga, 18:00:57)
    3. https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Performance_Test:Results wiki page for performance testing results (tbachman, 18:01:05)
    4. Integration team has some perf in CI, more going in to CI very soon (many people working on it actively) (dfarrell07, 18:01:24)
    5. regXboi sasy we need to figure out the Beryllium/Lithium isotope discussion (tbachman, 18:02:45)
    6. abhijitkumbhare says as per our charter we need to have 2 releases in the year - so a mini release lined up with OPNFV makes sense - otherwise we need to get an exception for the 2 release requirement (tbachman, 18:02:59)
    7. regXboi says OPNFV has a deadline in October — an isotope releases targeted at that use case may make sense, with Beryllium being a release that addresses larger issues (e.g. architecture) (tbachman, 18:03:37)
    8. colindixon urges again for folks to take this to the mailing list (tbachman, 18:04:14)

  10. cookies (regXboi, 18:05:09)


Meeting ended at 18:05:21 UTC (full logs).

Action items

  1. LuisGomez to start drafting a list of qualifiers for an issue for being a blocker to an SR - edwarnicke to assist
  2. regXboi, Wojciech. edwarnicke, and Mahesh to organize meeting to talk about AAA keystone federation
  3. LuisGomez to start a thread about how to unblock integration testing until patches are merged
  4. ChrisPriceAB to mail discuss/tsc (and others) to see if others are going to participate
  5. abhijitkumbhare to pick up the action on to e-mail the lists.
  6. catohornet will send mail to Integration team about helping with app-fest
  7. phrobb to send mail to Plugin2OC saying that barring an objection from them, they are likely going to be dropped from Lithium at the next TSC meeting
  8. colindixon to send mail to the TSC list to start a conversation about how to deal with projects that have no remaining active committers
  9. zxiiro to e-mail release to get people to merge patches with a list of patches
  10. tykeal to add some of these issues to the Weather page: https://wiki.opendaylight.org/view/Weather
  11. colindixon to add “consolidate requirements” to lesseons learned from Helium
  12. everyone please contribute to both the Be release planning and Board requests


Action items, by person

  1. abhijitkumbhare
    1. abhijitkumbhare to pick up the action on to e-mail the lists.
  2. ChrisPriceAB
    1. ChrisPriceAB to mail discuss/tsc (and others) to see if others are going to participate
  3. colindixon
    1. colindixon to send mail to the TSC list to start a conversation about how to deal with projects that have no remaining active committers
    2. colindixon to add “consolidate requirements” to lesseons learned from Helium
  4. edwarnicke
    1. LuisGomez to start drafting a list of qualifiers for an issue for being a blocker to an SR - edwarnicke to assist
    2. regXboi, Wojciech. edwarnicke, and Mahesh to organize meeting to talk about AAA keystone federation
  5. phrobb
    1. phrobb to send mail to Plugin2OC saying that barring an objection from them, they are likely going to be dropped from Lithium at the next TSC meeting
  6. regXboi
    1. regXboi, Wojciech. edwarnicke, and Mahesh to organize meeting to talk about AAA keystone federation
  7. tykeal
    1. tykeal to add some of these issues to the Weather page: https://wiki.opendaylight.org/view/Weather
  8. zxiiro
    1. zxiiro to e-mail release to get people to merge patches with a list of patches
  9. UNASSIGNED
    1. LuisGomez to start a thread about how to unblock integration testing until patches are merged
    2. catohornet will send mail to Integration team about helping with app-fest
    3. everyone please contribute to both the Be release planning and Board requests


People present (lines said)

  1. colindixon (86)
  2. tbachman (47)
  3. dfarrell07 (45)
  4. ChrisPriceAB (22)
  5. regXboi (22)
  6. odl_meetbot (14)
  7. cdub (8)
  8. dneary (7)
  9. edwarnicke (7)
  10. tykeal (4)
  11. gzhao (3)
  12. mohnish (3)
  13. dlenrow (2)
  14. rovarga (2)
  15. mlemay (2)
  16. zxiiro (2)
  17. snackewm (1)
  18. alagalah (1)
  19. abhijitkumbhare (1)
  20. jmedved (1)
  21. phrobb1 (0)
  22. phrobb (0)


Generated by MeetBot 0.1.4.