Page History

...

Date	Agenda
2015/02/04	Tunnels or Virtual Links There are a number of use cases and applications that want or need this abstraction. This topic would discuss some high level approaches.
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 multitables. Provide a sort of SelectorService which would return a "pipeline template" for the device the user wants to install a flow on.
2015/04/1	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/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/29

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

...