Providing a comprehensive solution for global connectivity is still not a trivial task. As most global enterprises know, the scale both geographically and organizationally can kill almost any well engineered network design. Size and complexity aside, just designing for the next “XaaS” solution and cloud sprawl can greatly challenge most network engineers One approach to […]
The post Leveraging IXP Colocation as an Enterprise appeared first on Packet Pushers.
Providing a comprehensive solution for global connectivity is still not a trivial task. As most global enterprises know, the scale both geographically and organizationally can kill almost any well engineered network design. Size and complexity aside, just designing for the next “XaaS” solution and cloud sprawl can greatly challenge most network engineers One approach to […]
The post Leveraging IXP Colocation as an Enterprise appeared first on Packet Pushers.

Note: This article was originally published here.
Update:This post has been updated to account for some recent changes in the appliance configuration (support for up to 7 front ports). In my previous post I described my developer setup to work with OpenSwitch. At the end of my post I showed how to download the build system, and configure and build an ‘appliance’ image.
The appliance is a virtual machine image (in OVA format) that could be run on VirtualBox or VMware (on this articule I will focus on VirtualBox) and provides a software datapath (based in OVS right now, but P4 support it’s landing soon). All the rest of the OpenSwitch stack is the same that you will see in a real hardware, and obviously the software datapath has certain limitations and features not implemented.
Despite his limitations, the appliance is a really nice way to get your hands into OpenSwitch without having real hardware.
If you are using the development environment, you can find the appliance .ova file on the images directory after completing the build, but otherwise you can also download a periodic image from the project archives (keep in mind Continue reading
Kyrio hopes to attract telcos and other non-cable industry players.
SDN, Software-Defined Networking, the trending technology that some friends/colleagues of mine like to refer to it as “Still Does Nothing”. Let’s see if it does some thing. SDN has been a market hype for few years now. Out of laziness, I ignored it in the beginning then I had to catch up a bit later …
The post Software-Defined Networks .. A Primer appeared first on Networkers-online.com.
A mere 78 lines of code that even a manager can understand.

The post Worth Reading: Rolling the root appeared first on 'net work.
Telcos looking at virtualization can look to where it's been done before.