#opendaylight-meeting: tsc

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

Meeting summary

  1. agenda bashing and roll call (colindixon, 17:00:32)
    1. gkaempfer (gkaempfer, 17:00:38)
    2. colindixon (colindixon, 17:00:40)
    3. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-07-28-17.00.html last week's meeting minutes part 1 (colindixon, 17:00:50)
    4. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-07-28-17.40.html last week's meeting minutes part 2 (colindixon, 17:00:59)
    5. adetalhouet (adetalhouet, 17:01:13)
    6. ACTION: anipbu to track the removal of ancient dependencies and readout next time how far we get (colindixon, 17:01:26)
    7. abhijitkumbhare (abhijitkumbhare, 17:01:35)
    8. ACTION: colindixon to get CaseyODL to replay about nofollow on the TSC list so we get an actual ruling (colindixon, 17:01:38)
    9. ACTION: anipu to follow up with relevant projects about distribution size: https://lists.opendaylight.org/pipermail/release/2016-July/007250.html (colindixon, 17:01:49)
    10. ACTION: colindixon to try to drive some/all of the ongoing TSC discussions to completion (colindixon, 17:02:10)
    11. Daniel Farrell (dfarrell07, 17:02:23)
    12. Anil Vishnoi (vishnoianil, 17:02:48)
    13. Chris Price (ChrisPriceAB, 17:03:02)
    14. ACTION: edwarnicke to send out his analysis ouf how to remove nodejs servers from people pulling in dlux to see if that helps (colindixon, 17:03:17)
    15. Mohnish Anumala (mohnish__, 17:03:23)
    16. https://lists.opendaylight.org/pipermail/tsc/2016-August/005725.html features that are currently labeled as experimental, comment there if you disagree or things have changed (colindixon, 17:04:15)
    17. ACTION: colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron/Carbon? (colindixon, 17:04:25)
    18. ACTION: phrobb to work on having a policy for how attendance to design forums works going forward with community involvement (colindixon, 17:04:32)
    19. ACTION: colindixon and phrobb to set up a poll of committers, PTLs and TSC members to see if there's a desire to have one TSC meeting a month at an APAC-friendly time (colindixon, 17:04:37)
    20. ACTION: phrobb to add linuxcon europe to the events list (colindixon, 17:05:02)
    21. ACTION: colindixon to add TSC elections to the agenda for next week (colindixon, 17:05:13)
    22. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=48214#Agenda the agenda in it's usual place (colindixon, 17:06:13)
    23. edwarnicke says that he's been trying to help get projects into the distribution, it's been bumpy for a variety of reasons,b ut making progress (colindixon, 17:07:06)
    24. rovarga for jmedved (rovarga, 17:07:27)

  2. TSC mail list discussions and votes (colindixon, 17:07:46)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-July/005695.html vote to set tentaive dates for a tradition carbon release plan passed (colindixon, 17:08:13)
    2. next step it hammer out what we need to get done and plan it for this release so that we can credibly take a stab at fast and/or phased if we want to for Nitrogen (colindixon, 17:08:44)
    3. ACTION: colindixon to start an e-mail thread trying to start a fast and/or phased experience during Carbon (pull in skitt, rovarga, and edwarnicke) (colindixon, 17:10:06)
    4. https://lists.opendaylight.org/pipermail/tsc/2016-July/005539.html escalation process we have in OpenDaylight (colindixon, 17:10:17)
    5. https://lists.opendaylight.org/pipermail/tsc/2016-June/005377.html Additional questions in the Project Proposal Template (colindixon, 17:10:31)
    6. https://lists.opendaylight.org/pipermail/tsc/2016-June/005407.html Asking the Board to Remove the Singularity Principle (colindixon, 17:10:35)
    7. https://lists.opendaylight.org/pipermail/tsc/2016-July/005594.html Categorizing projects, both on the wiki and for new projects to browse (colindixon, 17:10:45)
    8. edwarnicke (edwarnicke, 17:11:10)

  3. event (colindixon, 17:11:26)
    1. https://www.opendaylight.org/global-events (colindixon, 17:11:32)
    2. openstack sillicon valley and openstack east coming up wtih OpenDaylight involvement (colindixon, 17:12:39)
    3. opendalyight summit is coming up at the end of september (colindixon, 17:12:47)
    4. linuxcon Europe has a talk on ODL performance (from dfarrell07) (colindixon, 17:13:13)
    5. CFP for the OpenDaylight forum in India, CFP closes next week (colindixon, 17:13:53)

  4. boron (colindixon, 17:15:53)
    1. There are plans to change the yang model leaf name of tcp_flag in OpenFlowPlugin. Fix patches are pushed to all the impacted project: netvirt, genius, sfc, nic, vtn, didm (colindixon, 17:16:05)
    2. https://wiki.opendaylight.org/view/Simultaneous_Release/Boron/Waiver/API/Records#OpenFlow_plugin_Tcp_Flags_API_Change_Waiver <--- Link to API Change (colindixon, 17:16:23)
    3. Kindly remind projects to submit API Change Waiver if submitting any changes to the API such as yang files after M4 (colindixon, 17:16:42)
    4. https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-boron/203/ <--- Successful build of Boron Autorelease. (colindixon, 17:16:51)
    5. that also means we'll be doing branch cutting today (colindixon, 17:17:31)
    6. dfarrell07 and zxiiro say that there have been some conversations about delaying the release and/or M5 if we're having issues (colindixon, 17:20:40)
    7. jamoluhrsen says that if we weren't able to fix the distribution size limit, we might have to delay the final release, but seemingly not M5 (colindixon, 17:21:08)
    8. LuisGomez says we need to fix the distribution size issue in 1-2 days or we really will need to consider letting the release slip (colindixon, 17:22:05)
    9. colindixon asks if there's a reason we couldn't temporarily increase the nexus size limit to avoid slipping Boron while we fix it? (colindixon, 17:24:02)
    10. https://bugs.opendaylight.org/show_bug.cgi?id=6341 <--- blocker bug for distro size (jamoluhrsen, 17:24:12)
    11. , discussion ensues on the sanity of the huge distro. (phrobb, 17:24:44)
    12. the plan proposed is for Andy to increase the size allowed in Nexus so that other progress can be made. At the same time a blocking bug will be posted on the distro size and a condition of bug fix is to revert the max size limit to 500MB (phrobb, 17:27:18)
    13. ACTION: tykeal to increase the file limit from 512MB to 600MB to get us pas tthis hump (colindixon, 17:27:26)
    14. Andy to increase the size by 100MB to 600MB while this issue persists and the blocking bug is open (phrobb, 17:28:10)
    15. ACTION: jamoluhrsen should add to the bug that we need to have the nexus file size limit set to 512 MB again (colindixon, 17:28:36)
    16. quote: [8/4/16 16:13:51] <shague> zxiiro: any idea if we are going to relax the m5 deadline today? infra has been painful during this crucial time (rovarga, 17:29:53)
    17. colindixon says that projects should please raise their issues on the release and/or tsc list so we can figure out how to deal with it up-to and/or including a delay (colindixon, 17:30:41)
    18. colindixon says that if it's one project and a leaf project (which I think netvirt is) that this shoudl be handled for the one project instead of delaying the entire release over it (colindixon, 17:32:43)
    19. jamoluhrsen says VTN likely has simlar issues (colindixon, 17:32:50)
    20. colindixon says, obviously we'll dealy the release if we have to at the end if we'll have regressions (colindixon, 17:33:06)
    21. that being said (and edwarnicke and dfarrell07 agree) that we should wait until we get to the point we feel we have to dealy the final relese (colindixon, 17:33:33)
    22. obviously, if the approach seems fatally flawed, please speak up, the TSC exists to help projects get stuff done (colindixon, 17:34:14)

  5. stable/beryllum (colindixon, 17:34:26)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-August/005710.html Beryllium-SR3 release status: Ready to go (colindixon, 17:34:57)
    2. VOTE: Voted on "shall the TSC approve the Beryllium-SR release as linked to in the above mail?" Results are, +1: 10 (colindixon, 17:37:04)
    3. AGREED: by consenus, the TSC approves the Beryllium-SR3 release (colindixon, 17:37:21)

  6. singlularity discussions (colindixon, 17:39:03)
    1. this was a topic at the board 2 meetings ago, and a small group of people was going to try to explain the intent of those principles and it would maybe help the discussion (colindixon, 17:39:38)
    2. phrobb says he expects that to come back at the beginning of september (colindixon, 17:40:08)

  7. TSC elections (colindixon, 17:40:30)
    1. there was TWS on Monday on the TSC elections and our progress (colindixon, 17:40:41)
    2. https://meetings.opendaylight.org/opendaylight-meeting/2016/tws/opendaylight-meeting-tws.2016-08-01-17.00.html meeting minutes (colindixon, 17:40:56)
    3. https://wiki.opendaylight.org/view/Tech_Work_Stream:Main there's a WebEx recording that should be posted here (colindixon, 17:41:19)
    4. the results of the meeting were that we needed to do 3 things: (1) pick represented groups, (2) pick election cadence, (3) make sure we work out corner cases of using the tools we have (colindixon, 17:42:17)
    5. ACTION: colindixon and edwarnicke to try to work through the corner cases and process of the TSC elections (colindixon, 17:43:24)
    6. ACTION: dfarrell07 to upate the wiki about what happens when a person is a PTL for more than one project in the same represented group (colindixon, 17:44:01)
    7. https://meetings.webex.com/collabs/url/R2WM4rG0u4td9xj_n_xbKIKyWrZp7hZvOlvPnsnQYhG00000 <-- Link to Webex Recording of the TWS meeting on the Elections Process (colindixon, 17:44:08)
    8. the other corner case is how to do weighted elections after the fact, e.g., scaled-popularity (colindixon, 17:44:32)
    9. https://wiki.opendaylight.org/view/TSC:Election_Proposal the wiki page on this (colindixon, 17:44:52)
    10. https://wiki.opendaylight.org/view/TSC:Election_Proposal#All_Types.2C_Mature_Lifecycle_States in particular dfarrell07 says this one seems to have had the most support so far (colindixon, 17:45:39)
    11. ACTION: dfarrell07 to try to get us to the point that we coudl vote on (1) and (2) above (colindixon, 17:46:05)

  8. cookies (colindixon, 17:46:39)


