Cisco Blogs


Cisco Blog > Data Center and Cloud

OpenStack Juno: The Basics

Guest Blog by Mark Voelker, Technical Lead, Cisco http://blogs.cisco.com/author/MarkVoelker/

Today, the OpenStack@Cisco team is in a celebratory mood: OpenStack 2014.2 (“Juno”) has been released!  The 10th release of OpenStack contains hundreds of new features and thousands of bugfixes and is the result of contributions from over 1400 developers.  You can find out more about Cisco’s contributions to Juno here.  What’s more, in just a few short weeks we’ll be joining the rest of the OpenStack Community in Paris for the OpenStack Summit, where plans for the next release (“Kilo“) will be laid.  We think that OpenStack’s appeal has never been higher, and are excited to see continued growth forecast for the OpenStack market.  Since OpenStack continues to see new growth, we thought this would be a good time to take a step back and review a few basics for those of you that are just beginning to get acquainted with today’s dominant open source cloud platform.

First, a bit of history.  OpenStack was founded in the summer of 2010 as an open source project driven primarily by Rackspace Hosting (who contributed a scalable object storage system that is today known as OpenStack Swift) and NASA (who contributed a compute controller that is today known as OpenStack Nova).  The announcement quickly attracted attention, and in September of 2012 the OpenStack Foundation was created as an independent body to promote the development, distribution, and adoption of the OpenStack platform.  Since then, the Foundation has grown to over 18,800 members spanning over 140 countries and representing over 400 supporting companies.

Simply put, OpenStack is “Open source software for creating private and public clouds.”  Not only is it developed by a wide variety of corporate and individual contributors, it is also used by hundreds of companies (including Cisco!) for a variety of purposes.  You can find a sampling at the OpenStack User Stories and OpenStack SuperUser websites.  The software itself is a set of loosely coupled distributed systems comprised of several discrete pieces of software with a focus on supporting multi-tenancy and scalability for on-demand resources.  Whereas OpenStack originally contained just two major components, today’s integrated Juno release contains 11:

Read More »

Tags: , , , , ,

A New Partnership for OpenStack

What happens when the market leader in cloud infrastructure partners with an open source expert? We witness a very unique opportunity for disruption.

Recently, Cisco and Red Hat announced an integrated infrastructure for OpenStack-based cloud deployments. OpenStack is a collaborationf developers and cloud computing technologists aimed at creating new, scalable solutions. This partnership will target enterprise and mid-market customers by streamlining deployment and operation of OpenStack-based private clouds while providing access to the InterCloud. The integrated infrastructure will combine Cisco Unified Computing (UCS), Cisco Application Centric Infrastructure (ACI), and Red Hat Enterprise Linux OpenStack Platform.

Together, Cisco and Red Hat will deliver a set of InterCloud-ready solutions designed to bring OpenStack to enterprise and service provider customers. By combining complementary strengths, Cisco and Red Hat are in the position to capitalize on this disruption and strengthen their positions as market leaders. Read More »

Tags: , , , ,

#EngineersUnplugged S6|Ep13: #OpenStack and Cinder

October 22, 2014 at 12:31 pm PST

In this week’s episode of Engineers Unplugged, John Griffith (@jdg_8) and Kenneth Hui (@hui_kenneth) discuss Cinder--a way to abstract and give you block storage services inside of OpenStack. Great info with practical applications in this second of our series on OpenStack leading up to OpenStack Summit in Paris.

And let there be whiteboards and unicorns!

Cinder + OpenStack + Unicorns (courtesy of John Griffith and Kenneth Hui!)

Cinder + OpenStack + Unicorns (courtesy of John Griffith and Kenneth Hui!)

**Want to be Internet Famous? Act now! Join us for our next shoot: NetApp Insight. Tweet me @CommsNinja!**

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: , , ,

The Top Five Myths about Cisco ACI

October 22, 2014 at 5:30 am PST

It’s been almost a year since Cisco publicly unveiled its Application Centric Infrastructure (ACI). As we’ve noted in the past, ACI had to overcome a number of preconceived notions about Software Defined Networking (SDN), and without some detailed explanation, it was hard to get your head around how ACI worked and how it related to SDN. As we continue to clarify the message, there are still a number of ACI myths running around out there that we have to spend a good amount of time dispelling, so I thought I’d summarize them here. (Like Centralized Policy Management, Centralized Myth Handling can lead to greater efficiency and increased compliance. :-)).

