The document provides information about contributing to the open source SDN controller platform ONOS. It discusses how ONOS supports the transition from legacy to SDN networks through its scalability, performance, legacy device support, and other features. It encourages contributors to get involved through development, documentation, deployment, quality testing, or user experience work. Contact details are provided to join the community on Slack or mailing lists.

1. Contributing to ONOS
A guide by Dr. Ahmad Tajuddin bin Samsudin
Principal Researcher, Telekom Malaysia Research & Development
ONOS Ambassador, ON.Lab
2nd International Symposium on IOT & SDN/NFV
IoT-SDN/NFV, 31 July - 1 August, 2018
Cyberjaya
MALAYSIA

2. ONOS is building a better network
ONOS is the only SDN controller platform that
supports the transition from legacy networks to
SDN networks. This enables exciting new
capabilities, and disruptive deployment and
operational cost points for network operators.

3. How many SDN Controller
do you need to know to
interfaces the Network
Elements and Applications ?

4. Just one! Your own.

5. ONOS is the only open
source controller providing:
● Scalability
● High Performance
● Resiliency
● Legacy device support
● Next-Generation device support

6. Service Providers
require high availability
so that customers do not
experience network
downtime. ONOS was
architected from the start
to support the most
demanding operator
networks and has many
mechanisms to ensure
the network and its
connections are reliable.
ONOS has been
architected and built to
provide the highest
performance possible for
scaled network
operations. All releases
are held to this
performance, even while
adding many new
features. It supports
millions of application
intent requests at its
northbound interface,
while maintaining less
than 50 msec response
time (or better) for
network events – and
ONOS scales as needed
by adding new instances
when more control plane
capacity is needed.
Software modularity in
ONOS means that the
community has been
diligent about keeping
software functions well
defined and localized by
defining the right
abstractions and
interfaces. This has
many important benefits:
software that is easier to
read, test, and maintain.
Most importantly, it
allows partners to more
easily customize the
software.

7. SDN Components Model
SDN Application SDN Application
SDN northbound interface (NBI)
SDN Controller
Network
element
Network
element
Network
element
SDN southbound interface (SBI)
Application layer
Application plane
Control layer
Controller plane
Infrastructure layer
Data plane
Application-controller interface
Data-controller interface

8. ONOS Architecture

9. ONOS provides innovative northbound
abstractions that simplify the creation,
deployment, and operation of configuration,
management and control applications. The global
network view and application intent framework
are two examples. Applications can be easily
added to run “on-box” using native interfaces, or
“off-box” using REST and/or gRPC interfaces.
ONOS abstracts device characteristics so that the
core operating system does not have to be aware of
the particular protocol being used to control or
configure a device. ONOS has an extensive and
growing list of southbound support including P4,
OpenFlow, NETCONF, TL1, SNMP, CLI, BGP,
RESTCONF and more.
Northbound Abstractions
Ease of Network
Programming for
Automation & Control
Southbound
Abstractions
Easy Adaptation to
Legacy or New Devices
(Plug-in Architecture)

10. ONOS releases
Dec 2014
Avocet
Mar 2015
Blackbird
Jun 2016
Goldeneye
Feb 2017
Junco
2014 2015 2016 2017 2018
Jun 2015
Cardinal
Sep 2015
Drake
Dec 2015
Emu
Mar 2016
Falcon
Sep 2016
Hummingbird
Dec 2016
Ibis
Jun 2017
Kingfisher
Sep 2017
Loon
Dec 2017
Magpie
May 2018
Nightingale
Aug 2018
Owl

11. It’s no surprise Turk Telecom uses ONOS at 3 Turkish
government institutions where ONOS was configured for
multi-layer security at the user access, data, control and
application layers.
There are 18 officially
recognized ONOS in
Telecommunication industry
Source: onosproject.org

12. What people are saying
We are really excited to
introduce ONOS
innovations in to our
network fabric.
Rob Vietzke, Internet2
"It has become a key
issue for operators'
network to provide more
flexible and efficient
services. ONOS is a
platform that help
operators' network to
achieve the goal.
Yunjie Liu, Chinese
Academy of Engineering
TCS is pleased to
collaborate with ON.Lab
for the development of
ONOS, which is a
highly-scalable,
open-source
carrier-grade SDN
platform for multi-layer
networks.
V. Rajanna, TATA

