Data Center

EMC World 2015: OpenStack Kilo and the On-Demand Data Center

by Madhu Kashyap ‎05-01-2015 08:30 AM - edited ‎05-06-2015 10:00 AM (5,431 Views)

This week, OpenStack Kilo, the 11th release of OpenStack was released with some staggering numbers. Over 400 new features, 3300 bugs fixed, code contributed by over 1500 developers from more than 169 organizations and about 20,000 commits across all projects. Brocade’s own contributions were significant as well. In Kilo, Brocade upstreamed 10 plugins that covered switching, routing, and SAN Fibre Channel as well as NFV products including Vyatta vRouter and vADX (LBaaS). The release of these plugins enables a number of use cases. Let’s dive into one of the key use cases that illustrates the concept of elasticity and the On-demand Data Center.

 

Elasticity is one of the key tenets of cloud computing. It’s the ability to spin up or spin down instances (e.g. compute or NFV) to make better use of the infrastructure. Let’s say a tenant is deploying a three-tier application – web tier, app tier, and database tier. The tenant would need to quickly deploy a network and attach the virtual machines to this network so that they can communicate with each other. Let’s say the virtual machines are placed on different hosts throughout the data center. We all know that virtual machines often migrate from one host to another and when this happens the port profiles need to move so that the same policies are consistently applied. Measures also need to be taken to avoid data loss. Brocade’s Ethernet fabric with VCS technology in the data center provides these capabilities and can be easily orchestrated from OpenStack using the Brocade VCS plugin.

 

Now let’s assume that the demand for the application suddenly skyrockets and so the cloud admin spins up more virtual machines for the web-tier. This now requires a virtual load-balancer be placed in front of these VMs to redirect the requests. In just a few clicks the Brocade vADX LBaaS could be spun up through Horizon or the OpenStack APIs. The Cloud Admin or tenant could also add a Firewall to this setup to separate the trusted network (private network) from the untrusted network (public/internet traffic). This is also done easily by spinning up a Brocade Vyatta FWaaS image and using the Brocade FWaaS plugin.

 

Many datacenters have separate storage switches and arrays for high performance connectivity and IOPS for their most critical applications. So how about the database tier? This tier of the application is configured to read and write to SAN storage arrays. As Cinder is used to assign volumes, the Brocade SAN FC Zone Manager plugin for Cinder can be used to track and assign zones. This plugin was one of the first to be upstreamed from Brocade given Brocade’s SAN heritage and deep knowledge of this space.

The automation and efficiency benefits of the on-demand data center aren’t limited to managing multi-tier applications. There are equally compelling use cases for connecting globally distributed data centers, or to simplify hybrid cloud deployments. Today, Brocade is delivering the On-Demand Data Center Network by interconnecting all resources within and between data centers.

 

Learn more about all of the solutions above next week at EMC World 2015.

 

***** UPDATE *****

On May 6th, EMC posted a new blog about the company's continued support of OpenStack. I highly recommend giving it a read and stay tuned for more information as we get closer to the OpenStack Summit later this month.