< back to overview

ONOS Project: An Update

Aug 27, 2018
Timon Sloane
Timon Sloane About the author

Over the last 6 months, the community produced the 1.12 and the 1.13 releases of ONOS.

Over this time a significant service provider has taking ONOS 1.12 into production, and they are gearing up to upgrade to ONOS 1.13 in their test environments. This significant milestone demonstrates that ONOS has reached the required functional and operational maturity for significant production deployments.

Patches for 1.12.x and 1.13.x Minor Releases

As a result of this new production deployment, a number of significant improvements were made to the robustness of the ONOS core, Trellis and related apps. New remote administration tools were provided to aid in deployment and maintenance of the ONOS cluster. Diagnostic tools were added for collecting and analyzing ONOS log and a troubleshooting tool for Trellis was developed. Role Based Access Control (RBAC) for ONOS CLI was added and a customizable auto-layout for access network developed as an ONOS app.

New Features in 1.14 Release

Atomix and ONOS Core

Atomix, which is the basis of the ONOS distributed core, released version 3.0 & ONOS core has been upgraded to run Atomix cluster in a separate process. This represents the first step in disaggregating the ONOS process into multiple processes. Additionally, it serves to simplify the ISSU coordination by allowing the Atomix cluster to be upgraded first before any of the dependent ONOS functionality is updated; thus avoiding some lock-step upgrade issues.

Furthermore, because all of the ONOS distributed primitives are not specific to the SDN domain, they were moved out of ONOS and subsumed into the Atomix package. This not only reduces the the ONOS code-base, but it also benefits both the Atomix community and the ONOS community. Atomix users have access to useful functionality developed by ONOS and ONOS distributed code now has more developers working on it - albeit indirectly.

GUI

A significant initiative has been launched by the community to upgrade ONOS GUI from Angular 1.x to Angular 5/6. Work is on track to achieve feature parity by the end of the current release.

Bazel build

Two years ago, ONOS replaced Maven with Buck as a means to build the growing ONOS code-base faster and more efficiently. In the meantime, Bazel has been open-sourced and has surpassed Buck in terms of features and stability -- specifically builds are more deterministic, plugins (e.g. new build rules) can be defined without need to change and recompile the build system, and IDEs have better support for Bazel to aid developers. Given that both projects are descendants of Google’s Blaze build system and philosophy, we expect the transition from Buck to Bazel to be more seamless from developer perspective and will take less effort.

Unlike Buck-based projects, Bazel projects can be imported and shared across repositories, a critical feature that is currently blocking code-base disaggregation and hosting ONOS applications outside of the ONOS repo. This will also make it easier to share plugins and dependencies between ONOS and Stratum (currently using Bazel), as well as with countless other open source and proprietary projects (including Google, SpaceX, Lyft, and many others).

The goal is to build official release of 1.14 using Bazel and to deprecate Buck.

Community

The ONOS community has been active and has organized numerous meetups around the globe

  • In Korea, the ONOS and CORD community flourishes thanks to a working group and several meetups of the onos/cord + P4 working group
  • Asia also saw the first ONF community tour, with events spanning across Japan, Taiwan and Korea, all related to ONOS and CORD with also special attention to Stratum and P4
  • The first meetup in Indonesia was held with an introduction to ONF, our projects and a deep-dive into ONOS
  • Africa also saw its first meetup in Sudan with 70 attendees coming together to learn about ONF, ONOS and CORD along with a tutorial on how to create an ONOS application
  • Microsemi and Cork Institute of Technology organized a two-day ONF Community meetup in CORK. 50 attendees from various companies learned about the latest advancements in ONF’s projects from Service providers and other companies (BT, Huawei, Huber+Suhner)
  • A P4 workshop and a hands-on tutorial on ONOS were held in Italy
  • The second security and performance brigade meetup was held with participation from NOKIA, AIRBUS, LIP6, EMSE Sudria, DT highlighting their contributions and analysis
  • A two-day Open Networking Meetup was held in Darmstadt, where 70 people came together and discussed the future of open networking space with particular attention to ONFs new RDs and projects such as CORD, VOLTHA and P4. Europeon service providers also presented their work and highlighted their contributions to ONF projects.

Learn More

Click here to learn more about the ONOS project.

Share this post:
ABOUT THE AUTHOR Timon Sloane
Timon SloaneVP, Marketing & Ecosystem
Timon Sloane is the vice president of marketing and ecosystem of the Open Networking Foundation (ONF). He leads the organization’s efforts building an open source ecosystem, thus helping to enable broad transformation of the networking industry through the adoption open source business practices.

TAGS