 So let's get started start. Sorry about all the technical difficulties there. My name is Dan Floria I'm a product manager in the open stack team at VMware and I'll be talking to you about open stack and VMware and how the two work together now the schedule shows that Scott Lowe and Dan Wenland are supposed to be presenting and the schedule is wrong So you're stuck with me. So I know Yeah, exactly Before I get started, I just wanted to give you an overview of what's going on in this room this afternoon So we have a couple of more sessions after this one We have one the one right after this Arvin, Sony and Michael West are going to be going through a deep dive demo of the VMware integrated open stack product and I'll talk to you a little bit about that product so you know what it is and Then the last session will do a hands-on lab where if you want to try Open stack and see how open stack actually works with VMware You can either follow along on your own laptops or you can just watch it and see you know There's a hands-on lab You can also try it yourself later if you'd like and then tomorrow There's a great session Dan Wenland is going to be talking about open stack and VMware so if you want additional information kind of a good overview of all the activities around open stack from VMware That would be a great session to attend Okay For this session, I will hopefully keep it simple here. I'll go over what open stack is And just provide a definition that will help me Explain to you how VMware plugs into that and then I'll go over a couple of deployment options that you have for Open stack on VMware included including the VMware integrated open stack product and I'll give you a few links where you can learn more about it First of all what I wanted to do is just make this really clear The choices that you have when you're deploying open stack. So I Think it's less prevalent today, but there's still this notion that open stack and VMware You know, it's a fork in the road You have to decide, you know, are you going to go open stack or are you going to go VMware? And in fact the two work together So you you leverage VMware you can leverage VMware as an underlying platform When you're running open stack and what I'm hoping for is that this presentation Will help you understand how that all fits together and by the way, this is kind of an introductory So if you're already experts ninjas and open stack, you know, this is probably a little bit too basic for you Let's start by by providing a definition for what open stack is now. Everybody here is at the open stack summit So I'm sure everybody knows what open stack is. I just want to frame the discussion here to to Allow me to talk to you about how VMware plugs in So open stack is a framework for providing developers with a cloud style API on one end and On the other end providing you with a choice of virtual infrastructure So you're basically getting an API on one side and you're getting a choice of technologies that you want to put underneath VMware being one of them now When you're deploying open stack, you can see here. There's You're you're gonna have a data center. You're gonna have a bunch of compute. You're gonna have storage networking compute and what you want to do with open stack is create Put a framework around that to create a cloud Where you can start consuming that infrastructure that you have in a in a way that has a this cloud like API So that's what open stack lets you do first of all it creates a This abstraction around it to create a Consumption to allow you to you have a consumption API That's a cloud style API and it also takes a variety of different technologies and has the ability to wrap those things into a into a cloud Once you've wrapped open stack into this consumption API framework your application DevOps team or whoever is using that cloud Can start, you know writing scripts writing application management tools what not And those applications can take advantage of the open stack API start making API calls to do things like provisioning Scaling up and down doing code updates, whatever the application requires For you know, just one slide here to talk about some some of the workloads that are targeted for open stack so right now generally the applications that get targeted for open stack that we see are scale out SAS applications or web applications Test dev type of workloads and these are these are the kind of applications that need a lot of agility So they need you know, you're going to have an application that are you going to have some code that goes and deploys an Application and it needs to make changes a lot So you need to create a VM term down scale up scale down So you need kind of an agile infrastructure an agile API kind of Infrastructure form that that allows you to make these changes quick and that's generally what we see the people deploying open stack This is what they're doing with it Less so are the traditional tier one applications Whether they're tier one themselves or they're supporting a mission critical Application like let's say you have a database that you're using maybe for a 9-1-1 call service or something like that So we're seeing less of these kinds of applications to being deployed in open stack Because these tend to be the type of applications that you deploy and then you are very careful with the settings on the VMs For these applications and you're you're kind of managing them by hand and they need less agility than these kind of web SAS type Applications, so that's what we've seen so far some real-world customer use cases, so this is kind of a representative set of Common use cases that we've seen so we worked with an information company that wanted to create an internal DevOps environment They're already using AWS For an application that they're using there. This is a global company. So they want to use AWS because it gives them They don't have data centers all over the world where they need them and AWS gives them that but in addition to that they're looking at leveraging their IT environment for Providing this DevOps environment We worked with a large web company and this is not like Google or Yahoo It's not that big, but it's still pretty big and they wanted to provide an AWS style internal offering to developers This is a pretty common thing that you would hear we want an AWS style API, but we want to bring it in-house An enterprise that we talked to they wanted to do self-provisioning to allow developers to do self-provisioning Essentially what they said is I don't want support tickets You know, I don't want somebody to come to me and tell me that they need a VM I just want to let them do their own thing let them do it themselves so that I don't have to spend time on it and Finally we will not finally but just final example We talked to a financial company and this is another thing that we've heard from a few customers where they have a corporate mandate basically their management is saying that They'll shell use OpenStack and typically I think the reason that That the corporate mandate comes is that upper management wants to have the vendor neutrality of the API so that they can have a choice On the infrastructure that they want to use Okay, so now I'll start talking about how you deploy OpenStack and VMWare together and to do that first we can look at the architecture of vSphere and OpenStack my goal here is to kind of I'm assuming that there are people in the room who have Pretty good VMWare experience and what I want to do is explain it a little bit from from that point of view vSphere is a tightly coupled architecture and this is not good or bad it's just it was designed for a different purpose and OpenStack and this you know it's designed so that everything runs in vCenter and between vCenter and ESX there's this particular way that you deploy it and It's just you know kind of together as one thing and this is different from OpenStack Which is a lot more distributed and I'm a lot more loosely coupled Now I know this slide is a little bit daunting to look at It's probably a bit dated as well but I think it's a good representation if you want to get into more details of how what OpenStack looks like and You know it looks complex, but I think any Significant or any large-scale software system if you go to enough detail you're gonna have a diagram like this So it's really it looks a little scary, but I don't think it's that scary from any other Software systems out there. So the point to the point here is that it's a distributed architecture It uses a message bus. It uses a common database. You can deploy This is in a variety of ways you can deploy it on bare metal you can deploy it in a VM You can deploy it in a vSphere Cluster you can you have a variety of configuration options that you can choose from As long as as these components have connectivity So you have a network that connects all these things together and as long as you have a database that they can all access So they have the shared state You're pretty much good. Of course, there's a lot of complexity to deploy it But that's kind of what you need in this architecture and we can simplify this picture as well I mean you can yeah, we'll go through this and simplify it So first of all up there sits the horizon dashboard and this is the GUI that you see in OpenStack The Swift object store if you abstract out the details then you can look at just you know It's a box of course each one of these components as you hear about all of them They're not just necessarily one service There are a variety of processes working together and coordinating over a message bus and using my sequel or what whatever database underneath Glance is used for image storage Nova probably one of the most significant projects in OpenStack is used for compute Cinder for block storage Neutron is the networking project and finally Keystone is used for authentication Now that we have that out of the way. I think we can talk about how OpenStack and VMware work together and and what the you know I at the beginning I talked about OpenStack providing a northbound API and then allowing you to plug in a variety of virtual infrastructure technologies underneath and The way that OpenStack allows you to do this is through a plug-in or driver model so here you can see Nova, Cinder, Glance, Neutron and For each of those VMware has contributed drivers so We have our own drivers just like anybody else in OpenStack and these drivers know how to talk to our particular technology Right no different than anybody else So when an API comes in let's say you get an API you go into Horizon and you create a VM or you create an instance That gets translated into an API request to Nova which goes to the Nova scheduler Which goes to the to the VMware vCenter driver Which then calls vCenter which then calls ESX which then finally creates a VM and it's a similar path with all of these Other projects so when you create a volume The you go into Horizon you create the volume it goes to Cinder Cinder calls the appropriate driver and the driver goes to vCenter and creates the The volume in the in the data store in our case The same it's the same model with the other components, so I won't go through them The one that's a little bit different here is that for us The the NSX driver talks to NSX controller not to necessarily to be center Any questions? Yeah No, actually so there was a driver Written I was actually not created by VMware. There was a driver in the community that Talked from Nova directly to the ESX hosts and that wasn't a driver that VMware supported The one that the driver that VMware introduced was the one that talks to vCenter and that's the one going forward I'm not sure if the ESX driver has been deprecated I think there were discussions that it was going to get deprecated, but I'm not sure if it's been done or not Yes They're all open source. Yeah, all of our drivers are in open source just like any other driver and open stack and these are all written by VMware, so NSX the NSX driver has been there since Day one of quantum quantum was renamed neutron a year or two ago, but the NSX driver has been there since day one we added the Nova vCenter driver about a year and a half ago in the grizzly release and Cinder the cinder driver was added in Havana a Year ago and the glance driver we introduced six months ago in the ice house release so and they're all Written by VMware, but they're all upstream. I mean, that's not just VMware. It's other people contributing as well Other questions clear So this what this picture attempts to do is give you kind of a block diagram of how kind of technically how the plug-in model works and open stack and how it works with VMware and Hopefully it shows you that it works just like any other Kind of plug-in or driver in open stack and frankly this is kind of the driver the model You would use it for your printer or something right? It kind of works in a similar way Now we can zoom out a little bit and look at an entire open stack cloud. So if you're running You know, you're going to deploy open stack in your private cloud in your data center There are a variety of choices that you have to make and that's what we're attempting to show here There are but a bunch of layers here and at each layer as a cloud Infrastructure admin or team you have to make a decision of what you want to use So you're gonna have to choose obviously your hardware You're gonna have to choose what virtualization technology you want to use if you use no using open stack You've already made the decision on on this layer here because you're using open stack And then you also have to make choices on what you want to use for operations and management if you run with open stack on top of VMware for Compute you're going to be using the ESX ESX hosts and vCenter For networking you're running with NSX and for storage you can leverage vCenter data stores in addition to that Any any deployment of open stack you have to consider how my once you deploy I know you know I'm gonna talk about deployment to and it sounds like it's the end game. It's not That's just the beginning once you've deployed open stack and you're running this in production you obviously have to maintain it operate and manage it, you know kind of keep it up and running and Whatever solution you go for with open stack you're gonna need to have some tools around that for log management for just operations and management and The the solution from the solutions from Cisco from Vmware are VR ops login site and ITVM and On the management layer we realize automation and cloud foundry as well Okay, now we've gone through Block levels we've gone through the different layers of your cloud deployment We've gone through all this stuff and it's easy to kind of get lost in the weeds So I just want to make sure that that everybody understands that when you're running open stack with Vmware You're still using both vCenter and open stacks. So you're using both the horizon GUI So you're using the horizon GUI for doing things like obviously you're gonna use it for tenant workloads So when you create VMs tenants want to create VMs or volumes things like that You're gonna use the horizon GUI or you're gonna use the open stack API If you want to do Infrastructure management, so let's say you want to add clusters you want to add data stores If you want to do things like that, then you're gonna do that through vCenter Also, if you want to let's say you want to turn on HA in a cluster There's nothing in the open stack API that would let you do that or tweak DRS or something like that All of those things are still done through the center The open stack API is really mostly meant as a consumption API So it's meant to standardize how you create a virtual machine how you create a network it's much harder to try to standardize on how you manage your infrastructure because It's just you know the way you manage a KVM deployment or you know the way you manage your network with VMware NSX versus a Cisco solution or something is going to be very different. So standardizing on the management is Well, it's not been done yet Okay So hopefully it's kind of clear how the two the two sides fit together We can now start talking about how you would actually deploy. So how you know, this is how it all plugs in but if you want to have Open stack running on top of VMware in your environment. How do you actually make that happen? How do you get that installed? so one way to not do it is to You know go and do a get clone and start pulling down code and trying to install this yourself You can go down this route. It's Not recommended. I think You know, there are people who have tried and it's not just I think it's just open stack in general trying to just go From scratch and pull code it from upstream. It's difficult and especially for us for for our VMware customers for VMware admins What we wanted to do is provide them a way of deploying open stack on top of VMware not only in a way. That's easy Easy to deploy but we wanted to do it in a way. That's that's intuitive for a vSphere admin. So VMware admins are not necessarily Linux Linux or Open stack experts, right? They're VMware experts. So we wanted to let them deploy and operate open stack on top of their VMware infrastructure Leveraging their existing skills. So you basically you already know how to run VMware Make it as easy as possible for me to run open stack on top of that So for that we introduced a new product called VMware integrated open stack and this product right now is in a private beta and The goal is to make it the fastest and most reliable way of getting production grade open stack cloud on top of VMware infrastructure So what is VMware integrated open stack? I'm going to give you kind of a broad view of what it is and what the different components are and After this session, there'll be a demo that walks you through exactly how this works But at a high level what this product is First of all, you're starting with an existing vSphere environment. So you we assume that you have vSphere running you have vCenter you have clusters data stores all the stuff that you would normally have in a VMware environment On top of that VIO VMware integrated open stack is is Delivered as an OVA that you download and install in your vCenter and It's already got the drivers kind of built in for you. It's the architecture of it is kind of a tested validated reference architecture that we Is just part of it that you automatically get it has integrated tools for installation for upgrades for workflows like adding clusters and adding data stores to your installation and things like that So it's really trying to simplify the the deployment here and In addition to that, this is not part of vIO, but it's something that as I mentioned earlier, you will need tools once you've deployed you will need tools that let you Manage and operate and troubleshoot the installation and Together that's kind of the overall overarching vIO solution right you start with an existing vSphere environment you add vIO you use VMware tools like VR ops and log-insite for management operations and troubleshooting You get a fully validated architecture and you get a single support Contact so you can call VMware for any trouble you have from OpenStack all the way down to the infrastructure. So that's kind of the the short pitch Going one level deeper To show you what the the exact components here are in vIO first of all as I mentioned you start with your Existing VMware infrastructure. So you're going to have a vCenter server. You're going to have ESX hosts You need to have a management cluster with that with three ESX hosts. You need to have a compute Cluster for tenant workloads. You're going to have to have some data stores and a sex all these things all this stuff is not part of vIO It's just kind of the base Infrastructure that you need on top of that you're when you install vIO you're adding Nova Cinder Glance Neutron Of course, there's also Keystone and Horizon and the other projects But these are the projects that have Plugins or drivers that are VMware specific. So when you're deploying we already know that you're deploying on top of vSphere So we pre-configure it for you. There's no additional configuration that you have to make It's already the drivers already loaded in they're already configured to talk to your underlying infrastructure Additionally also I should mention that there are a lot of configuration options when you deploy actually every single service here Nova Cinder Glance They have hundreds of different configuration options and if you kind of mix and match them together if you you know You end up with an explosion of options that you have and we've basically fixed most of that configuration for you So we've kind of made those configuration decisions strobe lights There is also a vIO server that lets you do installation it lets you do, you know The workflows upgrade all that stuff and all of this in the orange box is what vIO? essentially is It's based on a VMware open stack distribution. So it's an official distro It's delivered as an OVA and I should also mention that it's currently based on ice house It's based on the ice house release. We do plan to keep this up to date so as We as open stack releases progress. It's in our interest definitely to to stay in sync with that and This is just a maybe a sneak preview into what you're going to see in the following session of what it looks like And it hopefully gives you a feel of you know of what it looks like from from a vCenter point of view So as I mentioned, we really tried to make this friendly to a VMware admin So we want to make it Intuitive and use kind of a workflow that is is something that a VMware admin would be used to so when you when you Install and deploy your OVA it goes in your vCenter and then you double-click that and you go through a configuration wizard That lets you install Okay so when you deploy with vIO you get You know that the architecture is fixed for you. So we have it's a production grade architecture So you get redundant load balancers you get active active controllers you get a replicated database you your configuration options are are Pre-configured this is a an architecture that we Use internally actually inside the M where we run it in a production opens that cloud. We know it works We've tested it all this stuff There are cases where customers are going to fall outside of that kind of box that we drew what we tried to do is Constrain the problem to make it simpler and more repeatable so that customers can can deploy this easily and customers can do this You know Many customers can do this easily but there are customers who are going to fall outside of of what we kind of designed here in terms of Architecture and they're too if they're too far outside of that box that we drew Then we still want Customers to be running OpenStack on top of VMware infrastructure So in those cases we would recommend that you work with one of our district partners So I've listed them here and you can use one of these district partners to hopefully Accommodate your use case. So if you have specific requirements and vio is just not quite a fit for you This is the best route to go So I am at the end here. So we talked about what OpenStack is we talked about kind of the framework model of having a Vendor neutral API and the technology choice that you have to fit in underneath and hopefully at this point it's clear that VMware is one of the choices that you have they're not opposing Technologies you don't choose between OpenStack and VMware you use OpenStack and then you choose which hypervisor platform You want you want to use underneath you want to use vSphere? Do you want to use KVM? So that's kind of the decision point we talked about OpenStack workloads and how VMware integrates with OpenStack we talked about the the loosely coupled and the tightly coupled architecture differences between vSphere and OpenStack the driver model of how we plug in and deployment choices So if you want to learn more first of all there is a hands-on lab that you can Do yourself whenever you like so the link is here. You can go. We're also going to have a session later today Where we walk you through this if you have questions. There's a community site Where you can go and finally if you're interested in trying out vIO. There's a beta site where you can go request access private beta questions It's based on ice house. Oh, it's based on ice house, but it's a VMware distro What distro what OpenStack distro or oh? I see so we install. I mean the OS we give it to you as a black box So when you when you deploy vIO You will deploy it and then the operating system that we use internally is essentially not I mean it's Constrained right so I can tell you but it's really it's really from a customer point of view really shouldn't matter From a user point of view right now. It's a bunch of well I mean their differences between those products differences and capabilities versus OpenStack and what it provides and this is you know Some customers want to use OpenStack. So we provide that choice, right? So if vCAC is a better choice for you, then that's the way That's the way you would go and and you know we can talk maybe afterwards There are differences between the two and what vCAC and what OpenStack provide you It's just kind of a business decision of which product is the right one for you Yes, you need enterprise plus You need NSX. That's the way that you get otherwise if you don't do that you can't use neutron Capabilities there is a basic mode and vIO where you can get provider networks only with no security groups And then you can go with distributed virtual switch more questions No, okay So the next session is a technical deep dive into vIO into VM or integrated OpenStack So if you're interested in seeing this in action and getting a better feel for it stick around