Earlier this month, I attended the first ever summit on OpenDaylight (ODL) project in Santa Clara, CA. This near sold out event was largely successful by many standards. It brought together a large number of great minds to the table to solve some of the toughest challenges the networking industry is facing around Software-defined Networking (SDN) and Network Function Virtualization (NFV). The group announced a first major step forward with the first open source software release called Hydrogen. The bulk of the credit goes to 154 contributors from Cisco, IBM, Ericsson, Red Hat, Citrix and others who wrote over a million lines of code in past ten months to make this happen.
The two-day summit was packed with a variety of sessions that were geared towards a diverse set of audience. The sessions varied from general topics to specific topics such as relevance of Open source software, NFV, LISP, standards, discussions on North and South bound APIs, developer tutorials for building applications & tool chain, using OpenStack with ODL, analytics, test automation, and a true story of SDN in production environment.
Of all these topics, here are the three important themes that stood out to me -
1. The importance of an Open Source, community initiative for SDN
The concept of Open Source software has been around since decades. It is fast catching up in the non-traditional realms of computer networking. For some, the concept of open source equates to free software. While this is partially true, I strongly believe that open=free is a misnomer. I have started to realize that open source and further, the collaborative initiatives like ODL is far beyond the notion of freeness. In my view, the most important thing that such an initiative does is to gather right minds to bring out bright ideas. The collective wisdom that emanates from such a collaborative initiative helps vendors develop a cohesive set of products that speaks a common language, and perhaps share certain fundamental design constructs to aid interoperability. At the same time, I believe that this collaboration helps to compress the infinite ways vendors can built products to a bounded, agreed upon set of behaviors and interfaces. Customers are real beneficiaries of such an open initiative due to this standardization and better product interoperability. As Vijay Pandey from IBM aptly said in one of his presentations, open source initiatives like ODL “promote innovation and raise the value bar.”
Cisco firmly believes in and supports such open source initiatives. Cisco is a platinum member of ODL project, as well as a Gold member of OpenStack Foundation. You can find more information about OpenStack at Cisco , and a rich set of Cisco Services to help you exploit and adopt OpenStack.
2. What and how much to Standardize (North and South bound APIs)
In the summit, there were several interesting debates on what to standardize and how much. With regards to how much, I am with Guru Parulkar’s mantra to “standardize as little as possible.”
One of the core capabilities that SDN brings to the table is the notion around exposing interfaces from control plane to the infrastructure layer (South Bound APIs or SBI) and to the application/business layer (North bound APIs or NBI). We talked about using common approach for design constructs above, and the APIs are central to the constructs. However, if we (are somehow able to) standardize every hook into the system, we are forcing the industry to take a “single” approach to solve the underlying problems. Additionally, I believe that such an approach will not only go against the very notion of openness, but will also hinder innovation and ability to provide unique experiences.
If we talk about SBI, we rightly need some standardized ways to abstract some of the infrastructure complexities. I learnt that ODL will include support for SDN open standards such as OpenFlow, VxLAN, PCEP etc. Similar to SBI, can we standardize the NBI’s as well?
Read More »
Tags: adoption challenges, APIs, Cisco, Cisco Services, consultative led, opendaylight, OpenStack, SDN, SDN controller
Written by Krishnan Subramaniam, Director (Migration Services practice), Cisco Services
According to repeat surveys by IDC, the bad news is that challenges of cloud – security, data privacy, System Integration/migration, and legal issues – have not changed in more than five years. The good news is that, finally, with Cisco’s cloud evolution announcement, we now have solutions.
Top challenges remain the same, but reported slightly less often
2013 IDC Services Group Survey: U.S. Professional Services Opportunities Related to Cloud Services, Doc #239862, March 2013, N = 421, IDC, 2012 Cloud Professional Services Survey N = 402, IDC, 2009 Cloud Professional Services Survey N = 364, Note: in 2009 Survey Legal was not offered as an option.
Cisco’s InterCloud portfolio helps to overcome some of the main technical challenges.
It is important to understand key features of InterCloud to understand how it helps tackle technical concerns. Cisco InterCloud:
- Provides a network bridge between the enterprise IT and service provider’s cloud over a secure path and creates a private network resembling the corporate network within the cloud provider’s space. In essence, the workload that will be migrated can retain its original IP address.
- Provides Read More »
Tags: cisco intercloud, Cisco Services, cloud, InterCloud, Service Provider
As cloud-enabled services transform IT departments everywhere, your path to success as an IT professional was made easier today with Cisco’s announcement to expand its cloud portfolio. With Cisco’s comprehensive cloud portfolio offerings, you can easily and securely combine workloads to manage cloud services across different clouds. By increasing your flexibility for strategic sourcing of cloud-enabled IT services, you can increase your influence as a trusted business partner to your stakeholders. And, as you take on these new strategic roles, Cisco and our channel partners can help you and your organization gain control of cloud services.
While defining and deploying a comprehensive cloud architecture presents tremendous opportunity for IT chiefs, this task is not without its challenges. Successful cloud implementation requires a cloud governance model fueled by strategic vision and a holistic approach that addresses all aspects of your data center and IT operations in the new application economy fueled by cloud.
Tags: ACI, application centric infrastructure, Cisco, Cisco Domain Ten, Cisco Services, cloud, Cloud Consumption, Hybrid Cloud, InterCloud, OpenStack
2013 was the year I started working on SDN -- specifically in the area of devising professional services for Cisco ONE and Application Centric Infrastructure, ACI. A few months ago, I used a compendium to summarize my Cisco Domain TenSM blogs. This was well received, so I thought it would be a good idea to wrap up the year with a summary of my 2013 journey into the SDN world, and in particular the adoption challenges I learned about along the way, some of which are illustrated in the diagram below.
SDN Adoption Challenges
Read More »
Tags: ACI, architectural approach, Cisco collaboration, Cisco Services, One Platform Kit, SDN, software defined network
The other week I attended the “Software Defined Networking 2013” conference in London. This is a UK-based event for the discussion of SDN, OpenFlow and Network Virtualisation Solutions from a strategic perspective. There were quite a few interesting perspective s I picked up at this conference. In particular, the conference for me reinforced the potential of SDN – but if you apply it to the wrong problem, you may not get the return you hope for!
Top of mind for me, then, coming out of this conference was a demo of “What SDN Can Do For You” from one of our competitors. At best, the phrase “using a sledge hammer to crack a nut” comes to mind.
The demo came from our friends in Palo Alto, who once (boldly but incorrectly!) predicted that “Cisco UCS would be dead a year after launch”. They gave a SDN-focused demo that, when I “peeled back the onion”, didn’t demonstrate a compelling SDN use case. Rather, it convinced me that if you have this particular problem as illustrated in their demo, you don’t need SDN: you need a new vendor!
Tags: ACI, application centric infrastructure, architectural approach, Cisco collaboration, Cisco Services, Cisco WebEx, jabber, Jabber Video, network virtualization, onePK, SDN, software defined network