Tag Archives: Community

ONOS and CORD Projects Add Eight New Collaborators to a Burgeoning Global Network

ONOS® and CORD® Projects are thrilled to announce that Agema Systems, Aricent, Criterion Networks, Infosys, INSPIRE Group, OpenAirInterface Software Alliance, Quanta Cloud Technology and University of Science and Technology of China (USTC) have joined the projects as collaborators – signifying continued growth throughout the increasingly-vibrant open source networking community.

Agema, Infosys, INSPIRE Group and USTC have joined the ONOS Project, the community advancing the Open Source Network Operating System that provides scalability, high performance, high availability and the system abstractions appropriate for mission-critical networks. ONOS’ new collaborators will help vendors and service providers monetize a common infrastructure based on SDN and NFV by enabling rapid invention and deployment of new business models.

CORD Project, the community building an open source and fully-integrated solutions architecture designed to support connectivity and cloud-based services for residential, enterprise and mobile subscribers, warmly welcomes Aricent, Criterion Networks, OpenAirInterface Software Alliance and Quanta Cloud Technology. These new collaborators will help redefine the economics and agility of access networks across the globe.

“With project goals to enable service providers to build real Software Defined Networks and build an open reference implementation of CORD, expertise of a diverse collaborator network will be essential,” said Guru Parulkar, executive director of ONF and ON.Lab. “As these eight new collaborators embrace open source and align with our rapidly-growing community, the global adoption of SDN and NFV technologies will be accelerated like never before.”

Both ONOS and CORD Projects are growing vibrant, global ecosystems comprising a mix of start-ups, students and the world’s most well-known and respected technology, electronics, and telecommunications operators, vendors and service providers. The neutral, third-party governance, open to all, fuels community engagement and accelerates SDN innovation. The vendor-neutral projects invite technical contributions based on meritocracy. Whether an individual or an organization, all are encouraged to get involved with the growing open source collaborator community.

More about the new ONOS collaborators:

Agema: Agema Systems is the leading provider of Open Networking Solutions for data center, carrier, service provider and enterprise customers. The open platform high performance switching products are among the industry’s best available solutions for bare metal or pre-loaded, third-party, extensible modular Network Operating System (NOS). Agema provides customers with the freedom to implement software solutions that best fit their needs.

Infosys: Infosys is a global leader in technology services and consulting. We enable clients in more than 50 countries to create and execute strategies for their digital transformation. From engineering to application development, knowledge management and business process management, we help our clients find the right problems to solve, and to solve these effectively. Our team of 1,99,700+ innovators, across the globe, is differentiated by the imagination, knowledge and experience, across industries and technologies, that we bring to every project we undertake.

INSPIRE Group: The INSPIRE (INternet Security, Privacy, and Intelligence search) Group is a part of the Institute of Computer Science (ICS) of the Foundation for Research and Technology – Hellas (FORTH). Their research activities focus on the Inter-Domain level, exploiting the rapidly emerging SDN paradigm to counter chronic problems of the Internet, including unpredictable network availability, lack of Quality of Service guarantees and vulnerability to established and new types of Denial of Service (DoS) attacks. The mission of ICS-FORTH is to perform high quality basic and applied research, to promote education and training, and to contribute to the development of the Information Society, at a regional, national, and European level.

USTC: The University of Science and Technology of China (USTC) is a prominent university in China that was established by the Chinese Academy of Sciences (CAS) in 1958 as a strategic action by the Chinese government to meet China’s science and technology needs. CAS integrated its resources with USTC to educate top talent in cutting-edge, interdisciplinary science and technology disciplines.

More about the new CORD collaborators:

Aricent: Aricent is a global design and engineering company innovating for the digital era. With more than 12,000 talented designers and engineers and over 25 years of experience, we help the world’s leading companies solve their most important business and technology innovation challenges from Customer to Chip.

Criterion Networks: Criterion Networks is a network transformation and solution integration partner for SDN/NFV Solutions to meet the custom needs of Operators and Large Enterprises. Criterion provides an on-demand SDN/NFV solution orchestration platform, Criterion SDCloud for development, evaluation and learning needs accelerating the innovation and deployment roadmaps of its customers. 

OpenAirInterface: The OpenAirInterface Software Alliance (OSA) is a non-profit consortium to develop an ecosystem for open source software/hardware development for the core network (EPC) and access-network (EUTRAN) of 3GPP cellular networks. OSA is building on the initial work of EURECOM to create an open reference implementation for OpenAirInterface that offers a 5G Cellular Stack on commercial off-the-shelf (COTS) hardware.

