#opendaylight-meeting: tsc

Meeting started by dfarrell07 at 17:00:35 UTC (full logs).

Meeting summary

    1. edwarnicke (edwarnicke, 17:02:06)
    2. https://wiki.opendaylight.org/view/TSC:Main#Agenda agenda (dfarrell07, 17:02:16)
    3. gkaempfer (gkaempfer, 17:02:17)
    4. Chris Price (ChrisPriceAB, 17:02:30)
    5. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-03-10-18.00.html last week's meeting minutes (colindixon, 17:02:30)
    6. colindixon (colindixon, 17:02:33)
    7. dfarrell07 (dfarrell07, 17:02:40)
    8. ACTION: zxiiro will look more into maven central now that we're at least signing things (colindixon, 17:02:56)
    9. ACTION: colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron? (colindixon, 17:03:21)
    10. ACTION: colindixon to send mail about follow the two OpenFlow plugin implementations issue to figure out lessons learned and how to avoid similar problems in the future (colindixon, 17:03:39)

  2. TSC elections (colindixon, 17:04:26)
    1. phrobb_ says there have been no new developments (colindixon, 17:04:37)

  3. events (colindixon, 17:04:42)
    1. https://www.opendaylight.org/global-events (colindixon, 17:04:50)
    2. many of us are at ONS (colindixon, 17:04:57)
    3. LuisGomez (LuisGomez, 17:05:03)
    4. there are people going to the collab summit at the end of this month (colindixon, 17:05:09)
    5. there's an SDN event in Beijing, then there's OpenStack in Austin (colindixon, 17:05:38)
    6. ChrisPriceAB asks if we have any OpenDaylight/OPNFV collaboration at OpenStack (colindixon, 17:05:56)
    7. ACTION: ChrisPriceAB and phrobb_ have heather come and talk to the ODL community about how to have a bigger presense at OpenStack (colindixon, 17:06:20)

  4. boron (colindixon, 17:06:43)
    1. https://wiki.opendaylight.org/view/Weather#Unmerged_Patch_for_projects_to_test_OpenFlow_Plugin_default_design_to_Lithium projects can test with the new plugin, we're asking people to please test against it (colindixon, 17:07:22)
    2. boron M1 offset 1 milestones are due today (colindixon, 17:07:43)
    3. https://wiki.opendaylight.org/view/Weather#Bug_4527_Security_Groups_:_For_.22Other_Protocol.22_rule.2C_NeutronSecurityRule.getSecurityRuleProtocol.28.29_is_set_to_NULL neutron bug fixed (colindixon, 17:07:54)
    4. ChrisPriceAB asks if we're maintaining and deprecating all the external interfaces (APIs) or are we moving everything? (colindixon, 17:08:35)
    5. abhijitkumbhare says that they have some patches for maintaining the older interfaces as well, but they have lower performance, abhijitkumbhare says that internal people should move if they can (colindixon, 17:10:18)
    6. ChrisPriceAB notes (and colindixon endorses) that we should think about making sure we keep (even low-performance) versions of the old APIs, would be useful (colindixon, 17:11:48)
    7. abhijitkumbhare is asking to get initial tests back from things by next week (colindixon, 17:12:29)

  5. stable/beryllium (colindixon, 17:13:28)
    1. Beryllium-SR1 was supposed to happen today, but we're having test failures which are still under investigation (colindixon, 17:13:48)
    2. ChrisPriceAB has said we're still OK with providing something useful to OPNFV (colindixon, 17:14:13)
    3. https://wiki.opendaylight.org/view/Simultaneous_Release/Beryllium/SR1/Status#Status (anipbu, 17:14:25)
    4. zxiiro says that boron is also failing with the same issues (colindixon, 17:14:38)
    5. anipbu seems to think it might be a regression in YANG parser (colindixon, 17:14:48)
    6. colindixon asks if we have the right people engaged, anipbu says it was only this morning that we thought it might be a yang parser issue, we're waiting on a response (colindixon, 17:15:55)

  6. system integration and test (colindixon, 17:16:09)
    1. jamoluhrsen says that anipbu covered most of it above (colindixon, 17:16:28)
    2. jamoluhrsen says he'd like to a TWS on monday about possible changes to the process for integration and test in boron (colindixon, 17:16:52)
    3. Badrinath attending on behalf of Mohnish Anumala (Badrinath, 17:17:31)
    4. https://lists.opendaylight.org/pipermail/release/2016-March/005993.html Int/Test reqs for tests (dfarrell07, 17:17:32)

  7. infrastructure (colindixon, 17:17:39)
    1. private cloud is coming up, zxiiro is moving the sandbox into the private cloud (colindixon, 17:18:06)

  8. new committers on SXP (colindixon, 17:19:30)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-March/004876.html Promotion of Martin Sunal, Abdelilah Essiari on SXP (colindixon, 17:20:01)
    2. they have 2/2 votes from active committers (1 inactive) (dfarrell07, 17:20:07)
    3. they each have 5-7 merged commits, with non-trivial code (colindixon, 17:21:02)
    4. VOTE: Voted on "shall the TSC bless Martin Sunal, Abdelilah Essiar as committers on the SXP project?" Results are, +1: 7 (colindixon, 17:22:36)
    5. AGREED: Martin Sunal, Abdelilah Essiari are now committers on SXP (colindixon, 17:22:56)

  9. HoneyComb/BridgeDomain creation review (colindixon, 17:23:58)
    1. https://wiki.opendaylight.org/view/Project_Proposals:HoneyCombBridgeDomain (colindixon, 17:24:08)
    2. https://wiki.opendaylight.org/view/Project_Proposals:HoneyCombBridgeDomain#Project_overview slides are available for download here (colindixon, 17:24:53)
    3. https://lists.opendaylight.org/pipermail/project-proposals/2016-February/000401.html proposed on 2/11/2016 (colindixon, 17:25:19)
    4. this is largely a way to interact with the VPP dataplane in fd.io via the honeycomb local agent in fd.io (colindixon, 17:27:42)
    5. particularly to work on the bridge domain model/API provided by the honeycomb agent in fd.io (colindixon, 17:28:03)
    6. this project would then act as the orchestrator to manage multiple different honeycomb agents to provide virtual bridge domains across multiple VPP instances (colindixon, 17:29:10)
    7. phrobb_ notes that we'll have to do an IPR (colindixon, 17:33:20)
    8. colindixon asks if there are any trademark issues with names here, he suspects not and that it's all inside the LF, which probably helps (colindixon, 17:34:11)
    9. VOTE: Voted on "shall the TSC move the HoneyComb/BridgeDomain to incubation?" Results are, +1: 7 (colindixon, 17:35:24)
    10. AGREED: the HoneyComb/BridgeDomain is now an incubation project (colindixon, 17:35:33)
    11. VOTE: Voted on "shall the TSC allow the HoneyComb/BridgeDomain project to join the boron release at offset 1 despite this being 2 weeks late, technically?" Results are, +1: 6 (colindixon, 17:36:45)
    12. AGREED: the HoneyComb/BridgeDomain project will be able to join Boron at offset 1 (colindixon, 17:37:08)

  10. Infrastructure Utilities Project (colindixon, 17:37:30)
    1. https://wiki.opendaylight.org/view/Project_Proposals:Utilities (colindixon, 17:37:40)
    2. https://lists.opendaylight.org/pipermail/project-proposals/2016-March/000416.html proposed on 3/3/2016 (colindixon, 17:37:53)
    3. this is a project looking to provide utilities that the proposers who have found to be very useful (colindixon, 17:38:26)
    4. they will start with two utilities: counters and Seamless Async Calls Utility (colindixon, 17:39:10)
    5. https://wiki.opendaylight.org/view/Project_Proposals:Utilities#Description see here? (colindixon, 17:39:22)
    6. the counters stuff works with YANG and JMX to provide useful counters to expose to others and monitor them (colindixon, 17:40:30)
    7. a lot of work with rovarga has happened here (colindixon, 17:40:53)
    8. colindixon notes that personally this counter stuff looks cool (colindixon, 17:41:12)
    9. colindixon has two worries: (1) the scope is currently limited to just these two utilities, which seems likely not quite what they want, (2) in the past projects which exist solely to aggregate things for other projects have had trouble, e.g., toolkit and coretutorials (colindixon, 17:42:13)
    10. edwarnicke suggests to try to work in the normal development pattern, e.g., get involved in the archetypes (colindixon, 17:42:54)
    11. the response is that this is the scope for the boron release, and it could be adjust in later times, and colindixon thinks that's fine and we shouldn't block it because of that (colindixon, 17:46:10)
    12. phrobb_ asks if there's code that we need to do IPR on any incoming code (colindixon, 17:49:48)
    13. abhijitkumbhare asks if we should think about structuring this as a hierarchical project, e.g., infrautilities/counters, infrautilities/async, (colindixon, 17:50:42)
    14. abhijitkumbhare says maybe it would be group more things together (colindixon, 17:52:56)
    15. colindixon says he feels a bit like we have too many repos already (colindixon, 17:53:17)
    16. please note we *do* have mechanisms in our lifecycle for a hiearchy of projects (edwarnicke, 17:53:30)
    17. ChrisPriceAB notes we can fix that problem in the future and we don't have it yet (colindixon, 17:53:33)
    18. VOTE: Voted on "shall the TSC move The Infrastrucure Utilities Project to incubation?" Results are, +1: 7 (colindixon, 17:54:27)
    19. AGREED: The Infrastrucure Utilities Project is now an incubation project pending IPR (colindixon, 17:54:39)
    20. VOTE: Voted on "shall the TSC allow The Infrastrucure Utilities Project to join the Boron offset 0 assuming they quickly send your M1?" Results are, +1: 6 (colindixon, 17:55:53)
    21. AGREED: The Infrastrucure Utilities Project can join boron at offset 0 (colindixon, 17:56:05)
    22. LuisGomez has voted +1 every time so far for the record (colindixon, 17:56:41)

  11. remove inactive committers (colindixon, 17:57:39)
    1. our charter allows PTLs to forcibly remove inactive committers after an extended period of time, e.g., six months (colindixon, 17:58:16)
    2. https://www.opendaylight.org/tsc-charter < - "From the charter "A Committer who is disruptive, or has been inactive for an extended period (e.g., six or more months) may have his or her Committer status revoked by the project leads." (edwarnicke, 17:59:20)
    3. as long as projects make honest effort to contact inactive committers, the TSC feels this makes sense (colindixon, 17:59:25)
    4. as far a we're concerned projects can remove inactive committers, the TSC would like to be informed in these cases, and will handle disputes (colindixon, 18:02:28)
    5. AGREED: the TSC feels like this doesn't need a vote, PTLs can remove inactive committers at their discretion, but the TSC strongly encourages that people let the TSC know, and also notes the TSC can resolve any disputes of this (colindixon, 18:04:07)
    6. ACTION: colindixon to start a mail about best practices about keeping committer lists clean (colindixon, 18:04:49)

  12. cookies (colindixon, 18:04:59)


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

