Coming Soon: Open Source Networking Days Australia Open Source Networking Day Australia is a one-day mini-summit hosted by Telstra and co-organized by LF Networking (LFN) and Aptira. This is the first time that LFN has brought an open source networking event to Australia and it will be a unique opportunity to connect and collaborate with […]
In our last post we looked at different general patterns of standards compliance in Open Network solutions. In this post we drill down another layer to look at interoperability at the Application Program Interface (API) level, which creates issues at a level beyond standards. As we’ve mentioned previously, network equipment has been focused on interface
Real-World Open Networking. Part 4 – Interoperability: Problems with API’s Read More »
In our last post we finished up a detailed examination of different aspects of Interoperability. In this post, we will analyse the different mindsets between traditional networking domains and software development domains, explain why there is often built-in dissonance. Whilst Open Network solutions require the integration of network and software components and practices, at the
Real-World Open Networking. Part 5: Dissonance between Networks and Software Domains Read More »
In our last post we unpacked Interoperability, including Open Standards. Continuing this theme, we will look at how solution developers implement standards compliance and the problems that arise. Mandating that vendors (and internal systems) comply with Open Standards is a strategy used by organisations to drive interoperability. The assumption is that Open Standards compliant components
Real-world Open Networking. Part 3 – Interoperability: Problems with Standards Read More »
In our last post we described the attributes of an Open Network Solution. In this post we unpack what surely is the “Holy Grail” of Open Networks: Interoperability. Interoperability is defined as: Bottom line, interoperability means that I can freely substitute components, i.e. If I have Component X in my Open Networking solution, then in
Real-world Open Networking. Part 2 – Interoperability: The Holy Grail Read More »
In our last post in this series, we completed our coverage of the third domain of Open Networking, that of Open Network Integration. To wrap up our overall Open Networking series, we begin a set of posts that address the practical reality of delivering Open Network solutions in the current marketplace, and particularly focusing on
Real World Open Networking. Part 1 – Unpacking Openness Read More »
Our Open Source Software Defined Networking (SDN) Controller comparison continues with Ryu. Ryu is a very different proposition to the other options being put forward. Although boasting a core set of programs that are run as a ‘platform’, Ryu is better thought of as a toolbox, with which SDN controller functionality can be built. Ryu
Comparison of Software Defined Networking (SDN) Controllers. Part 5: Ryu Read More »
The final Open Source Software Defined Networking (SDN) Controller to be compared in this series is Faucet. Built on top of Ryu, Faucet is a lightweight SDN Controller adding a critical northbound function for operations teams. Faucet is a compact open source OpenFlow controller, which enables network operators to run their networks the same way
Comparison of Software Defined Networking (SDN) Controllers. Part 6: Faucet Read More »
This final part of our Software Defined Networking (SDN) Controller comparison series includes an in-depth evaluation and product rating for each of the most popular Open Source SDN controllers in industry and academia including: the Open Network Operation System (ONOS), OpenDayLight (ODL), OpenKilda, Ryu and Faucet.It is important to understand the motivations behind the available