Quanta Cloud Technology: Quanta Cloud Technology (QCT) is a global datacenter solution provider. It combines the efficiency of hyperscale hardware with infrastructure software from a diversity of industry leaders to solve next-generation datacenter design and operation challenges. QCT serves cloud service providers, telecoms and enterprises running public, hybrid and private clouds.

Additional Resources

Accelerating ONOS development with the brigade model

I’ve been working at ON.Lab for almost a year now and I’ve seen the community grow quickly during that time — there were around 30 organizations involved when I started and there are over 70 members contributing to ONOS and CORD today.


It is encouraging to see the community grow, but it also brings a challenge of how to coordinate a group that large to make sure we’re all working toward a shared goal. One way to address this is to communicate clearly about our vision for ONOS and invite people to work together on completing specific parts of that vision.

This is where the brigade model comes in — the idea is to create small teams around specific features that we want to ship in upcoming versions of ONOS. This can help us connect with other people in the community who are excited about that feature and it gives that group a framework for working together.

Code for America has been successfully using brigades to build new tools that help with local civic issues all across the country. There are many best practices we can take from that experience to help us get moving quickly with this model in our community. If you’ve been involved in a Code for America brigade, we’d be very interested to hear your thoughts.

For next steps, we’re starting to get brigades formed around a few key ONOS features — dynamic configuration, a new intent framework, SDN-IP and VPLS, and virtualization. We’ll share more details about each brigade soon and we encourage you to share thoughts and suggestions about the model and the specific brigades we’re starting with. Join the discussion about this on the onos-dev list.

Community Blog Series: KISTI/KREONET with KREONET-S

KREONET-S Deployment (left) and Team members Ki-Hyun Kim and Tae-Wook Song (right), presenting “Powered by ONOS” technology onsite Open Networking Summit 2016 and KREONET Daejeon Center at KISTI.

KREONET (Korea Research Environment Open NETwork) is a national research and education network with a high performance network infrastructure that extends R&D resources to about 200 key R&D organizations across the industrial, academic, and corporate sectors. KREONET has been managed and operated by KISTI (Korea Institute of Science and Technology Information) since 1988. KISTI works to maximize the efficiency of science and technology R&D. Both of the nonprofits are Collaborator members of the ONOS project, building ONOS-based software defined networking applications.

We had the pleasure of chatting with Dongkyun Kim, Principal Researcher at KISTI, about his involvement in the ONOS Project:

Tell us about yourself and your participation in the ONOS Project.
As the Principal Researcher at KISTI, I’m responsible for the development and deployment of KREONET-S, the new SDN network on KREONET. KREONET-S builds hardware and software SDN network devices and distributed ONOS-based controls on top of the network infrastructure. Most importantly, our project centers on developing new SDN/ONOS applications and network services to drive the softwarization of KREONET infrastructure.

Why did you join the ONOS Project?
When it comes to SDN, guaranteed reliability of the controller or network operating system is crucial; that’s why KREONET chose ONOS as our controller platform. Through this partnership, we can provide reliable network operations for KREONET-S and guarantee
our clients the SDN network and service stability they need.

We benefit from ONOS Project’s collaborative open source approach. We leverage the hardware and software infrastructure support for streamlining development of new applications and services, like high performance, advanced security, virtualized network, programmable environment, and get value from the high level networking services and network orchestration based on virtual networks.

The ONOS platform is impressive technology, and ON.Lab is one of the most transparent communities available in open source networking. The project is succeeding in building out SDN ecosystems, such as CORD, with high availability, scalability and performance for Service Providers. I predict CORD will be the next level of network centers, and it will certainly play a major role in our upcoming initiatives as the next principal component of KREONET-S.

What contributions are KREONET currently making to the ONOS project?
KREONET is developing unique ONOS-based use cases on the application side with several partners here in Korea, including prototype applications called virtual dedicated network (VDN) and User-oriented Visibility (UoV). VDN/UoV has been deployed to provide virtual network integrations for advanced research on KREONET. We’re currently working on extended functionalities for VDN/UoV and hope to develop more for SDN-IP and packet optical solutions as part of our use cases in the near future.

