Slash Boxes

SoylentNews is people

posted by LaminatorX on Monday March 17 2014, @08:04AM   Printer-friendly
from the series-of-tubes dept.

evilviper writes:

"According to industry analysts, the reduced sales of traditional switching/routing heavyweights, during this traditionally active time, is due to widespread corporate investments and trials of software defined networking (SDN) equipment, which promises to improve routing efficiency, network management, and dramatically reduce hardware costs. Industry heavyweights like Google, Amazon, Facebook, and others are already heavily invested in OpenFlow and SDN, but it seems to be taking hold on a much wider scale, and not just in ultra-massive data centers."

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by SlimmPickens on Tuesday March 18 2014, @04:51AM

    by SlimmPickens (1056) on Tuesday March 18 2014, @04:51AM (#17931)

    Care to give an example?

    I assume you're asking about the hardware [] abstraction []. Think how much fancy mellanox hardware is found in datacenters.

    IMHO the problem with SDN is fully described in the following article []

    I'm not going to address all the points in the article however I point out that TFS itself is about how sales of traditional equipment is falling due to the widespread adoption of openflow. I think this [] does a good job of explaining what drives adoption:

    While no one in their right mind suggests completely replacing Ethernet and TCP/IP, anyone who's struggled to automate data center load management in today's virtualized data centers knows that current networking protocols present a challenge. For companies to make the most efficient use of their virtualized servers, they must move workloads around their data centers, but doing so implies moving network connectivity along with performance assurances, security, and monitoring requirements. Today, that's either impossible to do automatically, or the method for doing it is highly proprietary. And virtualization isn't the only challenge--as businesses add more applications to their networks, they need to address the unique needs of those apps at a policy level.

    So basically, SDN is here to stay because traditional networking doesn't handle the dynamic nature of todays datacentres. You can start playing with openflow right now because it's integrated into openqrm and probably all of the other provisioning magic sauce too.

    Also, I said above "We're talking about potentially not even using ethernet and TCP/IP." I want to clarify that I said that to try and explain what SDN is. While ethernet and to some extent IP are on the chopping block, the Linux TCP stack is going to be with us for a very long time.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 1) by mvar on Tuesday March 18 2014, @07:19PM

    by mvar (2539) on Tuesday March 18 2014, @07:19PM (#18212)

    I'm not familiar with mellanox hardware, i'll have to check it out. I was asking more for an actual example, but the links you provided will do. I have no doubt that SDN is here to stay,my problem lies with the way it is being pushed down our throats as the next big thing while the exact "nuts and bolts" of it remain a mystery for the vast majority of network professionals. Same thing happened with the "cloud" - last time i visited the openstack homepage it was a shitstorm of buzzwords and you'd have to dig for hours in order to find some technical document. As the article i posted says:

    We have trivialized SDN into being trivial. In an effort to make SDN news, to get URL clicks for publications and PR mentions for vendors, we’ve left every complicated issue out of our processes. We don’t write or talk about them, or even develop them. No application segmentation. No next-gen operations and automation. No new network services—we just use SDN to produce the same Level 2/3 services we had before it ever came along.