Action items

  1. zxiiro will look more into maven central now that we're at least signing things
  2. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
  3. colindixon to send mail about follow the two OpenFlow plugin implementations issue to figure out lessons learned and how to avoid similar problems in the future
  4. ChrisPriceAB and phrobb_ have heather come and talk to the ODL community about how to have a bigger presense at OpenStack
  5. colindixon to start a mail about best practices about keeping committer lists clean


Action items, by person

  1. ChrisPriceAB
    1. ChrisPriceAB and phrobb_ have heather come and talk to the ODL community about how to have a bigger presense at OpenStack
  2. colindixon
    1. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
    2. colindixon to send mail about follow the two OpenFlow plugin implementations issue to figure out lessons learned and how to avoid similar problems in the future
    3. colindixon to start a mail about best practices about keeping committer lists clean
  3. phrobb_
    1. ChrisPriceAB and phrobb_ have heather come and talk to the ODL community about how to have a bigger presense at OpenStack


People present (lines said)

  1. colindixon (103)
  2. odl_meetbot (30)
  3. dfarrell07 (18)
  4. edwarnicke (16)
  5. gkaempfer (7)
  6. tykeal (7)
  7. LuisGomez (7)
  8. ChrisPriceAB (6)
  9. Badrinath (6)
  10. abhijitkumbhare (4)
  11. phrobb_ (3)
  12. jamoluhrsen (1)
  13. anipbu (1)
  14. phrobb (0)


Generated by MeetBot 0.1.4.