The ONOS-based KREONET-S Project will be a pioneer for production SD-WAN services in Korea. We’ve recently made immense traction furthering Goldeneye deployment on KREONET-S.

  • Newly released version of ONOS now runs on KREONET-S for 24 network devices, including four core and edge network devices in Daejeon and Seoul, 192 unidirectional links, and 30-35 end-hosts under the control of seven-node ONOS cluster.
  • There are two cities enabled with ONOS in Korea and this summer more locations will be softwarized throughout Korea and USA, starting with Busan, Korea and Chicago, IL. The new long-distance SDN network between Korea and USA (about 10,500km distance and 160-170ms RTT) will be used for international SD-WAN extensions (via StarLight in Chicago) and we have some useful experiments underway for long-distance ONOS distributed controls and virtual network expansion on inter-cluster SDNs.
  • Recent KREONET packet-optical collaborations with ON.Lab, KISTI, and Bell Lab include setting up the communication channel between our collaborators, and research into the operations and configurations environment on KREONET and KREONET-S based on Nokia (Alcatel-Lucent) PSS-32/PSS-36 optical network devices (up to 17 locations in Korea).
  • We launched the KREONET-S website, www.kreonet-s.net, to deliver specific information about the KREONET-S project and ONOS deployment, while showing the sustainability of KREONET-S network in particular. The new website is connected inside SDN domain of KREONET-S, and accessible to the general public.

How will the work of the ONOS Project impact the industry in the short term? In the long term?
Although KREONET and KREONET-S are based on non-profit & special purpose network demands and research purposes, I believe the expected use cases deployed and used for our network community will give some good impacts to the industry. In the short term, the proven effectiveness of ONOS distributed controls is going to ease Service Providers’ concerns about SDN sustainability. Plus, I expect that successful and reliable services derived from the ONOS distributed control environment (e.g., VDN/UoV services) will help Service Providers feel comfortable deploying similar but singular value-added SDN/NFV services with their own innovative business models in the long run.

Announcing the ONOS Easter Egg Hunt


For Easter this year, join us for a hunt through the ONOS source code for easter eggs. We’ve hidden some fun features in the code and if you find them you’ll be able to win prizes, recognition and bragging rights.

You have two ways to enter before the hunt is over at the end of Easter, March 27, 2016:

  • Use the #ONOSEasterEgg hashtag to tweet a screenshot showing us what you found
  • Email ee@onlab.us with a description of how the easter egg was implemented and how to invoke it

For prizes, we’ll send out ONOS shirts to 10 people randomly selected who tweet a screenshot and we’ll award an ONOS swag pack to the person who emails us with the most complete description of the easter egg feature.

To help with the hunt, we’ll also be sharing daily hints. Follow the @ONLAB_ONOS Twitter account or check back here each day.

Daily Hints:

  • March 22 Hint: What are you LOOKING at?
  • March 23 Hint: Maybe TRIE harder?
  • March 24 Hint: FOOd for thought?
  • March 25 Hint: SHIFT your thinking!
  • March 26 Hint: RELEASE the fowl!
  • March 27 Hint: Discover the KEY combination

Congratulations to the people who found the easter egg and posted their answer:

Next Community Steering Team Meeting on March 10 at 8 AM Pacific

The next Community Steering Team meeting is planned for this Thursday, March 10, at 8 AM Pacific. Please join us if you can—the dial-in information is on the CST wiki page.

I realize that many people will be busy preparing for ONS, so we’ll record the video so people can watch afterward if they can’t make it. I also know that this time doesn’t work well for everyone, so we’re open to changing it if people want to propose alternatives.

The first CST meeting covered some high-level topics such as the scope and role of this group. Now that we’ve discussed that, at this meeting we’re ready to get into specifics about how to strengthen and grow the ONOS community. The agenda for tomorrow’s call includes:

  • Who do we need to invite so that this group represents the community (for instance, more service provider participation)?
  • Discussion about the ONOS Ambassadors pilot and its role in regional community building and a plan for next steps
  • What questions we want to include in a community survey?
  • What community metrics do we have now and what additional metrics do we need (for instance, retention rate for contributors)?
  • One of our first principles is learning opportunities – are there trainings we should be providing community (for instance, helping people prepare to become a module owner)?
  • Action: Fill in initial pass at project list and owners

Satish Karunanithi new ONOS Module Owner

We would like to announce that Satish Karunanithi has become an ONOS module owner. His initial areas of code ownership are as follows:

  • /protocols/bgp/.*
  • /protocols/ospf/.*
  • /protocols/pcep/.*

Satish has been providing good quality feedback in code reviews and has been very proactive on the mailing lists where he’s been giving helpful responses and guidance. We expect the list of code areas will grow beyond this initial list.

