Programmable NFV, Google SDN at ONS 2014
Jason Edelman rounded up what he deemed to be the most noteworthy conversations at the Open Networking Summit 2014 on his personal site. He points to Google's SDN strategy, Andromeda, and the work Google is doing with its network virtualization platform. Edelman also draws parallels between the Cisco vs. VMware feud for enterprise SDN and network virtualization, and the Google vs. Microsoft battle for the SDN-based cloud.
Edelman also points to programmable network functions virtualization (NFV), which was part of Google's talk at the conference, and he includes a summary of Big Switch's new moves, which includes the company embracing bare-metal switching.
Take a look at Edelman's full overview of ONS 2014 highlights.
How to set up overlays on Open vSwitch
Brent Salisbury posted another tutorial on his NetworkStatic site, focusing on setting up overlays using Open vSwitch. He writes that none of these overlay networks should be set up by hand, but if readers are looking to get a good understanding of Open vSwitch and overlays for proofing something before it's coded, this tutorial may be helpful. He warns that the tutorial isn't a good beginner how-to for OpenFlow or Open vSwitch, and he writes that these are things to understand thoroughly before attempting to develop overlay solutions.
Check out Salisbury's full tutorial on setting up overlays on Open vSwitch.
Clash of the cultures in SDN: Network engineers vs. developers
Both developers and network engineers need SDN skills, but they'll go about it differently. Network engineers are accustomed to seeking certifications, but developers play in code until they learn it. Network management consultant Lindsay Hill takes a hard look at the difference between these approaches. As the network continues to evolve, Hill writes that developers and engineers may be at odds. Engineers tend to view certifications as "badges of honor," while developers prefer code versus classes.
Hill takes a look at available SDN certifications, including Cisco's, as well as how sites like GitHub impact developers. He explains that when engineers and developers come together, there can be issues surrounding how each prefer to solve problems, how they operate in a business environment and how they validate technical experience. Hill ends his post by writing that he's unconvinced of effectiveness of certifications for SDN development, although mainstream network certifications may adopt SDN topics. In addition, he writes that he foresees only a few network engineers doing serious development work within SDN, while most will drive the tools from the graphical user interface.
Take a look at Hill's post describing the differences between engineers and coders within the SDN space.
Getting to know the value of SDN
On his EtherealMind blog, Greg Ferro takes a look at the business value and services associated with SDN. Major changes have occurred as a result of the new technology, like the quality of manufacturing and the increased volumes of network hardware. Today, a networking budget is spent on providing connectivity, such as WAN, LAN and the wireless of campus networks, but as the market moves more toward SDN, the business value of the network moves from connectivity to services.
In fact, value is going to be found within the applications that deliver business services, Ferro writes. All in all, SDN within networking is about finding visibility, mobility and operability in the software layer of the network -- this layer will, in turn, offer the business new ways to extract productivity and profits.
Check out Ferro's full post, which breaks down SDN services, value and commodities.