Meeting ended at 17:46:45 UTC (full logs).

Action items

  1. anipbu to track the removal of ancient dependencies and readout next time how far we get
  2. colindixon to get CaseyODL to replay about nofollow on the TSC list so we get an actual ruling
  3. anipu to follow up with relevant projects about distribution size: https://lists.opendaylight.org/pipermail/release/2016-July/007250.html
  4. colindixon to try to drive some/all of the ongoing TSC discussions to completion
  5. edwarnicke to send out his analysis ouf how to remove nodejs servers from people pulling in dlux to see if that helps
  6. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron/Carbon?
  7. phrobb to work on having a policy for how attendance to design forums works going forward with community involvement
  8. colindixon and phrobb to set up a poll of committers, PTLs and TSC members to see if there's a desire to have one TSC meeting a month at an APAC-friendly time
  9. phrobb to add linuxcon europe to the events list
  10. colindixon to add TSC elections to the agenda for next week
  11. colindixon to start an e-mail thread trying to start a fast and/or phased experience during Carbon (pull in skitt, rovarga, and edwarnicke)
  12. tykeal to increase the file limit from 512MB to 600MB to get us pas tthis hump
  13. jamoluhrsen should add to the bug that we need to have the nexus file size limit set to 512 MB again
  14. colindixon and edwarnicke to try to work through the corner cases and process of the TSC elections
  15. dfarrell07 to upate the wiki about what happens when a person is a PTL for more than one project in the same represented group
  16. dfarrell07 to try to get us to the point that we coudl vote on (1) and (2) above