We’re excited that Satish has accepted this responsibility and we think this is a great example of how the new module owner system is enabling us to broaden participation in decision making to more members in the ONOS community.

If you have any questions about the code in these areas or are looking for feedback on patches for those areas, please feel free to reach out to him.

To learn more about the role of module owners in the community and to find out how you could become a module owner, visit the Module Owners wiki page.

Help ONOS on social media

We can use your help to get the word out to more people about what is happening in the ONOS community. Here are a few ways you can help:

  • Share what you’re doing with ONOS and use the #ONOSProject hashtag when posting on your social networks
  • Share more than technical information — social activity, like having a lunch with other ONOS community members, is great content to post too
  • Subscribe to our Twitter account and retweet posts that you think are interesting: https://twitter.com/onlab_onos
  • Like us on our new ON.Lab Facebook page: https://www.facebook.com/opennetworkinglab/

If you have other ideas for sharing ONOS news or any tips and tricks you’d like to share with us, please comment and let us know.

Vision of the ONOS Community in 2016

As we start the new year, I wanted to share some thoughts about the goals for the ONOS community in 2016 and get feedback on it. In 2015 we saw the community grow and we’re now at a point where we have a big opportunity to grow the community even more and to coordinate the community’s efforts to make ONOS successful.

One of the main measures of growth that I think is relevant is the level of interest people are showing in ONOS contribution information. The chart below shows traffic to the Contributing to ONOS page. A few months ago the level of interest was fairly low and then we made a few small tweaks on the site that increased traffic to the page. That was followed in mid-December by an even bigger bump when we launched the new home page that has a prominent link to learn about contributing. Traffic dipped over the holidays and is now up to 350 pageviews a week compared to 250 before the home page update.


People are showing us that they want to learn how to contribute and the goal this year should be to capture that interest and align people in the community so we’re all working together. To do this, the focus for the work I want to do to support the community this year is on addressing needs of partners and collaborators, expanding our internal capacity and building out infrastructure.

Partners and Collaborators

There are now over 40 partners and collaborators actively involved in the ONOS community and that’s another great measure of the level of interest in contributing. We need to make sure all of these organizations are able to be effective in the community—are they facing roadblocks or running into other problems that we can support them with?

I think we need to spend some time talking to our partners and collaborators and listening to their feedback to understand challenges they’re facing. In some cases this will be in person discussions. I think it can also help to do a community survey and gather input from a large group. Once we get a better understanding of any concerns, we can put plans in place to address them.

Internal capacity

This work is about having the processes to be able to operate effectively with a larger community. As more people get involved, we need to be able to recognize their efforts and delegate responsibilities to them. We’ve seen good results from an initial effort to do this with expanding code reviewer status.

We’re also looking at other things we can do here. For instance, last week at the TST meeting we proposed the idea of a Spring Cleaning Sprint that would let us devote time to putting things in place that would make it easier for others to participate. If you have ideas for ways to increase our capacity to work with a larger community, please share your ideas.


A growing community also causes challenges that need to be addressed with tools. For instance, with a small enough group you can keep track of everyone in your head, but as the group grows that becomes impossible. I think a community directory would help here and give people a way to learn who is involved and what they’re doing.

It also becomes difficult to keep track of news about a big community. Right now ONOS news is shared in different channels (Twitter, ONOS web site, YouTube, etc) and you need to watch each of those to catch everything. We’re working to integrate these channels, so you can catch all of the news in one spot. We’re also planning to streamline the ONOS site and wiki more to make sure that relevant information is as easy to find as possible.

Measuring Success

Increasing the level of interest in contributing is a great start, but that isn’t enough. Success will be measured by converting that interest into actual contributions and by keeping community members engaged and retaining their expertise in the community. It is that process of connecting people who want to contribute with real contribution opportunities that makes a successful community.

One way we can measure conversion is by looking at activity for starter bugs. These are tasks that are good for people who want to code for ONOS and are new to the community. Can we have more starter bugs fixed in Q2 than in Q1 by connecting the people who want to contribute to these good initial contribution opportunities?

We can then look at retention by seeing if people take on other coding tasks after completing their first starter bug. And this process applies to any contribution area—for example, we also want to build a documentation community so we can measure conversion and retention by looking at initial edits to the wiki and then ongoing activity with editing, updating and creating new documents.

Getting help

This is a lot of work and more than one community manager can do on their own. In order to bring more people in to help with these efforts, another thing I’d like to do early this year is set up a Community Steering Team. People who are interested in building the ONOS community can take part and help shape and drive efforts to grow and strengthen the community.

