Have questions? Stuck? Please check our FAQ for some common questions and answers.

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

Compare with Current View Page History

« Previous Version 4 Next »


NOTE: This page is under construction and will be updated soon with the latest information about the ONOS roadmap.  For right now, this is just an outline to help start putting some structure in place for the page.


How to Read This Document

This roadmap is intended to provide information about what is being planned for upcoming ONOS releases and to provide guidance about how you can help us with planning for and delivering these items.  If you have any questions, comments or suggestions about this document, please feel free to post to the onos-dev mailing list.

How You Can Help

As an open source project, we welcome contributions from anyone in the community.  You are welcome to 'scratch your own itch' and contribute any new feature, bug fix or other contribution that you are interested in.  If you're excited about what we're planning for future releases and would like to help get these improvements out more quickly, you are also welcome to join our planning process and work on items on our roadmap.

Some major items on our roadmap that you can help with include:

 

  • Dynamic Configuration - provide support for configuring devices and network-wide services via YANG model-driven interactions where YANG models can be discovered or registered at run-time

  • Virtualization - enable use of ONOS as a network hypervisor through the creation of SDN capable virtual networks; networks whose connectivity can be programmed by applications as if they were physical SDN networks

  • GUI v2.0 - enhance the web UI to improve its usability on large-scale networks via region-based topology views with drill-down, context sensitive help, and global search

  • Deployments - enhance the existing Intent subsystem to enable ONOS to be deployed in networks around the world by providing the required layer 1-3 functionality

  • Intent v2.0 - re-design the intent framework to optimize scale and performance, enable conversational style feedback for error resolution on intent install, and add support for domain specific intent definitions and installation

  • P4 - support awareness of P4 programs including ability to deploy them, and facilitate applications to interact with the program-specific abstractions and controls

  • Disaggregation of ONOS code-base - separate the network-agnostic distributed applications platform from the network-aware core subsystems

  • In-Service Software Upgrade - design a mechanism for upgrading ONOS cluster without requiring downtime of control functionality where nodes can be upgraded one at a time

  • gRPC APIs - provide an efficient API to enable off-platform applications to have access to fine-grained control functionality and to allow off-platform applications to be written in languages other than Java

  • Federation - provide coordination mechanism for multiple ONOS clusters using either peer-to-peer or hierarchical arrangements to facilitate interactions between different administrative domains

  • Build & Package infrastructure - tools and processes for building ONOS and publishing the artifacts

  • OpenFlow 1.5 - upgrade libraries and providers to take advantage of the OF 1.5 protocol and updated libraries

  • LISP - continue adding support for LISP as SB protocol

  • Internationalization/Localization (I18N/L10N) - develop a framework for localization of the GUI and produce a set of localized message bundles

  • ECOMP/MANO/Open-O Integration - integrations with various orchestrator platforms

We also maintain a set of 'bounty bugs' in JIRA that are issues we want in upcoming releases but don't have owners assigned to them yet.  Please feel free to take one of those and we'll be happy to thank you with ONOS swag after completing those tasks.

Sprint Planning Meetings

Before each ONOS release there is a public meeting to discuss priorities to focus on for that release.  Everyone in the community is welcome to attend those meetings, to suggest priorities and to offer contributions for that release.  Keep an eye on the ONOS Meeting calendar for when these meetings will be held and for how to dial-in.  For reference, the planning documents from earlier releases are linked to here.

  • No labels