Cisco Blogs


Cisco Blog > Data Center and Cloud

Engineers Unplugged S6|Ep4: onePK

August 13, 2014 at 10:36 pm PST

In this week’s episode of Engineers Unplugged, we welcome for the first time (and not the last) guest host Janel Kratky (follow her @jlkratky)! She’s hosting Jason Pfeifer and Glue Network’s Gregg Wyant as they discuss onePK and how to apply it to the real world. You don’t want to miss this one, it ends with a Glunicorn.

If you would like to become Internet Famous, and strut your unicorn talents, join us for our next filming session at VMworld 2014. Tweet me for details!

This is Engineers Unplugged, where technologists talk to each other the way they know best, with a whiteboard. The rules are simple:

  1. Episodes will publish weekly (or as close to it as we can manage)
  2. Subscribe to the podcast here: engineersunplugged.com
  3. Follow the #engineersunplugged conversation on Twitter
  4. Submit ideas for episodes or volunteer to appear by Tweeting to @CommsNinja
  5. Practice drawing unicorns

Join the behind the scenes by liking Engineers Unplugged on Facebook.

Tags: , , , , ,

What’s New with onePK?

CiscoLive San Francisco is coming up so I’ve been updating my session, the Hitchhiker’s Guide to onePK, with the latest information and some new insights.

One new thing is that Cisco onePK (One Platform Kit) is now Generally Available! Anyone can go to onepkdeveloper.com, download the SDK, and take C, Java or Python for a test drive. And I really mean anyone. You don’t even need a Babel fish. Haven’t programmed since freshman year in college? Don’t worry. If you can click on an icon in a Linux desktop and type the name of a script, then you can use onePK.

The great thing about this is that now we can all get real. As a network engineer, technologies aren’t real to me until I see them running on a network. After all, you can read about LSA types and adjacencies all day long, but until you’ve deployed OSPF, you don’t really know OSPF. The same is true for onePK. Read More »

Tags: , , , , , , , , , , ,

The First Open Source Project to Win the Interop Grand Prize…

… is none other than…  (drum roll, please!) … our one year old baby, OpenDaylight! My heartfelt congratulations go to the OpenDaylight committers and contributors, the open source collaborators who have poured their heart and soul into this wonderful project. This is indeed a remarkable event, considering the skepticism surrounding its start just about one year ago, in fact at Equinox. The Interop and OpenDaylight announcement captures the meaning of this accomplishment very well and on behalf of the OpenDaylight partners, I would like to thank the developers and users, to wish them continued success and strong adoption. Know that as long as core open source principles are alive and well our project will do well. Thank you, Interop panelists and conference attendees, and most of all, thank you Cisco colleagues, customers, and partners for building and embracing the base of what promises to be a star project. I am so proud of you!

Tags: , , , , , , , , , ,

OpenDaylight Unleashes Hydrogen to the Masses

The OpenDaylight Project today announced that its first open source software release Hydrogen is now available for download. As the first simultaneous code release cross-community it has contributions across fifty organizations and includes over one million lines of code. Yes. ODL > 1MLOC. For those of you interested that’s approximately two hundred and thirty man-years of work completed in less than twelve months.

It was around this time last year that the media started to pick up on a few rumors that something may be in the works with software-defined networking and controllers. I remember our first meeting at Citrix where the community started to collaborate on The OpenDaylight Project and come to common ground on how to start something this large. We had multiple companies and academics in the room and many ideas of where we wanted this project to go but there was one thing we had in common: the belief and vision to drive networking software innovation to the Internet in a new way and accelerate SDN in the open; transparently and with diverse community support. Each of us had notions of what we could bring to the table, from controller offerings to virtualization solutions, SDN protocol plugins and apps to solve IT problems. Over two days at Citrix we looked at things from a customer perspective, a developer perspective and ultimately and arguably the most important, a community perspective. From there The OpenDaylight Project emerged under the Linux Foundation. As I look back I want to applaud and thank the companies, partners, developers, community members and the Linux Foundation for driving such a large vision from concept to reality in less than twelve months, which is an incredible feat in itself.