Action items, by person

  1. colindixon
    1. colindixon to get CaseyODL to replay about nofollow on the TSC list so we get an actual ruling
    2. colindixon to try to drive some/all of the ongoing TSC discussions to completion
    3. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron/Carbon?
    4. colindixon and phrobb to set up a poll of committers, PTLs and TSC members to see if there's a desire to have one TSC meeting a month at an APAC-friendly time
    5. colindixon to add TSC elections to the agenda for next week
    6. colindixon to start an e-mail thread trying to start a fast and/or phased experience during Carbon (pull in skitt, rovarga, and edwarnicke)
    7. colindixon and edwarnicke to try to work through the corner cases and process of the TSC elections
  2. dfarrell07
    1. dfarrell07 to upate the wiki about what happens when a person is a PTL for more than one project in the same represented group
    2. dfarrell07 to try to get us to the point that we coudl vote on (1) and (2) above
  3. edwarnicke
    1. edwarnicke to send out his analysis ouf how to remove nodejs servers from people pulling in dlux to see if that helps
    2. colindixon to start an e-mail thread trying to start a fast and/or phased experience during Carbon (pull in skitt, rovarga, and edwarnicke)
    3. colindixon and edwarnicke to try to work through the corner cases and process of the TSC elections
  4. jamoluhrsen
    1. jamoluhrsen should add to the bug that we need to have the nexus file size limit set to 512 MB again
  5. phrobb
    1. phrobb to work on having a policy for how attendance to design forums works going forward with community involvement
    2. colindixon and phrobb to set up a poll of committers, PTLs and TSC members to see if there's a desire to have one TSC meeting a month at an APAC-friendly time
    3. phrobb to add linuxcon europe to the events list
  6. rovarga
    1. colindixon to start an e-mail thread trying to start a fast and/or phased experience during Carbon (pull in skitt, rovarga, and edwarnicke)
  7. tykeal
    1. tykeal to increase the file limit from 512MB to 600MB to get us pas tthis hump
  8. UNASSIGNED
    1. anipbu to track the removal of ancient dependencies and readout next time how far we get
    2. anipu to follow up with relevant projects about distribution size: https://lists.opendaylight.org/pipermail/release/2016-July/007250.html


People present (lines said)

  1. colindixon (91)
  2. odl_meetbot (8)
  3. jamoluhrsen (7)
  4. ChrisPriceAB (5)
  5. abhijitkumbhare (5)
  6. rovarga (4)
  7. phrobb (4)
  8. vishnoianil (4)
  9. mohnish__ (2)
  10. gkaempfer (2)
  11. adetalhouet (2)
  12. dfarrell07 (2)
  13. edwarnicke (2)
  14. vrpolak (1)
  15. tykeal (1)


Generated by MeetBot 0.1.4.