Jenkins is an open software tool, typically used for continuous integration in software development. Network or system changes can be treated in a similar way as code changes are: developed, tested and deployed. Test frameworks are coming to Network world (look at TODD) but are not popular yet. Even without unit tests we can still use developer tools like Jenkins […]
The post Jenkins as system job scheduler appeared first on Packet Pushers.
Jenkins is an open software tool, typically used for continuous integration in software development. Network or system changes can be treated in a similar way as code changes are: developed, tested and deployed. Test frameworks are coming to Network world (look at TODD) but are not popular yet. Even without unit tests we can still use developer tools like Jenkins […]
The post Jenkins as system job scheduler appeared first on Packet Pushers.
Check-out the new Disaster Recovery with NSX and SRM white paper that explains how Cross-VC NSX + VMware’s SRM offers an Enhanced Disaster Recovery (DR) solution and solves many of the challenges related to traditional DR solutions. This solution provides consistent logical networking and security across protected and recovery sites and faster recovery upon disaster scenarios. A summary and overview of the solution is provided below. Continue reading
ONUG's efforts show that network functions virtualization is applicable in the enterprise.
Like the 3-D puzzle, a virtual data center has intertwined components; one change can have big repercussions.
After covering the details of PCEP protocol in the BGP-LS and PCEP Deep Dive webinar Julian Lucek focused on how a controller would use PCEP to build MPLS TE paths across a network.
Oh, and don’t forget to explore the rest of the PCEP webinar and other SDN webinars after watching the video ;)
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