In my first SDN blog, I asserted that “Services” -- that is technical support, professional and consultancy services -- are the missing “S” in the SDN debate. I’d now like to apply our Cisco Domain TenSM framework “in anger” to examine in more detail the impacts that SDN may have on your IT services and operations. While come of our competitors will only talk about the network switches and new device protocols, l’ll show how it’s not just the network switches that you should be concerned with: your SDN and Cisco ONE journey could involve impacts across multiple “domains”.
As I bogged about Cisco Domain Ten this past year, I’ve positioned it as a mechanism to help you on your data center journey. Let me now extend that use -- SDN after all is more than just a data center technology play. My experience with Cisco Domain Ten over the past year has helped me realize that it is, in fact, an excellent framework for considering impacts to more general IT services, and not just to the data center . I’ll also illustrate my case with both service provider and enterprise/business/public sector examples.
The following diagram summarizes the areas impacted -- let’s discuss each one.
SDN Impacts -- via Cisco Domain Ten
Read More »
Tags: architecture, Cisco Domain Ten, Cisco ONE, Cisco onePK, cisco_services, data center, SDN, SDN controller, software defined network
Cisco Live is here! It’s a great opportunity for you to discover some really exciting technology solutions at our Cisco ONE: Cisco Intelligent Programmable Network booth featuring a few of our latest innovations.
Onsite you will be able to see and ask your questions at live demos featuring applications and services developed with One Programmable Kit (onePK), Openflow and the eXtensible Network Controller. In addition, we have demos devoted to IPv6, routing, service discovery and network design simulation -- all things meant to make your network simpler and smarter.
There are also some great partner demos including our friends from SAP, Citrix, Glue Networks, Pramacom, Radware, and Starview who are showing some really cool apps that use the Cisco ONE APIs. Read More »
Tags: Cisco APIs, cisco live, Cisco ONE, Cisco onePK, EIGRP, onePK, OpenFlow, programmable networks, SDN
For those who are on the learning curve on various aspects of network programmability, open networking and SDN (like we are), I’d like to invite you to the third in a series of educational webicasts on these topics. Brought under the umbrella of the Cisco Open Network Environment, this particular webcast focuses on “An introduction to onePK”, and will be broadcast on April 9th, 2013 at 9 AM PST. You can register here.
The Cisco Open Network Environment is all about bringing the network closer to applications. One way of doing that is by exposing network devices to applications through a rich set of APIs, that can help tap into the intelligence inherent in the hardware and ASICs as well as in the network operating systems. This is what onePK is all about – it’s a single platform kit that will span all of Cisco’s network infrastructure portfolio across Enterprise and Service Provider, exposing them to applications in a homogenous way, allowing app developers to tap into the power of the open network.
Cisco announced its Open Network Environment or Cisco ONE strategy on June 2012 and has been in execution mode since then. onePK happens to be a key proofpoint of this cross-architectural strategy.
Join me on this webcast, as I host Ayman Sayed, SVP of Cisco’s Network Operating Systems Group as the lead Cisco expert on this topic. We will also be joined by two of the development partners that are working on onePK trials including Brendon Whateley, Principal Solution Architect at Starview Inc., and Kamil Knotek, Chielf of R&D at Pramacomm Prague spol s.r.o, as well as some new demos.
If you missed the last webcast on “An Introduction to OpenFlow” with David Ward, CTO, Cisco Engineering and Chief Architect, we had a turnout from 84 countries and over 120+ questions answered by our question managers in a one-hour period. You can watch a reply of the webcast here.
Read More »
Tags: Ayman Sayed, Brendon Whateley, Cisco ONE, Cisco onePK, Cisco Open Network Environment, David Ward, Kamil Knotek, lew tucker, OpenFlow, OpenStack, SDN, Shashi Kiran
So, we wrapped up our day with the Networking Field Day crew last week with a free form discussion on where we go next with SDN. To be honest, the session did not go quite as I envisioned, but, in retrospect, I would not changed anything. As Ethan Banks (of PacketPushers fame) noted in Twitter, this session was more about shooting the unicorns than letting them run free. It seems that if we are going to convert our SDN unicorns into SDN plough horses, we are going to shed a little blood. At the end of the day, the market will be served by frank conversations—we need to move beyond painting SDN acolytes as starry-eyed and SDN detractors as being heretical and reactionary.
In the interest of keeping the conversation going, here are some of the things I walked away with after the conversation on Wednesday (in no particular order):
Is Hardware Innovation is Over?
This industry has always been one big pendulum and, currently, the pendulum is firmly in the software camp. Today, many of the truly interesting things in networking are going on with software. While most would agree we are at an inflection point with programmability, there are no clear directions for the evolution of SDN. Certainly there are pieces in place like OpenFlow and OpenStack, but OF 1.3 in unlikely to be the zenith of OF evolution let alone SDN evolution—current technologies will continue to mature and new ones will inevitably emerge. More importantly, the “how we do things” and “what do want to accomplish” of SDN will most certainly continue to evolve and as long as that is the case, software will rule because it’s simply easier and faster to experiment with software. But, once some clear directions begin to emerge, I guarantee you the action will swing back towards the hardware because doing things in hardware tends to be faster and more efficient. I could point to Cisco examples of this, but instead look at what Intel, the poster child for general purpose processors, has done with VT extensions to support virtualization or QuickSync for video transcoding.
Is OpenFlow Ready for PrimeTime?
One of the more contentious points yesterday is if OpenFlow is production ready. I think it’s a flawed “do these jeans make me e look fat” kind of question. There are certainly folks out there using OF to handle production traffic—for example, some of the cool things Brent Salisbury is doing. So, it’s not a binary question, but more a matter of assessing scope and scale. The better question to ask is what is the operational and performance envelope of OpenFlow and how does that match my needs, priorities, and capabilities. The risk with any emerging technology is that, often, the only way you find the edge of the envelope is once you’re on the other side, usually with colorful and memorable results. Regardless, I don’t see this question existing in another year or so.
Read More »
Tags: Cisco ONE, Cisco onePK, Network Field Day, OpenFlow, OpenStack, SDN
By looking at the sheer amount of Breakouts and technical sessions here at Cisco Live London, it isn’t hard to understand why networks are becoming more and more complex. Networks are converging onto single infrastructures, more and more business processes are becoming more network centric and this translates into more functionality and more dependencies between functions and network layers, and thus more complexity. It becomes very hard for a single human being to understand these dependencies and layer interactions in order to do per-box configuration. Typically this problem is attempted to be ‘solved’ by moving some of these dependencies and layer interactions into a central place, but that just moves the problem. Wouldn’t it be cool to allow networks to become self-aware, such that they can learn from their neighboring nodes ? Read More »
Tags: Autonomic, Cisco ONE, Cisco onePK, Complexity