Welcome back! Season 3 of Engineers Unplugged starts now. The premiere episode features Aaron Delp (@aarondelp) and Giles Sirett (@shapeblue) discussing the evolution from traditional to cloud workloads. What are the costs, the barriers to entry, and the reasons to change? Great discussion about the pros, cons, and the future. Watch and see:
Is that unicorn unwell? Thanks to Aaron Delp and Giles Sirett for taking the Unicorn Challenge on Engineers Unplugged.
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)
Submit ideas for episodes or volunteer to appear by Tweeting to @CommsNinja
Practice drawing unicorns
Applications, scale, resilience, software defined--the buzzwords are addressed and whiteboarded. What do you think? Agree or disagree with Aaron and Giles? Post a comment or join the conversation on Twitter. For more behind the scenes, join Engineers Unplugged on Facebook.
There’s been a lot of hype and speculation among industry watchers over Cisco’s position in the software-defined networking (SDN) trend. But as Padmasree Warrior, Cisco Chief Technology and Strategy Officer, explained during Cisco Partner Summit, SDN itself is a limited vision – customers aren’t gaining all that much by merely virtualizing network functions, for example.
“SDN addresses only a portion of the requirements our customers need,” explained Padma during her Day 2 General Session keynote at Partner Summit. It’s network programmability that should be the goal, she said, and Cisco and partners are the ones who will “clarify and explain to customers how the network of the future must transition to deliver better value.”
Padma joined the Cisco Channels social media team at Partner Summit to further clarify Cisco’s approach to network programmability. Let’s hear what she had to say:
Hi All! This is the second of what I’m hoping will be a weekly recap for Enterprise Networks.I say “hoping” because we’re just testing it out for now to see if people like it and if it adds value.
In this video I give a short summary of what happened this last week, then I have a fun interview with one of our premier ASIC designers here at Cisco, Guntram Wolski. When we were coming up with the concept for this weekly recap I wanted to find some of the smart, fun, technical people who have been involved with the creation of some of our coolest technologies. I really lucked out with Guntram -- as you’ll see, we had quite a fun* interview. Finally, we have an announcement on what we’ll be covering next week. After the jump, I’ve got all the links to things mentioned during the recap. Let me know what you think of this video and if there are other people you’d like me to interview.
Join me and my good friends Dan Frye and Jim Zemlin, Tuesday June 18th at 8:30 am Pacific, in a webcast as we discuss open source, networking, communities and projects, the opportunities entailed, the win-win-win model (or win-cube model as I like to call it, for the Authors, for the Community and for the Enterprise), and the recently announced Open Daylight project hosted by the Linux Foundation. Thank you, Shashi Kiran, for organizing a wonderful event and opportunity to talk about one of my favorite subjects, Open at Cisco.
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.