Life of a Network engineer, so fascinating… isn’t. As I network guy for years, I have realised the purpose of my job as to unbox the devices, upgrade the operating system, dump a configuration, hook on the cables and BOOM!!!.. The Network is up and running. Getting protocols up and running to deliver a consistent desired output is never ending story.
For years, Networking has been defined whose standards are defined by the Vendors. To get in to networking industry one has to be qualified to these so called certifications, which defines the standard of how networking qualified a guy is?
The biggest frustration was when these certified are hired over Master and Bachelors of Engineering, just because they can do ‘the job’.So the vendor defined certified guys, AKA God of Networking, because of their expertise to design, deploy and maintain single vendor specific platform…what an illusion!!
So my networking life of boxed approach has leaded me to complexity, dependency and monolithic thinking. For years, I thought that networking can never be innovative, it’s merely a few boxes connected together with protocols. I wished I could have made the Network, my own Way…
With the emerge of Software Defined Networking (SDN), this has been made possible. Even traditionally, the network was always defined by the means of Software, tied in to the boxes. With SDN, the logic of network definition has moved from boxes to abstracted controller/orchestration layers. So your network is no more tied to the devices, but it resides in the orchestration and one can change the hardware without losing its network profile.
The abstraction allows you to create networks dynamically, simulate and manage them in a simplistic way. Different vendors have come up with their SDN offerings of moving the intelligence to their controller/orchestrator, but still the lock-down persists, they have just moved the intelligence away from the devices (still keeping some on-the-box intelligence).
True open SDN can only be achieved by the means of an ecosystem. A network ecosystem is made up of best of the class packet forwarding hardware devices, controller(s) and a single layer of orchestration on the top.
Open Networking Foundation (ONF) is fostering the ecosystem thinking into the networking, by the means of SDN. Following the same approach and teamed up with our ecosystem partners, we will be showcasing real life SDN use cases in Open Networking Summit (ONS).
Demonstrations anchored by ECODE’s Network Services Orchestrator – DFX include:
HP Virtual Application Networks Controller (VAN)(http://www8.hp.com/us/en/networking/sdn), part of the ECODE Networks demonstration, is an SDN controller which provides a unified control point in an OpenFlow-enabled network, simplifying management, provisioning, and orchestration. The VAN SDN controller enables delivery of a new generation of application-based network services. It also provides open application program interfaces (APIs) to allow third-party developers to deliver innovative solutions to dynamically link business requirements to network infrastructure via either custom Java programs or general-purpose RESTful control interfaces. The VAN SDN controller is designed to operate in campus, data center, or service provider environments.
Pica8, Inc. (www.pica8.com) is a computer networking company headquartered in Palo Alto, California, USA. Pica8 is a vendor of operating systems on white box switches delivering software-defined networking (SDN) solutions for datacenter and cloud computing environments. The company’s products include Linux-based OpenFlow-supporting switching operating system PicOS, which is shipped either as standalone software or pre-loaded onto a range of 1/10/40 Gigabit Ethernet switches based on commoditized (“white box”) switches purchased from original design manufacturers (ODMs)
So please visit us in ONS, to experience the true power of SDN ecosystem, fuelled with innovation and endless possibilities of future.