...
| 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/28 | Cancelled due to lack of prepared topics |
| 2015/10/21 | |
| 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
|
| 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
Suggested Discussion Topics
The following topics have been proposed, but currently lack an owner. Proposed owners are shown in parentheses.
- Publishing events to external event bus, e.g. Kafka, RabitMQ (David & Madan?)
- Should any internal ONOS event be candidate for this?
- Consider correctness issues in distributed environments
- Branches for use cases (Brian?
- What will we create branches for?
- What is their lifecycle?
- Where should other supporting code go?
- Packet layer Bandwidth Enforcement (Ali or Jono?)
- Will likely require a protocol capable of configuration i.e. OVS-DB or NETCONF
- Moving docs from Wiki to version control - which parts? (Ayaka?)
Deprecated Topics
Modeling services in the ONOS network graphCan we provide more abstract graphs that contain higher level objects?How are new devices modeled?
Intent ModelingMoving docs from Wiki to version control - which partsHow 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