I worked with a quite few of the folks mentioned in this article when I was at the Open Networking Foundation, if anyone has questions.
I worked with a quite few of the folks mentioned in this article when I was at the Open Networking Foundation, if anyone has questions.
Is this technology used in the Internet core?
Or for de-bundling access networks and Internet service? Where I live, access networks use shared media (broadcast cable or GPON), segregating customers through device and protocol obscurity (no tcpdump) and maybe encryption (but without tcpdump, it is hard to tell). There's not much room for defining anything in software there.
And in data centers, how far does multi-tenancy go in practice? Can tenants push their own P4 programs into hyperscaler infrastructure?
I have no idea on the internet core, but I wouldn't be surprised if SDN capable gear is used there. One major performance benefits of SDN is lowering latency as the processing is happening in the switch silicon instead of a general purpose CPU, which seems very applicable to core switching.
For access networks, it has been used. VOLTHA (PON solution that is in production in various places, see other post) is being used for this, and also there is code for doing PPP encap/decap in P4, which allows access control and lower latency at line rate.
I'm not aware of anyone making the programmability parts of SDN available as a service. Usually most hyperscalers don't allow access to infra components - anything below the kernel or certain specific peripherals - and the underlying network would be one of these areas.
What's your view on how these people actually impacted the adoption of SDN in general?
> The investments NSF made in SDN over the past two decades have paid huge dividends.
In my view this seems a little overblown. The general idea of separation of control and data plane is just that - an idea. In practice, none of the early firms (like Nicira) have had any significant impact on what's happening in industry. Happy to be corrected if that's not accurate!
Depends where you are in the industry - the hyperscalers specifically have budget to afford a team to write P4 or other SDN code to manage their networks in production, so they're probably the biggest beneficiaries.
Lower end, it did make programmability more accessible to more folks and enabled whitebox switches to compete against entrenched players to a far greater extent than previously possible. Again, hyperscalers are going to be the main folks who buy this kind of gear and run SONiC or similar on it, so they can own the full switch software stack.
Many of the startup companies in the SDN space did have successful exits into larger players - for example Nicira into VMWare, Barefoot (Tofino switch chip) and Ananki (the ONF 4G/5G spinoff) into Intel. Also, much of the software was developed as open source, and is still out there to be used and built on.
What are some of the SDN open source software that is still useful today ? e.g. ODL, ONOS, Ryu, Floodlight
ONOS is being used with VOLTHA to enable PON networking in various locations (For example DT in Germany: https://convergedigest.com/deutsche-telekom-taps-open-source... , and IIRC it's also in production in Turkey).
There was a Comcast deployment to trial ONOS + whitebox switches a while ago.
The specific interplay of commercial deployment to open source vs commercial closed source in the networking space was better described in this post from Larry Peterson: https://systemsapproach.org/2022/02/28/venn-diagram-engineer...