This post is also available in: Japanese
This is the 3rd part in multi-part series of posts on the leading SDN Startups. If you missed the rest, you can find them here:
Part 1 – Introduction
Part 2 - Plexxi, Plumgrid, Pluribus and Vello
Part 4 - Big Switch, Contrail, Embrane and Lyatiss
Figure 11 – Midokura Architecture
Midokura offers an integrated SDN controller and network virtualization software under the name of MidoNet. MidoNet is part of an end-to-end solution that includes a virtual switch that sits on the hypervisor and communicates over the physical infrastructure via tunnels to edge gateways. Policies are implemented at the edge on a virtual topology and then dynamically reflected on the underlying infrastructure. MidoNet is distributed on multiple servers and can also interface other SDN controllers and 3rd party applications like OpenStack via its Open Northbound API.
It is worth noting that Midokura has been extremely active (and recognized) at OpenStack. Its offering also integrates with other cloud orchestration solutions such as CloudStack. While MidoNet focuses on virtual switches only, integration with other SDN controllers make the expansion to the physical infrastructure possible in the future.
Figure 12 – Pertino Architecture
Pertino provides a Network-As-A-Service offering where subscribers download an agent on their devices that sends traffic and information to Pertino’s virtual switches located at different cloud datacenter-based POPs that host the SDN controller. Network virtualization and other services from Pertino (and in the future their partners) are performed as an overlay to one or more service provider infrastructures as subscriber traffic flows end-to-end through the Pertino cloud solution. Subscribers can then benefit from improved network performance and programmability anywhere their devices are and add applications as needed.
It is worth noting that Pertino is not a traditional SDN vendor. They do not offer SDN equipment but a NaaS solution that leverages SDN technology. They also use their own cloud orchestration technology to manage their services, optimize their resources and provision and bill their subscribers.
Figure 13 – Pica8 Architecture
Pica8 offers a physical switch that can be used as a traditional switch (in IP Fabric mode), an OpenFlow switch (in SDN mode) or as a hybrid switch. The network OS is distributed between all the switches and a few servers that also host the management software and a 3rd party OpenFlow controller. The controller uses OpenFlow and, as a result, can interoperate with both physical and virtual switches. Pica8 includes Open vSwitch (OVS) as part of its offering. RYU is the open source controller used for its reference architecture but they also demonstrated interoperability with Floodlight and NOX.
In my opinion, one of Pica8’s strengths is to have a traditional networking offering that can progressively become SDN over time. Being one of the few start-ups using OpenFlow, Pica8 can virtualized both physical and virtual infrastructure as well switches from other vendors delivering significant openness in their architecture.
This is the 3rd part in multi-part series of posts on the leading SDN Startups. If you missed the rest, you can find them here:
Part 1 – Introduction
Part 2 - Plexxi, Plumgrid, Pluribus and Vello
Part 4 - Big Switch, Contrail, Embrane and Lyatiss
Checkout more from our Guest Bloggers:
- SDN And The Forgotten Data Plane – Is My Flow Equal To Your Flow? (5/11/2013)
- OpenDaylight Project: The Speed Promise By Kelly Herrell (5/10/2013)
- SDN: Software Defined Everything: Infrastructure Integration Will Never Be The Same (5/6/2013)
- A Taxonomy For SDN Solutions (5/4/2013)
- SDN: Are You Sure You Want Applications To Program The Network? (5/1/2013)
Guest Blogger Disclaimer:
The views, opinions and positions expressed within these guest posts are those of the author alone and do not represent those of SDNCentral.com and SDNCentral, LLC. The accuracy, completeness and validity of any statements made within this article are not guaranteed. We accept no liability for any errors, omissions or representations. The copyright of this content belongs to the author and any liability with regards to infringement of intellectual property rights remains with them.
NFV and SDN: What's the Difference?
Top 5 Highlights from Open Networking Summit – ONS 2013 Tutorial Day
Exclusive: Shining the Spotlight on OpenDaylight-What you MUST know about the...
SDN And The Forgotten Data Plane – Is My Flow Equal To Your Flow? 
Featured Post: OpenStack Networking--Operational Simplicity With Cisco Nexus...