#opendaylight-meeting: tsc

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

Meeting summary

  1. agenda bashing and roll call (colindixon, 17:00:51)
    1. abhijitkumbhare (abhijitkumbhare, 17:00:58)
    2. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-10-13-17.01.html last week's meeting minutes (colindixon, 17:00:58)
    3. Anil Vishnoi (vishnoianil, 17:00:58)
    4. Daniel Farrell (dfarrell07, 17:00:59)
    5. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=51162#Agenda the agenda in it's usual place (colindixon, 17:01:17)
    6. colindixon (colindixon, 17:01:20)
    7. Stephen Kitt standing in for Alexis de Talhouët (skitt, 17:01:41)
    8. ACTION: colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way (colindixon, 17:01:48)
    9. Chris Price (ChrisPriceAB, 17:01:50)
    10. ACTION: colindixon and zxiiro to work on trying to build tools to help with what's failing on failures in our jenkins jobs (colindixon, 17:01:55)
    11. ACTION: dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion (colindixon, 17:02:00)
    12. ACTION: phrobb to get the OPNFV plugfest on our events page http://events.linuxfoundation.org/events/opnfv-plugfest/ (colindixon, 17:02:33)
    13. ACTION: phrobb to work on getting us bettter control of the events page to make his life less painful (colindixon, 17:03:11)
    14. ACTION: phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better (colindixon, 17:03:19)
    15. gkaempfer (gkaempfer, 17:04:55)
    16. ACTION: colindixon to add the agenda topic that networking-odl seems like it will be kicked out of ocata unless we improve our results on a scorecard (colindixon, 17:05:14)
    17. rovarga for jmedved (rovarga, 17:05:25)
    18. scorecard for networking-odl recently done by Newtron team: https://review.openstack.org/#/c/383910/6/specs/stadium/ocata/networking-odl.rst (phrobb, 17:06:39)
    19. https://review.openstack.org/#/c/383910/ the review for networking-odl in ocata (colindixon, 17:07:00)
    20. isaku says he things the major issue is the peception is that we are closer to a vendor driver than a "stadium" driver (colindixon, 17:08:02)
    21. isaku says that the general feeling is that the opendaylight community is not cooperative with the neutron community, edwarnicke asks how and isaku answers basically in that we stay inside our own boundaries and don't participate more broadly (colindixon, 17:09:11)
    22. ACTION: colindixon start a thread on networking ODL in ocata on the neutron-dev list: https://review.openstack.org/#/c/383910/6/specs/stadium/ocata/networking-odl.rst (colindixon, 17:10:38)
    23. ChrisPriceAB looked a how OpenDaylight and OPNFV will line up for the next release (colindixon, 17:11:41)
    24. it looks like OPNFV releases at the same time that we have code freeze, which will obviously have issues (colindixon, 17:12:18)
    25. ChrisPriceAB asks the TSC if there are ideas about how to get the projects that cross OPNFV/ODL over to OPNFV in a way that works (colindixon, 17:14:47)
    26. ACTION: ChrisPriceAB to open a maling list thread on release@ and tsc@ to talk about how to help projects that cross ODL/OPNFV deliver on promises in both places at the same time (colindixon, 17:16:43)
    27. tykeal says that pre-boron branches were a bit of a pain, and nobody used it, which this would effectively be similar (colindixon, 17:18:19)
    28. dfarrell07 says that what OPNFV really needs is builds with semi-stable patches released regularly with known issues, making sure autorelease runs wihtout failures more regularly would be huge (colindixon, 17:19:37)
    29. edwarnicke gives a pitch for dfarrell07's work on a continuous pipeline from OpenDaylight to OPNFV (and other downstreams) being expanded (colindixon, 17:20:06)

  2. events (colindixon, 17:21:02)
    1. https://www.opendaylight.org/global-events (colindixon, 17:21:10)
    2. fd.io already has continuous pipelines to OpNFV, and edwarnicke is more than happy to share lessons learned ;) (edwarnicke, 17:21:10)
    3. openstack in barcelona next week, there is a ODL/OPNFV reception as part of that on Tuesday night, you should receive info soon if you haven't already (colindixon, 17:21:55)
    4. india forum coming up november 16th (colindixon, 17:22:07)
    5. MEF 16 coming up on 11/7 (colindixon, 17:22:27)
    6. https://www.surveymonkey.com/r/RZKD83B OPNFV / ODL reception link (ChrisPriceAB, 17:22:30)
    7. OPNFV plugfest on 12/6-12/9 (colindixon, 17:22:40)

  3. boron (colindixon, 17:22:54)
    1. Boron-SR1 is next week on October 27 with a cutoff this Sunday on 10/23 23:59 UTC. (anipbu, 17:23:08)
    2. The Boron Autorelease job is passing. (anipbu, 17:23:12)
    3. https://git.opendaylight.org/gerrit/#/q/status:open+branch:stable/boron <--- 33 patches pending for stable/boron (anipbu, 17:23:20)
    4. https://bugs.opendaylight.org/buglist.cgi?bug_severity=blocker&bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=WAITING_FOR_REVIEW&f1=cf_target_milestone&f2=cf_target_milestone&j_top=OR&list_id=67733&o1=substring&o2=substring&query_format=advanced&resolution=---&v1=Boron&v2=--- <--- Two blocker bugs in openflowplugin (anipbu, 17:23:37)
    5. https://git.opendaylight.org/gerrit/#/dashboard/?title=Boron+Status&Yang+File+Changes+Since+Boron=branch:stable/boron+status:merged+file:%22%255E.%252Byang%22+after:2016-09-15 <--- 34 patches modifying yang files without API Freeze Waiver between Boron Release and Boron SR1 (anipbu, 17:24:01)

  4. beryllium (colindixon, 17:24:47)
    1. Beryllium SR4 Build 20161019 is ready to be presented to the TSC for approval. Blocking bugs have been resolved and test issues have been signed off as OKAY. (anipbu, 17:24:53)
    2. https://wiki.opendaylight.org/view/Simultaneous_Release/Beryllium/SR4/Status <--- Status Page (anipbu, 17:25:10)
    3. https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=1820514274 <--- All projects with test issues have signed off as OKAY to release (anipbu, 17:25:17)
    4. https://lists.opendaylight.org/pipermail/tsc/2016-October/006169.html thread from anipbu saying we're good to go (colindixon, 17:25:18)
    5. VOTE: Voted on "shall the TSC release Beryllium-SR4 based on the 20161019 build?" Results are, +1: 9 (colindixon, 17:26:13)
    6. AGREED: Beryllium-SR4 based on build 20161019 is released! (colindixon, 17:26:26)
    7. that is the last scheduled release of Beryllium, we will publish security updates until carbon is released (colindixon, 17:27:29)
    8. zxiiro says the release might happen later today rather than immediately after the TSC call as normal (colindixon, 17:27:49)

  5. carbon (colindixon, 17:27:58)
    1. https://lists.opendaylight.org/pipermail/release/2016-October/008490.html <--- We had Carbon Autorelease Failures in infrautils but it was fixed in https://git.opendaylight.org/gerrit/#/c/47059/ (anipbu, 17:28:05)
    2. https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-carbon/34/ <--- Autorelease Build Failures in DLUX - DLUX Static Web. (anipbu, 17:28:11)
    3. https://git.opendaylight.org/gerrit/#/c/47001/ <--- SFC project changing module artifact versions in maven and remove incorrect parent versions with potential impact to cardinal, faas, groupbasedpolicy, netvirt, nic. (anipbu, 17:28:45)
    4. https://lists.opendaylight.org/pipermail/release/2016-October/008491.html <--- Carbon M1 Offset 0 Status is due on today 10/20 (anipbu, 17:29:08)
    5. https://wiki.opendaylight.org/view/Simultaneous_Release:Carbon_Release_Plan <--- Kindly request TSC to formally approve the Carbon Simultaneous Release (anipbu, 17:29:20)
    6. VOTE: Voted on "shall the TSC approve the Carbon Release Plan as it stands here: https://wiki.opendaylight.org/view/Simultaneous_Release:Carbon_Release_Plan ?" Results are, +1: 8 (colindixon, 17:31:35)
    7. AGREED: the carbon release plan as it stands here is formally approved: https://wiki.opendaylight.org/view/Simultaneous_Release:Carbon_Release_Plan (colindixon, 17:31:48)
    8. colindixon strongly encourages relevant projects to work to include fast and/or phased elements into their per-project release plans where appropirate and staffable (colindixon, 17:32:18)

  6. infra (colindixon, 17:33:13)
    1. rackspace did finish expanding our cloud for us (last week), we haven't expanded the quota on anything to use the new resources (colindixon, 17:33:37)
    2. tykeal is planning to build out odlforge there now (colindixon, 17:33:45)
    3. we may have to have some outages to roll out a kernel security update at some point (colindixon, 17:34:32)
    4. we will be updating main nexus and jenkins/gerrit sandbox this weekend (small outges) (colindixon, 17:35:23)
    5. there are some issues with jenkins/gerrit integration based on the gerrit ssh API changing (colindixon, 17:35:42)
    6. committers have the ability to remove jenkins as a reviewer to remove a -1 verify from it, then after that jenkins won't be able to post to gerrit in the new version (one unresolve edge case with no workaround) (colindixon, 17:37:00)
    7. https://git.opendaylight.org/gerrit/46975 Integration-distro-test trigger fix (zxiiro, 17:38:23)
    8. https://git.opendaylight.org/gerrit/47139 distro-check patch for 60 minute timeout (zxiiro, 17:38:38)
    9. https://git.opendaylight.org/gerrit/47151 renaming console log name in logs server (zxiiro, 17:39:18)
    10. the last thing makes everything but the domain part the same for logs and jenkins servers (colindixon, 17:40:05)

  7. Claudio Gasparini as a committer on BGPCEP (colindixon, 17:40:43)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-October/006150.html (colindixon, 17:40:47)
    2. https://lists.opendaylight.org/pipermail/bgpcep-dev/2016-October/000796.html 3 of 5 current committers +1 (colindixon, 17:40:58)
    3. https://git.opendaylight.org/gerrit/#/q/owner:cgaspari%2540cisco.com+status:merged+project:bgpcep lots of patches (colindixon, 17:41:07)
    4. VOTE: Voted on "shall the TSC approve Claudio Gasparini as a committer on BGPCEP?" Results are, +1: 9 (colindixon, 17:42:29)
    5. AGREED: Claudio Gasparini is a committer on BGPCEP (colindixon, 17:42:44)

  8. Jakub Morvay as a committer on NETCONF (colindixon, 17:42:47)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-October/006165.html (colindixon, 17:42:48)
    2. https://lists.opendaylight.org/pipermail/netconf-dev/2016-October/000699.html 2 of 3 current committers +1 (colindixon, 17:42:49)
    3. https://git.opendaylight.org/gerrit/#/q/owner:jmorvay%2540cisco.com+project:netconf lots of patches (colindixon, 17:42:50)
    4. VOTE: Voted on "shall the TSC approve #topic Jakub Morvay as a committer on NETCONF?" Results are, +1: 8 (colindixon, 17:43:25)
    5. AGREED: Jakub Morvay is a committer on NETCONF (colindixon, 17:43:43)

  9. ODL Parent Graduation Review (colindixon, 17:43:55)
    1. https://wiki.opendaylight.org/view/ODL_Root_Parent:Mature_Graduation_Proposal (colindixon, 17:44:05)
    2. https://lists.opendaylight.org/pipermail/project-proposals/2016-October/000538.html requested on 10/6/2016 (colindixon, 17:44:14)
    3. dfarrell07 thanks skitt for doing this so that odlparent can be mature and thus have stable features, so other projects can have stable features (colindixon, 17:45:17)
    4. skitt adds that's what prompted this (colindixon, 17:45:24)
    5. with colindixon's help (skitt, 17:45:37)
    6. VOTE: Voted on "shall the TSC graduate odlparent to being a mature project?" Results are, +1: 8 (colindixon, 17:45:53)
    7. AGREED: odlparent is a mature project (colindixon, 17:46:05)
    8. ACTION: skitt to update the wiki with odlparent being mature (colindixon, 17:46:36)

  10. TSC elections (colindixon, 17:47:13)
    1. last week the TSC agreed to open the nominations, and about the dates, as well as when people need to have their things done to participate (colindixon, 17:48:05)
    2. phrobb didn't start the nomination process last week as was agreed (colindixon, 17:48:39)
    3. in essence, we have two choices, (a) assume that things are OK with a 1-week nomination period, or (b) push the elections out a week (colindixon, 17:48:57)
    4. rovarga notes that we have no self-nominations, which points to maybe people haven't been paying attention, colindixon notes that things tend to happen at the end, so that wouldn't have pointed (colindixon, 17:50:19)
    5. VOTE: Voted on "shall the TSC (1) shorten the effective noimation period to keep our current dates or (2) push our election dates out a week to keep the nomination period the same?" Results are (colindixon, 17:51:14)
    6. VOTE: Voted on "shall the TSC (1) shorten the effective noimation period to keep our current dates or (2) push our election dates out a week to keep the nomination period the same?" Results are, 2: 8 (colindixon, 17:52:10)
    7. AGREED: we will move the dates for the TSC election out a week to accomodate the fact that the call for self-nomination didn't go out last week (colindixon, 17:52:33)
    8. ACTION: phrobb will send mail to all people who are eligible to run that they are eligible as well as asking for self-nomination, dfarrell07 adds that we should use this opportunity to encourage people to get the categorizatoin right, clean up committer lists and hold PTL elections if need be (either new ones or first ones in the case of 6-8 projects) (colindixon, 17:55:18)
    9. dfarrell07 says that they way that works is that projects without PTLs wouldn't get votes (colindixon, 17:55:35)
    10. abhijitkumbhare asks if we should have a google sheet to track PTLs, categorization, (and maybe committers) to make gathering information easier (colindixon, 17:56:56)
    11. https://wiki.opendaylight.org/view/Project_list#Project_Types Wiki with projects sorted by types into RGs (dfarrell07, 17:57:03)
    12. ACTION: colindixon to change the project facts template to include a type field and then auto-populate lists based on that information (colindixon, 17:58:12)
    13. phrobb says that his plan was to let self-nominees declare their group when they fill this out here: https://wiki.opendaylight.org/view/TSC:2016_Election (which does part of the categorization) (colindixon, 17:59:00)
    14. in the next two weeks, we get all of the projects put in a the right types to make voters (not nominees correct) (colindixon, 17:59:26)
    15. the intented project type was reported in M0 status, we got responses from a lot, but not all projects for that (colindixon, 17:59:51)
    16. ACTION: anipbu to verify the project types match the M0 reports: https://wiki.opendaylight.org/view/Project_list#Project_Types (colindixon, 18:00:22)

  11. cookies (colindixon, 18:00:37)


