My photo

Bill St. Arnaud is a R&E Network and Green IT consultant who works with clients on a variety of subjects such as the next generation research and education and Internet networks. He also works with clients to develop practical solutions to reduce GHG emissions such as free broadband and dynamiccharging of eVehicles (See http://green-broadband.blogspot.com/) . View my complete profile

Tuesday, August 16, 2011

Open Flow in the real world: Carriers, clouds and follow the sun/wind networks

[It is exciting to see the concept of software controlled networks pioneered by CANARIE and CRC (UCLP) and other researchers such as Nick Mckeown at Stanford starting to gain momentum.

NEC should also be applauded for recognizing one of the important applications of Open Flow is follow the wind/sun networks where the network becomes a service under control of the user. A great presentation on this subject can be seen at the Future Internet Assembly in Budapest http://www.fi-budapest.eu/presentations/THU_Figuerola.pdf - Some excerpts from GigaOm article --BSA]
http://gigaom.com/cloud/openflow-in-the-real-world-carriers-clouds-and-more/?utm_source=social&utm_medium=twitter&utm_campaign=gigaom

The shift in networking and the hype around the OpenFlow protocol has led to a lot of confusion and overinflation of what OpenFlow can do. To get a bit more grounded in reality, I spoke with Don Clark, director of business development at NEC. NEC is a vendor deploying switches that use OpenFlow and a member of the Open Networking Foundation, the group spearheading the standardization of programmable networking.
Programmable networks are about agility and automation
For those just tuning in, OpenFlow is a protocol that allows a server to tell a switch what to do. It’s revolutionary only in that most switches historically have had their own proprietary software inside the switch telling it what to do. With OpenFlow and other programmable networking efforts, the decisions on how to build out a network and how to move packets is taken away from the box that actually moves the packets, and placed on a server. Now, someone can program the network independently of the gear inside the data center and the software on the switch.
It’s a simple idea with big implications for the industry. Clark says that since unveiling OpenFlow-enabled switches at Interop in May, NEC has learned a few things. Much like server consolidation was a large driver behind virtualization in the early years, software-defined networking will have its own impetus, and Clark believes that will be the ability to take the people and time out of network configuration. This allows folks operating clouds or platforms as a service to be more agile and respond to changes in their underlying infrastructure without changing and reconfiguring the network — resulting in fewer errors and improved speed.
“Right now the network equipment does a lot, but with OpenFlow it allows us to ask the hardware to do much less than it does today,” Clark says. “So moving it out from the equipment to the application stack, then the equipment’s job is simplified, and then on the controller side, networking becomes an application that is integrated with other business processes in the application stack.”
Clouds and carriers are low-hanging fruit
Today, Clark says most of NEC’s customers have a cloud or are building a cloud and want to offer the same kind of automation on the network side as they do on the cloud side. Clark says this can lead to faster provisioning (which is why most people are looking at programmable networks today) to follow-the-sun application models that could move applications from data center to data center based on reducing the amount of compute energy consumed. I’d love to see companies build out models and methods for helping companies like Google or Facebook send low-priority compute jobs to places where they could be completed using renewable energy.

[…]
So far, Clark says cloud providers are the most keen on using OpenFlow, but carriers represent another potentially huge market. The ONF counts Deutsche Telekom and Verizon on its executive board. Clark says the carriers are looking at adding OpenFlow to add functionality to their networks that today they get from several independent gear providers from Cisco and Juniper to Sandvine and Acme Packet, for example. “On the service provider side, we’ve seen a lot of unique apps that they are looking to deploy OpenFlow with,” Clark says. “A lot of the equipment carriers’ use is specialty equipment and they are excited about general purpose equipment that can handle specialty tasks.” This could disrupt the gear market.
The shift from selling switches to selling services
Because NEC has a business selling switches, it’s in a similar position to Cisco, Juniper or other vendors that might find their margins eroded by the emergence of what would become commodity switches. Clark isn’t as concerned about that, because NEC is busy building services, features and add-ons to its gear to accommodate the growth of OpenFlow and programmable networking. “We have a solutions practice and we’re very excited about what this networking model allows solutions providers to do,” Clark said. Namely, he’s trading high-margin switching for high-margin consulting, a tack that many in the open source world have tried. For example, look at what Rackspace is trying to do with OpenStack.
[…]
------
Green Internet Consultant. Practical solutions to reducing GHG emissions such as free broadband and electric highways. http://green-broadband.blogspot.com/
email: Bill.St.Arnaud@gmail.com
twitter: BillStArnaud
blog: http://billstarnaud.blogspot.com/
skype: Pocketpro