1.      MYTH:  Cisco has limited software expertise and can’t deliver a true SDN solution because ACI requires Cisco switches (hardware) as well as the APIC controller (software).
REALITY: Cisco believes data centers require a solution that combines the flexibility of software with the performance and scalability of hardware. ACI is the first data center and cloud solution to offer full visibility and integrated management of both physical and virtual networked IT resources, all built around the policy requirements of the application. ACI delivers SDN, but goes well beyond it to also deliver policy-based automation.

2.      MYTH: ACI requires an expensive “forklift upgrade” Cisco customers must replace their existing Nexus switches with new ACI-capable switches.
REALITY: ACI is actually quite affordable due to the licensing model we use and because customers can extend ACI policy management to their entire data center by implementing a “pod” with a cost-effective ACI starter kit. On July 29, Cisco announced four ACI starter kits which are cost effective bundles that are ideal for proof-of-concept and lab deployments, and to create an ACI central policy “appliance” for existing Cisco Nexus 2000-7000 infrastructure to scale out private clouds using ACI. Customers who compare ACI to SDN software-only solutions discover that operational costs, roughly 75 percent of overall IT costs, are substantially lower with ACI — so the total cost of ownership is compelling. Along with the fact that the existing network infrastructure can still be leveraged.

3.      MYTH:  The ACI solution is not open; Cisco doesn’t do enough with the open community. 
REALITY: Openness is a core tenet in ACI design. We see openness in three dimensions: open source, open standards, and open APIs. This naturally fosters an open ecosystem as well. Several partners like F5 and Citrix already are shipping device packs for joint deployments. Customers experience tremendous benefits when vendors come together to provide tightly integrated solutions engineered to work together out of the box.

ACI is designed to operate in heterogeneous data center environments with multiple vendors and multiple hypervisors. ACI supports an open ecosystem covering a broad range of Layer 4-7 services, orchestration platforms, and automation tools. One of the key drivers behind this ecosystem is OpFlex, an open standards initiative that helps customers achieve an intelligent, multivendor, policy-enabled infrastructure. Additionally, through contributions to OpenStack Neutron with our Group-Based Policy model, we are offering a fully open source policy API available to any OpenStack user. Cisco is also working with open source Linux vendors like Red Hat and Canonical to distribute an ACI Opflex agent for OVS, and contributing the Group-based Policy model to Open Daylight.

4.      MYTH: Customers want SDN solutions for their data center networks, but ACI is not an SDN solution.
REALITY:  We believe that SDN or even software defined data centers are not the sole results customers are looking for – it is the policy-based management and automation provided by ACI that delivers tremendous benefits to application deployment and troubleshooting– and provides a compelling TCO by cutting operational costs.  Channel partners agree with us:  a recent study by Baird Equity Research surveyed 60 channel solution providers and found that they would recommend the Nexus 9000 portfolio and ACI to their customers.

5.      MYTH:  Cisco can’t compete against cheap commodity “white box” switches – they are the future of data center networks.  
REALITY:  The truth is that only a handful of companies can effectively deploy white boxes because they require a great deal of operational management and troubleshooting, which is more expensive than the upfront costs of non-commodity hardware. Deutsche Bank published a report last year titled “Whitebox Switches Are Not Exactly a Bargain” which explains how the total cost equation changes when you take into account operational costs. In addition, white boxes don’t include the rich features and capabilities that most companies want. Channel solution providers know this very well. The same Baird Equity Research study of 60 channel solution providers cited above indicated that only 2% would recommend NSX running on white-box or non-Cisco networking gear.

In the data center, “one size does not fit all”, so Cisco offers a variety of switch configurations to match customer needs. For example, customers can start with merchant silicon-based line cards and migrate to an ACI environment with ACI-capable line cards and APIC, if and when they wish.

BOTTOM LINE:  We believe that Cisco will continue to win with our partners in the data center by delivering innovation through a highly secure and application centric infrastructure.  Through training, support, and new certifications, we are empowering over two million networking engineers and thousands of channel partners worldwide to succeed with ACI in the data center and cloud.

Tags: , , , , , , ,

Cisco and OpenStack: Juno Release – Part 2

