Open Source NOS Demos At the OCP Summit

From sdxcentral: Facebook, Google, and Big Switch Networks at this week’s Open Compute Project (OCP) Summit will demonstrate three approaches to network operating systems all built with Open Network Linux (ONL) and all running on OCP switch hardware. All built with ONL is interesting to me. This is making the case ONL is simply an underlying Linux distribution. Why this wasn’t clear to me before is because of the poor messaging around all of these projects.

Open Source NOS: Response

My blog post on dNOS caused some interesting discussions to happen. My thinking was most people, be they open source people or networking people, don’t care about open source network operating systems. I have my theories as to why, and this Twitter thread contains my thoughts: I'm beginning to think my assumption most people don't care about open source network operating systems is valid. — Kyle Mestery (@mestery) March 14, 2018 It could also be that some of them are initially marketed as open source but with a long lead time until the code is released for public consumption.

dNOS: Another Open Source Network Operating System

This, from an AT&T press release at the end of January: AT&T* is working to provide the industry with a more open, flexible and cost-effective alternative to traditional integrated networking equipment. We intend to open source a project that we call the Disaggregated Network Operating System, or dNOS, hosted by The Linux Foundation. So far so good. Another network operating system, which is also open source, but I’m following along.

Stratum: An Open Source, Silicon Independent, Switch Operating System

Fun times continue in the land of Open Source Networking, as the ONF launches Stratum into the wild today. From the splash page of the project: Backed by a broad spectrum of organizations from across the networking industry, Stratum is building an open, minimal, production-ready distribution for white box switches. Stratum exposes a set of next-generation SDN interfaces including P4Runtime and OpenConfig, enabling interchangeability of forwarding devices and programmability of forwarding behaviors.

LibreSwitch: The OpenSwitch Fork Which Almost Made It

Some of you may be aware of OpenSwitch, the Linux Foundation’s open network operating system which describes itself as: * Linux-based network operating system (NOS) platform * Open source, vendor-neutral royalty-free model * Large ecosystem of industry leader support * Rapid onboarding of new platforms, protocols and applications * Viable option for open networking switch disaggregation While I was at HP, I was heavily involved in this project at the time.

Response: Open Source Open Standards Open Loop

Dave Ward recently wrote a blog post evaluating some thoughts around Open Standards and Open Source. It’s a great read, I encourage you to spend some time reading it and digesting it. There are many good points in there, I’ll highlight a few below with my own comments around his ideas here. About three years ago, at IETF 91, I gave a presentation on the state of SDOs like the IETF and Open Source networking communities and the industry trend of innovators (vendors, operators, entrepreneurs, developers) regardless of affiliation coming together to form developer communities in the open.

Scale Testing OVN

Recently, I’ve been spending an increasing amount of time building a virtual networking layer. Of course, I’m doing this using both Open vSwitch as well as OVN. I’ve been lucky enough to be a part of a few talks on OVN, so I won’t go into many details on OVN here. But I will say we’ve found it to be a great solution to solving virtual networking at scale. What I’d like to discuss here is some of the things we’re testing with regards to OVN at scale.

Subnetpools in Neutron

One of the most interesting new features in Neutron for the Kilo release is the addition of subnetpools to the API. This work was initially targeted to integrate nicely with pluggable IPAM. Unfortunately, this did not make it into Kilo and is targeted at Liberty. But even without pluggable IPAM as a consumer, the subnetpools addition is quite useful. Here’s an example of how you might use it. neutron net-create webapp