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.
Business leaders today are heavily growth-oriented and are looking at new ways of deploying applications to obtain greater agility. That is where we see hybrid cloud becoming mainstream as it frees businesses to run applications on-demand and where it’s most cost-effective. Cisco InterCloud was announced to address this opportunity and facilitate optimal hybrid cloud deployments.
Cisco InterCloud comes with unique capabilities that enable enterprises to connect their private cloud to heterogeneous public clouds. It creates the notion of a single scalable hybrid cloud for all physical, virtual and cloud workloads -- an infinite datacenter where the public cloud is treated as a virtual extension of the data center. Cisco InterCloud is designed with these tenets:
Open: Customers are excited about Cisco InterCloud, as it is an open solution that gives customers the freedom to choose hypervisor on private cloud and select their public cloud from a rich ecosystem of cloud providers. Service providers like InterCloud as it is open API based, integrates with multiple cloud platforms, e.g., CloudStack, vCloud, and OpenStack and enables them to rapidly offer a hybrid cloud solution. It reduces the effort to onboard enterprise customers. Cisco InterCloud thus provides a multi-cloud, multi-hypervisor cloud experience.
Secure: Another key factor in hybrid cloud adoption is the need to address the security and compliance concerns of public cloud deployment. Cisco InterCloud provides end-to-end secure connectivity by encrypting traffic between the enterprise private cloud and the service provider cloud. It also ensures workload security by encrypting all data-in-motion within shared multi-tenant public cloud. Additionally, customers can also deploy network services such as zone based virtual firewall and edge firewall for further workload security within public cloud.
Flexible: Customers demand bi-directional workload portability across private and public clouds. With Cisco InterCloud, customers not only can provision workloads from a self-service portal, but also with a click, migrate workloads to the public cloud and back. All of this activity happens behind the scenes as InterCloud converts workloads to the right VM format, such as VMware VMDK to AWS AMI, or to CloudStack format for providers such as BT. It makes workload portability easier as applications don’t need to be re-architected as IP addresses are retained upon migration and enterprise VLANs are extended into the cloud.
I believe that lines of business and developers are leading the journey to hybrid cloud adoption. IT has realized that it needs to shift away from its role as gatekeeper to instead being a partner to Lines of Business but IT faces certain challenges in doing so. IT has to deal with the overhead of integrating with each cloud provider and find ways to do in a secure manner. Cisco InterCloud enables IT to act as a cloud broker on behalf of lines of business. Cisco InterCloud provides unified hybrid cloud management through a built-in IT Admin portal and an extensible northbound API layer. It also allows IT to enforce consistent network security, L4-7 services and workload policies throughout the hybrid cloud.
This week’s Cisco InterCloud announcement demonstrates our continued commitment to customers. We envision a future where customers have an array of cloud options and can pick the ‘best fit’ based on workload needs, performance, cost, and location requirements. We are going into beta next quarter and have announced general availability soon afterwards. As 2014 dawns, we see a shift towards mainstream hybrid cloud adoption — hybrid cloud is finally here for real.
Earlier this week, we announced the Cisco Domain Ten framework 2.0, enhanced by great input from customers, partners, and Cisco’s well-earned experience of strategizing and executing IT transformation.
The enhanced Cisco Domain Ten framework helps customers drive better strategic decisions, providing greater focus on business outcomes, providing deeper analysis of hybrid cloud implications, and extending the framework beyond data center and cloud to include all IT transformation initiatives.
You may have read Stephen Speirs earlier blogs about Cisco Domain Ten for cloud transformation. Today, let’s look at key changes in the Cisco Domain Ten framework 2.0 from the original version. These changes have been adopted to enhance discussions on three themes:
Highlight importance of public clouds as part of IT transformation and solutions using IaaS, PaaS, and SaaS within the data center and across the entire business.
Addition of “Organization” in Domain 10 to bring together the business and technology focus for strategy discussions.
Name changes for some domains to facilitate ease of alignment and discussion on overall IT transformation across multiple architectures and technology solutions such as ITaaS, collaboration, mobility, video, etc. for both enterprise and provider perspectives.
I’m at our annual Cisco Live Europe conference in Milan this week – it’s a great event and a great opportunity to introduce new innovations to customers. In fact, today we announced the latest release of our cloud management software solution: Cisco Intelligent Automation for Cloud (Cisco IAC) version 4.0.
I recently wrote about the new Forrester Private Cloud Wave, and how Cisco was ranked in the top three overall and #1 in strategy. Our high marks in strategy in that report were based in large part on the roadmap and strategic vision that is being delivered through this new cloud management release – together with the latest release of Cisco UCS Director for infrastructure management.
Cisco Intelligent Automation for Cloud is a cloud management platform designed for enterprise and public sector IT organizations building private and hybrid clouds, as well as service providers deploying public or virtual private cloud services. This is the fourth major release for Cisco IAC – and it’s a big one.
With the new 4.0 release, Cisco is breaking ground by providing both the out-of-the-box functionality that our customers are asking for and the flexibility that we know they need as they extend their cloud deployments beyond basic IaaS.
Cisco’s award winning converged infrastructure management software solution just got even better! In the latest release of Cisco UCS Director, we’ve added broader and deeper infrastructure support across the compute, network, storage and virtualization layers, as well making the product even more scalable. The latest release also comes with new software development kits (SDKs) for partners to provide extensibility and interoperability and a northbound API for integration with Cisco’s Intelligent Automation for Cloud (IAC) as well as other cloud management systems. Let’s take a closer look at these enhancements in detail.
SDKs and APIs
UCS Director’s new SDKs and APIs were recently made available to give our partners the following functionality:
Northbound API which integrates into higher platforms like Cisco IAC. This API enables you to perform operations on Cisco UCS Director resources and to integrate those operations into applications so that they can provide API-supported functionality and features.
SDK available on cisco.com & DevNet (CDN), which provides open automation for partners looking to create new device connector
UCS Manager 2.1 (Delmar); KVM console; SAN zoning through UCS Manager; standalone management of UCS C-SeriesUCS Integration -Local disk provisioning and policies
-Workflow tasks for vNIC templates and service profile
-Assign blade or server pool to group
-Cloning of profile and profile template
Whiptail – application acceleration
Invicta, Acella API Version 1.5 support
CRUD actions, workflows, and reports
Converged and stack views
UCS Central Integration
-Multi-domain Manager concept
-Inventory for UCS-M elements
-Local/global service profile and templates
-Pools and policies for network and storage equivalent to UCS-M