Hydrogen is truly a community release. Use cases span across enterprise, service provider, academia, data center, transport and NfV. There are multiple southbound protocols abstracted to a common northbound API for cross-vendor integration and interoperability and three editions have been created to ensure multi-domain support and application delivery as well as deployment modularity and flexibility for different domain-specific configurations. These packages have a consistent environment yet are tailored to domain and role-based needs of network engineers, developers and operators.

  • The Base Edition, which includes a scalable and multi-vendor SDN protocol based on OSGi, the latest (and backward compatible) OpenFlow 1.3 Plugin and Protocol Library, OVSDB, NetConf/Yang model driver SDN and Java-based YANG tooling for model-driven development.
  • The Virtualization Edition (which includes the Base Edition) and adds Affinity Metadata Service (essentially APIs to express workload relationships and service levels), Defense4All (DDoS detection & mitigation), Open DOVE, VTN, OpenStack Neutron NorthBound API support and a virtual tenant network offering.
  • The Service Provider Edition (again, including the Base Edition) that also offers the Metadata Services and Defense4All but includes BGP-LS and PCEP, LISP Flow Mapping and SNMP4SDN to manage routers, gateways switches.

More information can be found on the website with regards to the releases and projects themselves.

I want to stress the importance of how well the vision has been delivered to date. I’ve been involved in multiple standards-bodies and in open source discussions in the past but this is truly one of the largest undertakings I’ve seen come together in my entire career. OpenDaylight developers have been coding day and night to get this release out the door and it’s amazing to see the collaboration and coherency of the team as we unite to deliver on the industry’s first cross-vendor SDN and NfV Platform. In addition and frequently not mentioned is that many of the protocols listed in the Editions above are also standardized at organizations like the IETF during the same period. Code and specs at the same time. It’s been a long time since rough consensus and running code has been the norm.

Over here at Cisco we’re fully committed to OpenDaylight. We’re currently using it as a core component in our WAN Orchestration offering for service providers to allow intelligent network placement and automated capacity and workload planning. The ACI team (formerly Insieme) collaborated with IBM, Midokura and Plexxi to create a project in OpenDaylight that creates a northbound API that can set policy and be used across a wide range of network devices. And of course we’re bringing components of the OpenDaylight codebase into our own controllers and ensuring application portability for customers, partners and developers alike. From this I would expect to see more code donations going into the community moving forward as well. We made several announcements last week about our campus/branch controller that includes OpenDaylight technology.

At the end of the day an open source project is only as strong as its developers, its community and its code. As we as a community move forward with OpenDaylight I expect it to become stronger with more members joining with new project proposals as new code contributors coming onboard from different industries as well. As I look at our roadmap and upcoming release schedule I’m pumped for what’s next and so happy the community has catalyzed a developer community around networking.

Please do visit the site, download the code and take Hydrogen for a test-drive. We want to hear feedback on what we can make better, what features to add or how you’re going to utilize it. Moreover, we’d love you to participate. It’s a kick-ass community and I think you’ll have fun and the best part; you’ll see your hard work unleashed on the Internet and across multiple communities too.

Tags: , , , , , , , , , , , , , , , , , , ,

#EngineersUnplugged S4|Ep10: Software Defined Hype

January 15, 2014 at 8:05 pm PST

In this episode of Engineers Unplugged, Michael Letschin (@mletschin) and Hans De Leenheer (@hansdeleenheer) discuss the history behind software defined and predictions for what the future holds for applications and developers. If hardware is an enabler and not a limit, what then? How does this impact developers? Let’s listen in:

Behold the developer-unicorn: lean and mean.

Behold the developer-unicorn: lean and mean.

**The next shoot is last week of January at Cisco Live in Milan! If you want to be internet-famous, contact me ASAP to talk about being on the show.**

This is Engineers Unplugged, where technologists talk to each other the way they know best, with a whiteboard. The rules are simple:

  1. Episodes will publish weekly (or as close to it as we can manage)
  2. Subscribe to the podcast here: engineersunplugged.com
  3. Follow the #engineersunplugged conversation on Twitter
  4. Submit ideas for episodes or volunteer to appear by Tweeting to @CommsNinja
  5. Practice drawing unicorns

Join the behind the scenes by liking Engineers Unplugged on Facebook.

Tags: , , , ,