Meeting ended at 18:00:52 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 get the OPNFV plugfest on our events page http://events.linuxfoundation.org/events/opnfv-plugfest/
  5. phrobb to work on getting us bettter control of the events page to make his life less painful
  6. phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better
  7. colindixon to add the agenda topic that networking-odl seems like it will be kicked out of ocata unless we improve our results on a scorecard
  8. colindixon start a thread on networking ODL in ocata on the neutron-dev list: https://review.openstack.org/#/c/383910/6/specs/stadium/ocata/networking-odl.rst
  9. ChrisPriceAB to open a maling list thread on release@ and tsc@ to talk about how to help projects that cross ODL/OPNFV deliver on promises in both places at the same time
  10. skitt to update the wiki with odlparent being mature
  11. phrobb will send mail to all people who are eligible to run that they are eligible as well as asking for self-nomination, dfarrell07 adds that we should use this opportunity to encourage people to get the categorizatoin right, clean up committer lists and hold PTL elections if need be (either new ones or first ones in the case of 6-8 projects)
  12. colindixon to change the project facts template to include a type field and then auto-populate lists based on that information
  13. anipbu to verify the project types match the M0 reports: https://wiki.opendaylight.org/view/Project_list#Project_Types


Action items, by person

  1. anipbu
    1. anipbu to verify the project types match the M0 reports: https://wiki.opendaylight.org/view/Project_list#Project_Types
  2. ChrisPriceAB
    1. ChrisPriceAB to open a maling list thread on release@ and tsc@ to talk about how to help projects that cross ODL/OPNFV deliver on promises in both places at the same time
  3. 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 add the agenda topic that networking-odl seems like it will be kicked out of ocata unless we improve our results on a scorecard
    5. colindixon start a thread on networking ODL in ocata on the neutron-dev list: https://review.openstack.org/#/c/383910/6/specs/stadium/ocata/networking-odl.rst
    6. colindixon to change the project facts template to include a type field and then auto-populate lists based on that information
  4. dfarrell07
    1. dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion
    2. phrobb will send mail to all people who are eligible to run that they are eligible as well as asking for self-nomination, dfarrell07 adds that we should use this opportunity to encourage people to get the categorizatoin right, clean up committer lists and hold PTL elections if need be (either new ones or first ones in the case of 6-8 projects)
  5. phrobb
    1. colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way
    2. phrobb to get the OPNFV plugfest on our events page http://events.linuxfoundation.org/events/opnfv-plugfest/
    3. phrobb to work on getting us bettter control of the events page to make his life less painful
    4. phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better
    5. phrobb will send mail to all people who are eligible to run that they are eligible as well as asking for self-nomination, dfarrell07 adds that we should use this opportunity to encourage people to get the categorizatoin right, clean up committer lists and hold PTL elections if need be (either new ones or first ones in the case of 6-8 projects)
  6. skitt
    1. skitt to update the wiki with odlparent being mature
  7. tykeal
    1. phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better
  8. 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 (116)
  2. odl_meetbot (36)
  3. ChrisPriceAB (16)
  4. anipbu (15)
  5. dfarrell07 (10)
  6. vishnoianil (10)
  7. abhijitkumbhare (9)
  8. skitt (8)
  9. edwarnicke (8)
  10. rovarga (7)
  11. gkaempfer (4)
  12. zxiiro (4)
  13. tykeal (3)
  14. vrpolak (1)
  15. phrobb (1)
  16. jamoluhrsen (1)


Generated by MeetBot 0.1.4.