If you would be interested in taking part in a Community Steering Team, please reach out and let me know. And if you have any thoughts, comments or suggestions on the plans mentioned here, feel free to comment below or on the onos-discuss list.

Results from code reviewer pilot and next steps

In November, we announced a pilot program to increase the number of code reviewers in order to distribute responsibility and authority for code reviews more broadly in the community. Now that the pilot is over, I wanted to post a summary of what we learned and share plans for next steps.

We saw positive results in terms of code review rate and the load of code review. The people who were picked to take on this new responsibility did a good job of taking on the code review burden without sacrificing code quality. Even when a new module owner didn’t give a +2 review, they were doing more reviews and that helped other people who did give a +2 since they didn’t need to conduct a whole review from scratch. There were no major concerns, just opportunities for tweaking.

One tweak we saw is about how some globally relevant files (such as utility files or packages) don’t fit neatly into the way we initially organized modules. To address this, the TST will compile a list of those files and will submit them for feedback at an upcoming TST meeting. After that all module owners will have access to those. Keeping that list updated will be an ongoing process and more details about that will be shared soon.

We also saw a few ways that the Gerritt plug-in that manages this process should be improved. There are three Jira tickets open now that we’ll fix in Q1 before bringing additional reviewers in. Those are:

  • ONOS-3708: Enhance the submitter Gerrit plugin to separate module owner reviews from others
  • ONOS-3709: Enhance the submitter Gerrit plugin to assign 2 most specific module owners to a review
  • ONOS-3710: Enhance the submitter Gerrit plugin to generate an easy to read module owners page

As soon as those tweaks are addressed, we’ll continue with expanding the number of code reviewers. The TST and existing module owners will create a list of new people to invite and others may post to the TST list with nominations. In this new set of reviewers, we’ll invite at least one person who isn’t based in the Menlo Park office so that we can evaluate how this process works with community members in other locations.

Note that there aren’t yet specific criteria for becoming a code reviewer and more clearly defining that and creating a way to use metrics to identify good candidates is something we’ll work on for a future improvement. Ideally we’ll have a simple way to keep an eye out for people who are making good code contributions and good reviews so we can recognize them by inviting them to become a reviewer.

All of this information will soon be added to the wiki so it’s easy to find and reference. If anyone has any questions or comments about this, please feel free to comment on this post or join the discussion on the onos-discuss list.

ONOS home page update: final design and draft content

A couple of weeks ago we shared an early design for a new ONOS home page. Thanks to everyone who looked at that and shared their thoughts. The feedback was positive and we ended up making just a few small tweaks and the final design is below.


You can see in the design though that almost all of the text is placeholder copy. The next step is for us to figure out what exactly we want to say in each section. We’ve taken an initial pass at this and welcome any comments, questions or suggestions that you have. Below is the copy for each section.

Section 1

  • Headline: The Open Network Operating System (ONOS) project is building a better network
  • Paragraph: ONOS is bringing the promise of software defined networking (SDN) to service providers. Today’s network experience is outdated: little innovation, expensive operation, inflexible to change. We have a vision of what networking could be — more agile for mobile and data center applications with better economics for both users and providers. The ONOS project includes an open source SDN OS platform and compelling applications and use cases for service providers.
  • Button: Learn more about our mission

Section 2

  • Headline: Get involved and join us!
  • Paragraph: Leading service providers and vendors are funding and contributing to this effort. Whether you are an individual or an organization, come on-board and contribute to ONOS. There’s a lot happening with our growing community of partners, collaborators, and individuals that you can take part in. Help us with development, documentation, testing and more.
  • Button: Learn how to contribute to ONOS

Section 3

  • Headline: See what all the excitement is about! Try ONOS yourself.
  • Paragraph: ONOS is designed to stand up to the demands of service providers. As a cluster based operating system, it scales horizontally with network size and application demand. We have demonstrated industry leading performance with high application throughput and low event response latency. ONOS makes application programming much easier with rich northbound abstractions all while maintaining a network view for applications. A pluggable southbound interface allows control of both legacy and OpenFlow enabled devices.
  • Button: Download

Section 4

  • Headline: News & Announcements
  • Paragraph: Find out the latest information about announcements, events, the community and more.
  • Button: Follow #ONOSProject on Twitter

If you have any feedback on the text for the new home page, please feel free to add comments here or join the thread on the discuss list.