As we start off this New Year, how about including a resolution to improve application delivery? In Best Practices for Application Delivery in Virtualized Networks – Part I , we covered key application delivery challenges that have come up due to the complexities of managing the many types of applications that enterprises use today, and further complicated by data center consolidation and virtualization. We then covered some best practices, courtesy of Dr. Jim Metzler’s 2011 Application Service Delivery Handbook, which recommended taking a lifecycle approach to planning and managing application performance.
A key step to the lifecycle approach is to implement network and application optimization tools, such as WAN Optimization solutions and Application Delivery Controllers, including server load balancers. Of course, these solutions are not new to the market and already address many of the needs that exist with delivering enterprise applications in virtualized data centers -- namely, the need to ensure network reliability, availability and security for users accessing these applications. In this post, we will discuss a recent study by IDC, where IT decision makers across Europe and the US spoke out about their strategies for using server load balancers to deal with emerging challenges.
. What important attributes do you look for in your server load balancers?
To reduce network bandwidth, video is highly compressed. Any loss likely causes visible artifact for a varying amount of time. Watch this short video and see the impact of packet loss, jitter and delay on video.
Reading about the Bus funding crisis in California has ignited a number of discussions around how collaboration technologies could be used to soften some of the impact of losing the busing funds. We’ve talked here numerous times about how telepresence is being used to take students on field trips and connect them to new learning experiences, without the necessity of travel.
Field trips are often times students’ favorite memories from school. Who doesn’t love getting to leave the classroom for the day and explore what they’re learning hands-on? Unfortunately, there are a number of things that can prevent a good field trip experience in today’s educational environment – whether it’s the school’s rural location or the ever-decreasing school budgets. Read More »
Since the announcement of VXLAN last summer, there has been interest in the Open Source community for an open implementation of this. With the increasing number of Open Source cloud and virtualization technologies out there, where does VXLAN fit into this picture? I think one logical place for it to exist is inside OpenStack Quantum. As a service providing network connectivity between interface devices, this is a logical place for it to exist, especially as it pertains to disparite plugins.
But before I explain how VXLAN could plug into Quantum, some background may be good. Omar Sultan posted a great 3 part blog series on VXLAN (Part 1, Part 2, and Part 3). Reading this will give you a good, relevant background on VXLAN.
An Open Source implementation of VXLAN would require 2 pieces: A data path piece, to implement the protocol and framing format. And a control path piece, to handle orchestration of segment IDs and multicast addresses. For the data path piece, patches were posted to the Open vSwitch mailing list in October 2011, but so far have not been merged into either the Open vSwitch project’s git tree, nor the upstream Open vSwitch kernel code in the Linux tree. Once these patches make it into a public git repository, the data path portion of the equation is complete.
But what about the control path piece? One logical landing spot would be in OpenStack Quantum. Looking at version 1.0 of the Quantum API guide, we can begin to see how to add VXLAN support into Quantum. Quantum networks are created agnostic of their underlying segmentation technology. Currently, VLANs are used. Adding in VXLAN support would be as simple as adding in a type to “Create Network” call. Specifying VXLAN would allow Quantum to provision a Segment ID, and allocate a block of multicast addresses to use. Multiple hosts could still be added to multiple networks with a type of VXLAN. Quantum would work great for handling these types of tasks.
The place where this really begins to shine, however, is in the plugin architecture of Quantum. With Quantum handling the tasks of segment ID allocation, the plugins will have to handle the VXLAN protocol implementation for a network with type VXLAN. Vendors can now implement VXLAN in their plugins, and this buys end users the ability to have a heterogenous VXLAN environment out of the box.
Fresh Direct, an independent produce importer located in Vancouver, British Columbia, prides itself on customer service. A Cisco Small Business network makes employees more accessible to customers and to each other. This not only has improved the company’s service and efficiency but also help set them apart from their competition.