...
The team will be meeting every week, 15:00-16:00 PST via Google hang-outs and Slack #tech-steering channelHangouts on Air. The recurring meetings along with their proposed agendas and resulting meeting minutes will be published below (in reverse chronological order). Please see the ONOS calendar for for details on the how to join the meetings; each week's entry will be updated to convey the agenda and the Google hang-out linkslink.
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:
| 2016/02/17 | |
| 2016/02/10 | |
| 2015/01/27 | - ACINO presentation by Domenico Siracusa
|
| 2016/01/20 | |
| 2016/01/13 | |
| 2016/01/06 | - Discussion of Scrum process and use of Jira for providing visibility of progress. (Thomas)
|
| 2015/12/02 | |
| 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.
|
...