You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 54 Next »

About the team

The technical steering team is responsible for all technical decisions in the project. They are responsible for the content and structure of the code base and for all technical priorities with respect to the code base. The ONOS chief architect is the team lead of the technical steering team. 

Who's in the team

 The following folks are in the team for 2015:

Contact Information

Drop the technical steering team an email if you have a technical or architectural topic to discuss or get guidance for.  The email archive is available for browsing and review of past conversations.

Contributors who wish to collaborate on medium to large feature submissions, are encouraged to follow the suggested process outlined on the Contributing to the ONOS Codebase page.

Recurring Meetings

The team will be meeting every week, 15:00-16:00 PST via Google hang-outs and Slack #tech-steering channel. The recurring meetings along with their proposed agendas and resulting meeting minutes will be published below (in reverse chronological order):

Standing Agenda Items:

  • Community Acknowledgements (2 minutes) – Please feel free to update the wiki in advance with details about who you would like to acknowledge and why

Specific Discussion Topics:

Date

Agenda

???
  • Overview of ONOSFW, an integration of ONOS into OPNFV (Jiangchuncheng)
2015/11/18
  • Federated network control with ONOS (Madan)
2015/11/11
  • Presentation of scalable DPI engine mechanism for ONOS for both on-platform and off-platform DPI applications (Taesang Choi & Sangsik Yoon)
  • (Backup Topic) Informal discussion of strategy for off-platform ONOS applications (Thomas & Brian)
2015/11/04
2015/10/28Cancelled due to lack of prepared topics
2015/10/21

  • Discuss various aspects of using NETCONF/YANG in the context of ONOS (Peter Lee from ClearPath, Larry, et al.)

    • both for consuming SB-oriented device configuration models

    • and for exposing NB-oriented network-wide configuration models

2015/10/14
2015/10/07
  • Topology models, BGP-LS provider and related GUI enhancement suggestions (Satish K.)
2015/09/30
2015/06/24
  • Hardening & Refining Distributed primitives (Brian)
  • Network Virtualization strategy (Thomas)
2015/04/29
  • Driver framework overview (Thomas)
2015/04/15
  • How many releases back should ONOS be supported? Now and in future.
    • Current decision is to support 6 months back (current and previous release) for bugs and 1 year back for security fixes
  • What should be the policy & process for deprecating Java APIs?
    • Deprecate in one release, remove in the next?
  • Nursery core & API to allow incubation and separability
    • Use @Beta annotation
2015/04/01
  • Table Pipeline API & drivers (Ali)
  • Overview of distributed application subsystem (Thomas)
  • Overview of distributed configuration subsystem (Thomas)
  • Call for re-write of sample applications using intent subsystem
  • Open discussion on future topics
2015/02/18
  • Axing the trivial stores
    • The trivial stores are no longer useful since the distributed stores have been completely functional for a single instance.
  • Performance testing scenarios
    • Flow system tests varying amount of work while varying the amount of communication.
  • Bundle karaf with ONOS?
    • This would make installation easier.
  • Improved Support for multi-tables.
    • Provide a sort of SelectorService which would return a "pipeline template" for the device the user wants to install a flow on.
2015/02/04
  • Tunnels or Virtual Links
    • There are a number of use cases and applications that want or need this abstraction; discuss some high level approaches.

Pending Topics

  • Branches for use cases
    • What will we create branches for?
    • What is their lifecycle?
    • Where should other supporting code go?
  • Modeling services in the ONOS network graph
    • Can we provide more abstract graphs that contain higher level objects?
    • How are new devices modeled?
  • Intent Modeling
    • How should new intent types be introduced into the framework?
  • Packet layer Bandwidth Enforcement
    • Will likely require a protocol capable of configuration i.e. OVS-DB or NETCONF
  • Moving docs from Wiki to version control - which parts?

 

  • No labels