Hello. My name is Marcos Hernandez. I'm a Principal Engineer here at VMware and I am responsible for our presales activities around OpenStack and NSX and containers. Today, we're going to talk about VMware integrated OpenStack and more specifically, about how OpenStack leverages NSX to provide enterprise-grade network and security services in a private cloud implementation based on OpenStack. But before we get into that, let's take a step back and define some basic concepts with regards to OpenStack. OpenStack is an aggregation of independent projects that are individually developed but jointly tested. As you can see here in this slide, there is a one-to-one correspondence between each one of these projects and a specific function that you will typically encounter in a private cloud implementation. So, if we take for example Nova, which is a compute project in OpenStack, the notion here is that, if you need to consume some compute resources, say for example, you want to create a virtual machine which OpenStack calls an instance, or you want to resize a virtual machine, notionally you will be interacting with the Nova API. On the other hand, if you want to create a network, a load balancer creates some security policies for your applications, then you will be interacting with a Neutron APIs, which is a Neutron, is a network project in OpenStack. It will be the focus of this presentation, given that is where we integrate NSX into this architecture. The same notion applies to all the other projects, for example, persistent storage in OpenStack is provided by the block storage service and that is called Cinder. Your image catalog in OpenStack is handled by Glance. There's a UI that is also used in OpenStack, and that is a project called Horizon, and everything that you see here in this slide is a core service of an OpenStack implementation. What core means is that, if you are providing a commercial distribution of OpenStack, you need to include these projects with your distribution to be able to get our rubber stamp from the OpenStack foundation that basically says that your OpenStack distribution abides by a common set of APIs, and it exposes normalized APIs for the consumers. This group, this interrupt group inside of the OpenStack foundation is known as DefCore and VMware Integrated OpenStack is DefCore compliant. So, what that means is that, someone interacting with VMware Integrated OpenStack shouldn't necessarily be able to tell that this is a VMware specific implementation of OpenStack. That is the promise of deaf core. As I said, VIO is DefCore compliant. DefCore also allows you to list your distribution at www.openstack.org, and you can see if you go to www.openstack.org, and you'll look for VMware Integrated OpenStack, you will see the set of API test cases that we had to pass to be able to attain this designation. VMware integrated OpenStack, the key of our solutions in the eye, is the integration that we provide out-of-the-box. We're more integrated. OpenStack is a fully curated solution that works on top of VMware compute network and storage infrastructure. The idea there is that, not only is VMWare providing the basic infrastructure components in the form of the software defined data center or SDC, but also we're now providing the infrastructure as a service layer, the IaaS layer, using OpenStack that gives you the benefit of that, provides a benefit to you of a single support point for your entire private cloud implementation, and that is the value that we bring to a table. So, the key to understand in this value is by taking a look at where we interface with various infrastructure components when we were talking about VMware integrated OpenStack. On this slide, you will see a red box representing the OpenStack framework. That is OpenStack, and as I mentioned before, VMware integrated OpenStack being DefCore compliant is OpenStack, is not OpenStack like is OpenStack. And think of this, OpenStack or this red box as a cloud operating system. An operating system does not necessarily dictate which endpoint or peripherals you need to use that is typically handled by drivers. The same is true with OpenStack. OpenStack that does not dictate a specific technology for hypervisor or networking or storage services. You connect to this peripherals using drivers. VMware has developed an upstream and open source drivers that connect the compute services of OpenStack to vSphere. The networking services of OpenStack to NSX, and the storage services in OpenStack to native vSphere data stores. If these are provided in the form of NFS, or VMFS, or VS, it doesn't really matter. These are data stores that are abstracted by vSphere and consumed by OpenStack. So, that is the VMware integrated OpenStack, is the integration that we offer out-of-the-box in this opinionated implementation of OpenStack on top of the SDC. But northbound of OpenStack, we exposed a standard APIs. So the typical instrumentation tooling or components that would leverage and integrate with OpenStack can be overlaid on top of VIO to consume this OpenStack APIs and consume the infrastructure that is being as abstracted by it. So, depending on the use case for OpenStack, you will see it being used in different manners. OpenStack is typically seen at the tail end of a CIC pipeline to provide infrastructure as a service. So, that is a very popular use case of OpenStack. OpenStack is also resonating really well with our enterprise customers for the so-called automating IT use-case. We're also seeing a big play of OpenStack in those cases. And finally, last but not least, is the relevance of OpenStack in the telco space with network function virtualization providing abstraction and consumption capabilities for virtualizing the so-called VNFs or virtual network functions that are being used by telco customers to provide this type of services. So, there's a multitude of use cases. Those are the three main ones for OpenStack, and the notion again across the board is the same. OpenStack provides open APIs that are openly and well-documented and that are independent of any specific or vendor-specific implementation for consuming infrastructure That is in northbound aspect of what we offer with VIO, standard OpenStack APIs. But southbound of this red box, we, as I mentioned offer an opinionated integration with vSphere VMware NSX components to provide an entire solution with a single point of contact and a single support contract. Why run VMware or run OpenStack on top of VMware infrastructure? The notion again is very, very, very simple. You want to use OpenStack because it exposes APIs that are attractive for the particulars of your use case, but you want to do it on infrastructure that you know that you trust or you already have personnel trained on. So, that is the case of vSphere NSX and the storage services of OpenStack. OpenStack expresses and exposes the API that you want, but you run it on the infrastructure that you trust. That's kind of the JSON and the core of the value proposition of running OpenStack on top of VMware infrastructure. We have undoubtedly, the best hypervisor technology. We have the best network virtualization technology, and we offer via VMware vSphere abstraction robust and solid storage services that can also be software defined. So, that is the main value proposition of VMware Integrated OpenStack when you run it on top of the SEC. But getting OpenStack on reliable infrastructure is just one part of the puzzle here, one piece of the puzzle. There's also the Day 2 operations. OpenStack clouds are very complex to administer and manage, and we offer instrumentation. Also, out-of-the-box in the form of management packs and content packs across our portfolio of Day 2 operations and monitoring tools, such as we realized operations, we realized Log Insight and for costing, and chargeback and showback, we realized business. So, there's integration and compatibility with each one of these three products for Day 2 operations, which are also critical not only for keeping the lights on, but for understanding and designing for adequate capacity management and optimizing their resource utilization of your OpenStack cloud to get the best bang for your buck. So, Day 2 is something that cannot be an afterthought, it has to be at the forefront of the reasons of why and how we do OpenStack, and our tooling in the form of this different products or provide a great visibility and give you a greater understanding of what's happening with your OpenStack cloud. So in summary, VMware Integrated OpenStack, which is OpenStack, provides the benefit of an open API to your consumers, developers, or automation tools, and you're doing that on top of infrastructure that you trust, infrastructure that for many, many years, you've learned how to optimize and engineer. You can also leverage the skills and expertise of your VI admins and your network admins that are managing vSphere and NSX to provide an OpenStack use case in your private cloud implementation. As I mentioned a few moments ago, the Day 2 operations are also top of mind and the tools that you trust, the tool that you understand that are provided by VMware can also be used in this implementation to bring it in full circle and provide complete visibility of what your cloud implementation looks like.