The tenth OpenStack release codenamed Juno was released on October 16, 2014. This press release provides a good summary of what to expect in Juno. It also discusses important new capabilities included in the more than 340 new enhancements built in to Juno and highlights different usecases that showcase the diversity of workloads supported on OpenStack.

In the first part of the Cisco and Openstack Juno Release blog, I covered Cisco’s OpenStack team contributions to the Neutron project. Here I’ll provide details of our contributions to other OpenStack projects as well highlight our development efforts on StackForge. Cisco was the sixth top code reviewer for the Juno release across all projects in Juno release and is Foundation’s fifth largest company in terms of OpenStack membership.

This Nova blueprint was completed in Juno and provides support for configuration and provisioning of instances with SR-IOV port connectivity.  The implementation generates SR-IOV specific libvirt domain and network configuration XML for the instances as well as includes the capability to schedule instances based on the compute nodes SR-IOV capabilities.  One of the key use-cases for SR-IOV is Network Function Virtualization (NFV) that requires high performance traffic throughput in and out of a virtual machine providing network services (Virtual Network Function or VNF).

We proposed and implemented support for metering Network Services in Neutron using Ceilometer. This included new pollsters and notification handlers for Load Balancer as a Service (LBaaS), Firewall as a Service (FWaaS) and VPN as a Service (VPNaaS). The metrics are categorized into Provider or Service Level, providing different level of details. Provider level metrics help determine the type of implementation and its feature, whereas the Service level metrics provide more granular metric details on the service health and consumption. Separately, instance metrics were enhanced as part of this blueprint to support read and write metrics per instance disk device.

In the Cinder project, Fibre Channel Zone Manager allows FC SAN Zone/Access control management in conjunction with Fibre Channel block storage.  It has a pluggable architecture and we contributed the Cisco FC Zoning plugin that automates creation, deletion and modification of zones in zonesets.  Zones are configured automatically as part of the active zone set for the specified VSAN in the FC SAN to provide a more flexible and secure way of controlling access.

Enhancements to Horizon to enable configuration of  IPv6 subnet modes is also part of the Juno release. This allows tenants to configure address and Route Advertisement (ra) mode for their subnets through the user dashboard. Neutron supports multiple IPv6 address configuration modes including SLAAC and DHCPv6 (both Stateful and Stateless modes).

StackForge

The Cisco OpenStack team has been actively developing across different projects on StackForge as well. This provides an excellent platform for OpenStack related projects to make use of OpenStack project infrastructure and also continue to collaborate in the open.

OpenStack Services Puppet Modules -- One of challenges that we hear about from our OpenStack customers is how to make OpenStack more manageable and deployable.  There are several different deployment options for OpenStack and we have tremendous experience with automating the underlying system and service configuration via Puppet. We work with customers, partners and the community to enhance Puppet modules for OpenStack services and integrate with Cisco infrastructure as well.  We also recently announced, in collaboration with RedHat, Cisco UCS Integrated Infrastructure that combines Cisco’s server, switching and management technologies with Red Hat’s enterprise-grade OpenStack platform.

Group Based Policy (GBP)– Currently staged on StackForge, this project aims to provide policy abstractions that extend the current Neutron API resources and introduces a declarative policy driven connectivity model that presents application-oriented interfaces to the user. The Group Based Policy framework implementation provides the flexibility for new API resources – End Points, End Point Groups, Contracts and Classifiers – that can be mapped to existing Neutron resources or passed directly to a third party controller.  In addition to a mapping driver that supports all existing Neutron plugins, Cisco will also be releasing a driver to directly integrate GBP with its Application Policy Infrastructure Controller.

Nova Solver Scheduler – For resolving complex constraints based on policies and business rules, we have been collaborating with the community to develop a smart Nova Scheduler driver that models compute placement as a supply and demand problem.  The intent is for the Solver Scheduler to integrate with the Gantt project that is aiming to separate out the Nova scheduler as a standalone project.

Summary

Cisco’s OpenStack team contributions are across numerous projects in OpenStack. Our aim is to work with the community, with our customers and partners to enable more successful OpenStack User Stories, resulting in a win-win situation. We are going to be presenting several general sessions that were selected as part of the community voting process at the upcoming Kilo Summit in Paris. You can find more details in this blog post and we look forward to seeing you there!

You can also download OpenStack Cisco Validated Designs, White papers, and more at www.cisco.com/go/openstack

 

Tags: , , , , , , , ,