13. ONOS Mission
● We are pursuing our vision of
what networking could be for
the public good
● We want to fix closed,
proprietary, complex, expensive
and inflexible networks
● We want networks that are
enabling innovation rather than
impeding innovation

14. How to contribute?
Make ONOS even better by
joining the community.
Join us on our mission!

15. Get Involved !
Development. Help build ONOS. Opportunities range from coding new features to
creating unit tests to bug fixes to making sample applications.
Documentation. Help create clear, concise documentation. Identify and add
whatever is missing and fix what is unclear or just plain wrong.
Deployment. Help us show the world that ONOS can work in real networks by
deploying ONOS and its applications on your network.
Quality. Help test ONOS – whether it’s the platform, sample applications or
documentation. Work with the Jira issues to ensure that they are clear, complete,
and the problems are reproducible.
User Experience and UI. Help ensure that the ONOS user experience is WOW -
not blah! Help create a unique look, feel, and experience for ONOS users.

16. Contact Information
Join us on Slack for real-time conversations
about ONOS. There is a general channel as
well as channels dedicated to specific topics.
Feel free to stop by and ask questions and
introduce yourself.
(https://slackin.onosproject.org/)
ONOS uses Google Groups for its
mailing lists. Unless otherwise noted,
they are all public - anyone can join,
follow and post.
onos-dev@onosproject.org (This list is for all ONOS development related discussions. If
you are a developer, you should be on this list)
collaborate@onosproject.org (This is a list used for organizations to submit collaboration
requests)

17. Membership
Partner (USD 500,000 per yr)
Collaborating-Innovator
(USD 1500-50000 per yr)
Innovator (USD 1500-50000 per yr)
Collaborator (FREE)
66Volunteers
ONF relies on and is
greatly appreciative
of the many
companies and
individuals who
contribute as
volunteers to our
work and mission.
The benefits of
Collaborator status
are granted to those
companies who first
made meaningful
contributions as
Volunteers, and who
now have identified
active engineering
resources working
on future
contributions.

18. More links
● Tutorial - Learn how to use ONOS and write applications
hands-on
(https://wiki.onosproject.org/display/ONOS/Tutorials)
● Guides - Read comprehensive guides to usage,
contribution, and architecture
(https://wiki.onosproject.org/display/ONOS/Guides)
● FAQ - Some common questions, answered
(https://wiki.onosproject.org/display/ONOS/FAQ)

19. License, Patents, and Contributor Agreement
ONOS® requires that contributions to the source code be released under the Apache 2.0
license. Code submitted to the project is required to have licensing information in the
header. This allows all submissions to be immediately available to all community members
under the Apache 2.0 license. ONOS also requires all submitters to agree to our Contributor
License Agreement (CLA), which is based on the Apache Software Foundation CLA.

20. Act Now !
https://onosproject.org/software/

21. TM R&D project - BoD
This project aims to leverage on
SDN capability to respond faster
towards customer bandwidth
requirement by providing the
flexibility of Bandwidth on
Demand (BoD) services, and
develop the Super Controller
components which will interact
with the related SDN Domain
Controller for the current network
installation. The customer can
schedule their bandwidth via a
BoD self-service portal using
calendaring and adjust it almost
instantly.
Scheduling, Resources,
Topology, Traffic Forecasting,....
Super Controller
centOS 7.2
ONOS 1.9.2
Java SDK 1.8
OSGI/ Apache Karaf 3.0.8
Eclipse
Buck & Maven

22. BoD impact
BoD Current practise
To modify QoS Immediately (within 2
minutes)
2 - 4 weeks
Checking bandwidth
availability
A few seconds 7 - 10 working days
Human intervention none At least 3 staff (sales, oss-bss
officer and network engineer)
Schedule Online Manual

23. BoD snapshot

24. BoD snapshot

25. BoD snapshot

26. SDN application

27. NBI @ ONOS

28. https://www.linkedin.com/in/ahmad-tajuddin-samsudin-b36a4137/
tajuddin@tmrnd.com.my
ahmad.tajuddin.bin.samsudin@gmail.com
+60133922351