Welcome back loyal viewers--this is an episode not to be missed. Engineers Unplugged is thrilled to welcome the Packet Pushers (@packetpushers), aka Greg Ferro (@etherealmind) and Ethan Banks (@ecbanks), as they discuss the underlay network. Yes, they’re showing us the underside and future of software defined networking.
Watch and see:
Welcome to Engineers Unplugged, where technologists talk to each other the way they know best, with a whiteboard. The rules are simple:
Episodes will publish weekly (or as close to it as we can manage)
At this year’s Hadoop Summit 2013, I presented on the “The Data Center and Hadoop” which built upon the past two years of testing the effects of Hadoop on the data center infrastructure. What makes Hadoop an important framework to study in the data center is that it contains a distributed system that combines both a distributed file system (HDFS) along with an execution framework (Map/Reduce). Further it builds upon itself and can provide other real-time or key/value stores(HBASE) along with many other possibilities. Each comes with its own set of infrastructure requirements that include throughput sensitive components along with latency sensitive components. Further in the Data Center, understanding how all these components work together is key to optimized deployments.
After studying many of these components and their effects, the very data we were alanyzing became a topic of a lot of our discussions. We combined application performance data, application logs, compute data AND network data to build a complete picture of what is happening in the data center.
With the advent of programmable networks (aka “Software Defined Networking”) it is not only important to make the network more application aware, but to also know where and how to analyze and make the right connections between the application and the network.
The Software Defined Networking (SDN) market evolution is having a major effect on networking job roles. New careers in IT are being built, focusing more on complex services and architectures rather than systems.
A recent survey by Cisco found that 71 percent of IT professionals intend on using SDN technology this year for a number of reasons, ranging from creating more programmable networks to simply reducing costs.
With these shifts in mind, new talent needs arise for IT professionals to accommodate evolving industry job roles.
Through the years, market transitions and technology disruptions have introduced IT knowledge gaps. Knowledge of networking fundamentals is no longer enough. Now, network professionals must understand networking systems with integrated security, wireless and voice capabilities. Cisco is leading the charge to provide direction and proper learning paths and resources to help address these challenges.
Listening to our community, we’ve determined new skills and job roles require a deeper understanding of deployments and troubleshooting of SDN architectures, as well as familiarity with SDN specific troubleshooting tools.
Just as we have been all along, Learning@Cisco is investing heavily in creating education and certifications programs to help our community evolve skills in order to continue to be the driving force of innovation in networking.
Watch below as I discuss Learning@Cisco’s efforts around SDN further.
If you are following the industry debates around Software Defined Networking (SDN), and are wondering “What really is SDN?”, “How the concepts of network virtualization and network programmability relate to SDN?” and perhaps more pertinently, “What can it do for my business” and “What network problems, indeed what IT problems, could it solve for my organization?” Well, don’t worry, you are in good company. Many customers looking at SDN are asking exactly these questions. When I blogged the other week on “The Missing ‘S’ in the SDN Debate”, I mentioned I would write again in more depth on the offerings from Cisco Services that would help you identify and benefit from SDN, the next evolution in the network. Today, then, I will share more information on the “Cisco Strategy and Analysis Services for Open Network Environment (ONE)”, which helps you gain an appreciation of what SDN is, what Cisco ONE is, and how it will help you. This service has been design specifically to answer the questions above for you, enabling you to optimize your IT strategy to greatest effect.
First, if you are attending CiscoLive in Orlando this coming week (week of 24 June 2013), please do look out for our “Design Centers” in the Data Center Cloud or Enterprise Networks areas of the Cisco booth. Here you can discuss your SDN and Cisco ONE questions with Cisco Services’ solutions architects, who have already been running strategy workshops with some of the early adopters of SDN and beta customers of Cisco ONE.
While I’ve been writing about Cisco Domain TenSM, I’ve been watching the SDN debate evolve in our industry, and I have to say, I’ve had my concerns. Don’t get me wrong – I personally see SDN as an important and very much required evolution (and note: ‘evolution’ – not ‘revolution’) of the networking industry. Being able to extract more value from the network – through, for example, a consistent and broad network API – I mean, who wouldn’t be excited about that! And especially for us in Cisco, with the largest by far networking installed base, the ability to uncover and exploit additional value for our customers from the network can only be a good thing!
As I say, over the past year or two, I’ve been perturbed about lack of discussion across the industry about the adoption and deployment challenges associated with SDN. There is – bluntly – too much “nirvana” or “marketing promises” out there, too much focus on the end result (e.g. “look at our use case, wow isn’t it great”) without discussion of steps required for a success, and too little discussion on the costs and challenges of the design and implementation of SDN solutions (e.g. “took us X man years + $M of investment”). It’s now time to change the discussion.
I was therefore delighted to see Jim Meltzer’s discussion of the issues he was seeing with his clients regarding SDN.