 All right. Hello, everyone. It's picking me up, right? Yeah, good. Hi, my name is Dan Willent from VMware. Appreciate you all taking the time to come to this session. I'm going to be talking, this is going to be mostly an overview session about OpenStack and VMware for people who kind of probably don't have a whole lot of background on that topic. We've got a bunch of deep dive sessions later here at the summit that I'll end with a slide that talks about all of those. So it's kind of where can you go next to learn more things. So a little bit about me. A background in networking and security. I joined a company, a startup, called NYSERA. I was there for a while, and as part of that was involved in the very early days of OpenStack, helped create the OpenStack networking project, which was then called Quantum, now called Neutron. And so I was the project team leader, PTL, for that for a couple years. And now I'm at VMware. I acquired NYSERA a couple years ago. And I head up our overall product and strategy around OpenStack. So it's kind of funny, I've been to every OpenStack summit now, since the first one, the private one in Austin. It's kind of helped me realize every six months, it's kind of like this drumbeat of, where is OpenStack now? How is it different from where we were a year ago, two years ago, three years ago? And so as part of that, I kind of started thinking, and kind of made me realize that OpenStack's gone through a couple different ages. And so everyone would probably have a slightly different definition of that, but this is kind of how I think of it. Like in the early days, it was fun. We stayed up all night, we hacked, we drank a little bit of beer, we hacked some more. It was all this kind of like, just grow the community, more people, let's get involved, hey, let's do this thing, it's fun. And this is kind of this age of formation, and there wasn't a lot of companies or vendors, necessarily at that point, vying for anything. Let's make this happen, let's take on the world. And then things like, I remember when I stepped in the San Francisco summit, I was like, where did all these people come from? And then like each summit, it was just more people, and more people, and more people. And it kind of, OpenStack and the expectations for OpenStack just kind of went through the roof. And in a lot of ways, I've talked with a lot of the early leaders of OpenStack about this, and in a lot of ways, there's this notion of kind of like OpenStack was something for nothing. It was a cloud for free, it was amazing, it was this opportunity, and everyone was kind of piling in to figure out what was going on. In fact, someone used a great analogy, this isn't mine, I don't know if he wants me to give him credit, so I'll use it generically. But he said, people kind of had this impression that OpenStack was like my sequel. It was just something you downloaded, you installed, and it worked, and then you moved on to the next thing. So I think that really kind of inflated these expectations around OpenStack that in some ways were actually very hard for OpenStack to measure up to and to deliver on. And so my theory now, and obviously anytime you're, it's easy to look back three years ago and say where you are, it's always harder to make statements about where we are today. But I kind of see us now moving into this age of more pragmatism around OpenStack. People kind of understand what it is better, they understand what it's going to do. And their main question is kind of, how does OpenStack drive value for my business? It's not so much, wow, there's this cool thing that I like to hack on, it's not that, oh, it's this amazing thing for free, it's hey, there's value here, how does that value apply to my business? So if you look into what's caused this shift, it's an interesting question to ask. I think in part it's just more awareness of people who've actually used OpenStack. People have now downloaded it, they've stood it up, they're not just reading articles about it, they actually have firsthand experience about it. There's also this great operator meetups now where you can hear stories from everyone else, people have a much more realistic view of what it means to use OpenStack. And that it's not something that you just download like MySQL and are off to the races. But it's also, my theory at least, is that it's also I think a changing set of people looking at OpenStack. And people who are not these web-scale companies who are gonna throw a bunch of developers at it, but they're actually enterprises saying, okay, I have my existing technologies, I have my existing teams, how is this going to work for me? How does OpenStack help my business? And so there's a handful of general directions or general shifts that I've seen. The first and probably most obvious one is a shift from this free do-it-yourself model more to using some vendor to de-risk. Even some of the very earliest people who are all gung-ho about I need to tweak this part of OpenStack and this part of OpenStack, once they've gone through a couple upgrades, this and that, they're kind of saying, maybe I don't need to tweak this, maybe I'm just going to have someone else help me with that. Another one is kind of early days, everyone's like, oh, I'm gonna hire a bunch of OpenStack-enabled developers and they're gonna come on board and I'm gonna have my cloud project up in three months. Suddenly realize, well, everyone else is trying to hire those, you know, there's 20 of those people in the world and everyone was trying to hire 20 of them. So it's much more of a shift now to, well, how do I take my, how do I enable my current team to deliver OpenStack, as opposed to assuming I'm gonna hire this new team that's just out there. And finally, and this is something that probably is pretty consistent that you're hearing across talks and at the keynote, it's all about from a focus on kind of, oh, this is free or this is cool technology to how do I enable developer innovation? And so let's go into, you know, that's the most important point here, I think, and ultimately that's kind of, my takeaway of this whole kind of thought experiment was that really I think this age of pragmatism is really about people separating out the why of OpenStack from the how of OpenStack, which was something that's actually very surprisingly, it seems obvious now, but it's surprisingly very muddled early on. You know, the why is pretty obvious. There are businesses that want, that see software as a key differentiator, right, and they see automation via APIs as a way that help their software development teams, you know, deliver software faster and more reliably, because they can repeatedly deploy through dev, test, and production. And OpenStack's the house side of that. OpenStack's a framework, right, that enables those APIs for automation. And importantly, you know, it enables those APIs on top of your choice of underlying infrastructure. So that's kind of the context the rest of the talk will actually be talking specifically about VMware. But I actually think this shift in focus is actually important, because these are the types of discussions that we like to have with our customers around OpenStack. It's not just, you know, great, supports OpenStack APIs. Well, any way you run OpenStack is going to support those same standard open vendor-neutral APIs. The real question is, what technology do I pick as an engine? You know, that gives me the operations capabilities I need, the security I need, the ability to troubleshoot, the ability to scale, et cetera. And obviously I'm from VMware, and I think we've got some really cool technology on that front. And so that's what we'll be talking about for most of the rest of the talk. So, you know, the high level way that we think about the value of OpenStack in VMware for our customers is, again, developers should only ever have to deal with those open vendor-neutral, you know, standard APIs that let them innovate, right? But the person running the cloud, the person, you know, in the old days, I'd say carrying a beeper. I don't know what, you know, maybe it's a cell phone now or a smartphone now. But, you know, it's what tools do they have, right, to reliably, securely deliver a cloud infrastructure, you know, based on their existing skill set and existing capabilities. And that's really where the value of bringing the OpenStack APIs and the rock solid VMware infrastructure comes together. And really, I think of this as an opportunity in several ways. First off, you know, it's an opportunity for the OpenStack community, right, to be able to embrace this model of, you know, not just saying, hey, enterprises, you have to learn a new way of running your infrastructure. It's a way for them to say those cloud developers can use all the tools, they can use the OpenStack APIs, the CLIs, they can use heat, they can use horizon, et cetera, right, but they can do that in a way that works with their existing ops team. Those existing ops teams continue to use their same tools, the scripts they have built, the third-party tools they have brought along, all of their existing knowledge and expertise. So, you know, it was really great. We actually worked with the OpenStack foundation. The foundation came to us and said we want to write a white paper about how OpenStack can be accelerated into the enterprise using OpenStack on top of VMware. And so, we actually, you know, they had one of their staff writers work and they actually put out this white paper, they talked to several customers who are using OpenStack in VMware. And so, this was a great example of why I think actually running OpenStack on VMware is a fantastic opportunity for the OpenStack community as a whole, right, it makes it easier to make this technology, you know, be accepted and be embraced and have enterprises take it and run with it. But of course, I actually think OpenStack is a great opportunity for VMware as well, right. Ultimately, as VMware, the way we look at OpenStack is that it's a set of APIs and tools and layers, right, that can make our core product much more attractive to this new generation of developers who wants everything to be API-driven. And so, what you can see up here is a picture of that's our CEO, Pat Gelsinger, up at a stage where we have a VMworld room slightly larger than this, I'd say about 30,000 people in there, right. Telling, you know, maybe a little I'm just estimating here, but, you know, telling, you know, all the 30,000 people there and all the people watching the live stream how VMware is making it easy for VMware customers to consume OpenStack. So this is a product that we announced last at VMworld, it's called VMware Integrated OpenStack. Launched as a beta at VMworld just went GA about two months ago. And, you know, our goal here is if you've already invested in vSphere, right, VIO is free to use. And if you want to pay us for support you can pay us just 200 bucks a CPU per year. So our goal here is to make it both from a financial perspective and from a needs of use perspective very easy for anyone who knows how to run production grade VMware infrastructure to use that to deliver OpenStack to their development teams. So it's always very exciting when you see your boss way up on the stage talking about your product. So that's why I always like that picture. So, hopefully that makes sense at a high level. I'm going to step back a little bit and provide a little context next. So, you know, I mentioned I came to VMware through an acquisition of NICERA. NICERA is actually a company that started out, we actually created OpenFlow, we created the first OpenFlow specs. We created a project called OpenVswitch which, you know, is an open source virtual switch that's still actually at the heart of most OpenStack networking whether you're using VMware or not. And so, you know, pretty soon after we started OpenVswitch, NASA and Rackspace created OpenStack and because of our involvement with OpenVswitch and because Rackspace was using the NICERA technology, they invited us to be part of OpenStack and from there, you know, NICERA was primarily involved in the networking project which is now called Neutron. Once the acquisition happened and NICERA joined VMware, basically VMware had a choice. A lot of people said, oh, VMware acquired NICERA, now they're going to shut down all that OpenStack stuff that the NICERA team did. But actually, you know, we had a lot of discussions about it and VMware was actually very open and they said, actually, we're going to double down on OpenStack. We're not just going to keep the NICERA stuff integrated with OpenStack, the whole rest of our product portfolio with OpenStack. And so what you can see is over time, we've integrated with Nova and Cinder and Glance and Solometer and now we've even launched a full GA product to deliver OpenStack to our customers. So again, this is about VMware's commitment to open APIs, open interfaces for our customer and contributions to the open source community. I want to provide a quick update on a couple of things around Kilo. So obviously, you know, in terms of upstream involvement in OpenStack, we're kind of regularly one of the top 10 contributors to OpenStack, you know, in the Nova, Neutron, Cinder, Glance, all those core projects. And the fact that we upstream this code means that you can download the open source OpenStack code and run it with VMware products. You can actually go to a third-party vendor like Canonical or Red Hat or Morantis or HP and use their distros or NSX technology. And so, there's a lot of options in terms of how you can run OpenStack on VMware. It's not just VMware integrated OpenStack. Another thing to call out, I mentioned earlier, we've been driving the OpenVswitch project for quite a while. We also, just recently, earlier this year announced something called OVN. It's basically, it's kind of a add-on to the OpenVswitch project to solve a lot of the virtual networking challenges. OpenVswitch itself exists only on a particular hypervisor. OVN is about creating those together, creating virtual networks that overlay on top of individual hypervisors to provide virtual networks. So think of this as a base capability. It's compatible with KVM, compatible with Zen as well. And VMware and Red Hat are pretty much the main people. This is all open source. Keep an eye out. I think I heard something that there's a release coming up soon, but I don't know the exact date. So if you want to see the announcement, there's a blog post there, just Google OVN. That's really cool stuff. Another thing we've been driving with an OpenStack is something called the Congress Policy Project. So this is really about saying, well, there's all kinds of rules and policies and enforcement that an enterprise or other business is going to typically want to be able to do on top of OpenStack. And those things don't exist only in this project. They actually span projects. It may be that if you're booting off of this image, that means you can't connect to the network because this isn't a validated image. And so we helped create a community around this Congress project and actually just this last cycle, it was actually promoted to a full OpenStack part of the official OpenStack project. So that was a big win. You can see some of the other companies that are working with us on Congress as well. That's the result of all of this upstream work we've been doing and integration. Like I said, it's really about making sure that there's a great way to leverage every bit of the VMware technology stack if OpenStack is the way you want to think about your infrastructure. And so, you know, in the world of OpenStack, really, there's two main sets of people we think about. We think about the application development teams, right, the DevOps team. They're building their applications. They're either writing scripts against APIs or using some third-party tools like Vagrant or Chef or whatever to orchestrate the automation, the deployment, the upgrade, the scale out and scale down of their application. And all that application management and automation happens on top of the standard OpenStack APIs and tooling. And that happens with VMware integrated OpenStack or with any other version of OpenStack that you're using. And the question really comes down to this cloud infrastructure team. And what technology is the right set of technologies for them to be able to deliver a world-class cloud to their application development teams? Because we already said earlier, right, those application developers, that software they're writing is what's differentiating the business, right? We need to provide them with great cloud infrastructure so that they can move quickly and build great applications. And so, all the way from the virtualization technology to the hardware technology to the tools that you use to operate, manage and troubleshoot, monitor that infrastructure, those are all decisions made by the cloud infrastructure team. And this is, of course, where a lot of the VMware technology plugs in. So, for example, we've done integration with NOVA so that I can talk to vCenter and ESX. Probably the number one question we get here is, hey, do I still get to use things like vMotion and DRS when I'm using OpenStack with VMware? And the answer is, yes. We've done this integration in a way that OpenStack actually deploys to a cluster and so DRS can still move those workloads around where you can put a host in maintenance mode and it will evacuate. So, we've been very careful about how we've done that integration in a way to preserve a lot of the capabilities that people love about vCenter. NSX is a networking technology that actually is independent of vCenter or vSphere. You can deploy it with another hypervisor like KVM, you can deploy it with vCenter, you can deploy it with a mix of the two. But NSX lets you create virtual networks with no requirement about controlling the physical networking hardware underneath so you can create firewall rules and load balancing policies and isolated networks all virtually via API calls. From a storage perspective it's actually very interesting what we've done here. So, from both a Cinder storage and a Glant storage perspective we've integrated with the vSphere APIs for storage. And what that means is that any storage that works with vSphere automatically works with OpenStack and vSphere. That means whatever third party storage you're already using in your vSphere environment, all of that, no need for a particular Cinder driver or anything like that. It all just works. There's any combination of vendor storage that you have. It all just works out of the box. Because Cinder volumes end up as VMDKs on top of vSphere data stores. And that goes the same thing with VMware Virtual SAM, which we'll talk about a little bit later. It's a way to take the disks and flash in your hypervisor hard drives themselves and creates virtual storage area networks out of them. And so whatever storage or combinations of storage you leverage with vCenter you can automatically run that with OpenStack and vCenter. And this is actually very important because a lot of the value our customers see is that they can take the production grade infrastructure that they have today and they can immediately deliver OpenStack on top of it in a way that they can run at production grade. They don't have to re-evaluate or re-validate a bunch of hardware or new systems. In terms of operations and troubleshooting this is something we'll get into later. We have a lot of tools on that side that help you run a cloud better. vRealize is a suite of products. There's vRealize operations, vRealize log insight for log analysis and vRealize business for charge back. All of these have been integrated in a way that can play very nicely with OpenStack on top of VMware. And obviously you can run whatever you want at this higher layer because we're just exposing standard OpenStack APIs. But one of the products we also offer through our sister company Pivotal up at this layer is Pivotal Cloud Foundry which exposes a higher level platform as a service for your developers who want to build applications using that model. And then of course you can get OpenStack yourself, you can get OpenStack from a user to get OpenStack from VMware all in this tightly integrated package and that's called VMware Integrated OpenStack. So hopefully this gives you an idea. Like I said, there will be many follow-up sessions that will dive into specifically NSX and all these other areas. This is intended primarily to be an overview. So one thing that I always, you know, people kind of want to, a lot of times when people talk about running OpenStack in VMware, they're very focused on what does my application need, which is definitely one of the features of OpenStack. It doesn't need HA, it doesn't need different storage capabilities, etc. But, you know, it's also very important to say, you know, think about the gap between what you need to run a tiny POC on and the gap of what you need to run a production grade system on. So I've got a couple concrete examples. I don't know if anyone, this is one of my favorite blogs about OpenStack. I've used this for a couple years but it's still as true today as when they just from a guy who basically ran eBay's OpenStack cloud. OpenStack is a starting point for building a cloud. It's not a cloud solution. And there's a whole bunch of these other problems you're going to have to solve when you think about an OpenStack cloud. And that's ultimately where you have to think about actually, you know, consuming a solution or building your own solution. And that's a choice that OpenStack provides. So a couple concrete examples. So I mentioned that we use view-realized operations. We use view-realized operations. It's a tool many of our customers already use to manage their vSphere environments. And with view-realized operations we've added OpenStack intelligence to it. And that means two things. So first off, the OpenStack control plan itself, right? OpenStack, when deployed for scale with high availability is actually a pretty complicated application in and of itself. So we actually monitor that application. We can tell you if it's healthy and we can tell you if maybe one of your Nova API nodes is down or your Neutron API server is overloaded or it's lost connectivity to your vCenter, et cetera. All of those troubleshooting tools we can kind of automatically embed them into that interface. Secondly, if a customer calls up and says, oh, I'm tenant, you know, Foo on the OpenStack cloud, I'm having a problem with one of my VMs. You can actually pull up based on the OpenStack tenant name. So you can see all of their VMs using their OpenStack identifiers. And then you can see how they map from OpenStack VM to underlying vSphere VM to the physical server it's on, to the physical hardware it's on and the health of all those items along that path. So we'll be giving a full demo of this tomorrow. Very, very powerful stuff to see. Similarly, log insight. It's not just about log collection, which to be honest with you isn't that hard but it's really about the log analysis and being able to provide a bunch of very meaningful dashboards and alerts, et cetera. So we've already baked a bunch of OpenStack intelligence into that. We run OpenStack internally for our own developer consumption. And so we've taken a lot of that learning and mindset and built them into these two operational tools. There's also, I just actually found this while Googling around the other. This is another, this is one of their own experiences using Vrealize log insight to solve. They talk about how they install, they talk about how they actually had a real issue in their environment and did some troubleshooting there. So I thought that was always like real-world customer examples. So that was interesting. This is another thing, so actually both of these are examples of using NSX. This was a customer who, you know, wrote a post about how they were doing some cool networking with NSX across data centers. But the real thing is, lots of different OpenStack solutions can let you do a demo that you create a network here, create a network there. What I really like about that picture on the right is that that's actually, so you guys have all seen the topology view in Horizon, right? This is what it looks like when you've got, you know, a network or two networks. This is actually what it looks like when you've got, like, I had to trim it, but I think there are about 1,000 networks in that setup, right? This is what happens when you're actually using OpenStack for something like CI, you don't have one network, you don't have two networks, you actually get hundreds and thousands of these things. And so that's really, you know, the advantage of NSX. It's in, you know, you have to think about how is this system going to operate at scale? What resilience properties does it happen if one of my gateway nodes fails, right? Or what happens when I upgrade? Do all my VM users lose networking connectivity? If so, they're not going to be very happy. So NSX has solved a lot of those key issues from upgrade to operations to troubleshooting. And it's actually now, I think, this was actually a couple months ago. There's over 400 customers running NSX or leveraging NSX right now. So that's very powerful, very very powerful and actually hypervisor agnostic tool. So you can run it with vSphere, you can run it with any hypervisor as well. So this is a good one. I think the VMware security team may kill me for that. So how many of you have heard about Venom? If you're running a KVM or a ZenCloud, I really hope you heard about Venom. It actually doesn't apply to VMware, but I'm going to use it generically here anyway. It's a super scary security bug that was discovered very recently. Basically it means that someone who's inside of VM and should be isolated from everyone else can actually break out into that hypervisor and potentially break into any of the other VMs on the server. And depending on the security at your hypervisor layer could break into other hypervisors as well. So very scary bug. You can't patch this one soon enough kind of bug. But if you think about if you're a standard cloud, what are you going to do? Are you just going to immediately take down all your tenant VMs? Probably not. People talk a pretty big game about all my VMs, all my apps are cloud native. I'll tell you, even GCE for example doesn't just take down all your VMs, even Amazon sends you an email and kind of gives you some time to manage it. GCE actually has its own live migration capability now built in to help avoid these reboots. So even these more modern applications care about this type of stuff. And so this is actually something that's borderline trivial in a VMware environment. We have a combination of maintenance mode which evacuates servers combined with something called the VMware Update Manager which can automate the rolling patching of those servers. So this is just another example. Probably not the first thing you thought of when you were thinking about what platform do I choose for OpenStack, but a very important one that affects very fundamental security properties of that system. And again I'm just going to state for the record, this was not a vulnerability in ESX. Just kidding. For my own legal protection I'm saying that. Another cool thing, storage is another thing in OpenStack. It's easy to just think, well, any storage works in VMO, right? But then you have to think about, well how am I going to tier my storage? What different offerings am I going to have? So with OpenStack and VMware you have something called storage policies. Makes it very easy to create different tiers of your storage. Maybe my databases need lots of IOPS. Maybe this other thing is just for logs, so who cares. I just want cheap storage, etc. And so as I mentioned, any storage that works with vSphere or OpenStack and vSphere, this slide in particular is diving into VMware VirtualSan, which is kind of on this trend toward commodity storage where you can actually take disks and flash that exist in the hypervisor. And you don't have to manage a separate storage subsystem. It will actually aggregate them and let you give basically different levels of performance guarantees on a per workload or per disk basis. So you can, for example, I said you can have different tiers of storage. You can have a different type of storage, but you can also have a different type of storage. So I'm going to talk about the top numbers that have come out of here. We're talking over the 64 node cluster that's now supported in vSphere 6, you can get millions of IOPS even in well-tp mixes. The top number is just kind of random read. The bottom is a mix of I think it's about 70-30 read-write. You can get some of those as well. So that's a pretty big deal. So you can choose a hybrid mix of spinning and flash, or you can choose all flash. And, you know, as I mentioned this is all managed from vSphere in a way that's integrated with all those ops tools that I showed you before, makes it a very simple, cohesive system to manage and leverage. So, you know, just to go back, you know, I wanted to circle back and talk a bit about VMware integrated OpenStack. So everything I've said today, right, like I said, you could use VMware integrated OpenStack, or you can use VMware integrated OpenStack. You have to figure out what the right tradeoff is for you. I was just specifically talking about the VMware product, VMware integrated OpenStack. So what we do there is we basically take, you know, you take your existing vSphere environment, VMware integrated OpenStack is a combination of the upstream OpenStack code, right, with the VMware drivers enabled, and us having figured out a reference implementation of deploying the control plane, again this is all deployment. So we've got a lot of experience from a very practical experience with this stuff. With integrated tools for managing, installing, upgrading, how do you apply patches, how do you do rolling upgrades, how do you add a cluster after the fact, how do you add more compute capacity, date two things, all that integrated into a nice package that's very familiar to someone who runs a vSphere environment all day. And then, as I mentioned, integration and it's optional integration into these additional cloud management solutions. And then we wrap that all up in this validated architecture and we provide a single contact for support. And that single contact for support is actually probably more important than you might think. I mean, if you think about, you boot a VM, it fails to come up, it's in an error state. It's not at all immediately obvious, not immediately obvious and maybe after hours of looking at logs, right, was that problem actually in vCenter or maybe with their storage that's backing vCenter or maybe it was a problem with the Nova driver or the Nova scheduler, right. So having a single support contact there actually makes it much more fluid in terms of going from issue to resolution in terms of OpenStack. So, let me see how I'm doing on time. I'm gonna, yeah, let's do it. Let's see. So I'm gonna click out of here quickly and I'm gonna pop over and just, so there'll be a full demo of this. Like, tomorrow I'll show you, I just want to give you a little taste of of deploying VMware integrated OpenStack. So basically, again, the idea here is that any VMware admin this should be very, very familiar to. And so, you can see basically what happens is you download a virtual appliance, a single virtual appliance to start, you deploy it and you see this little icon showing up, this VMware integrated OpenStack icon over here. So you can click on that and I click deploy OpenStack. It basically takes you through a wizard. Now, since I don't actually, you don't want to sit here watching me fumbling and type the whole time. I'm just gonna import a template here, which is one of the ways to deploy it, but I'll take you through each of the screens that you'd used to deploy in. Again, we'll go through this in more detail tomorrow. So this is really more just an example. So first off, I have to point to my vCenter, right? What vCenter am I gonna use to back this deployment? Then I'm gonna first pick a cluster where I want my VMs for my OpenStack control plane to be deployed to. These are my Nova servers and my Neutron servers, et cetera. So I just pick a cluster, use that. I'm gonna select the networking that I want to use for that cluster. So there's two network ranges. Configure where my load balancer is, right? Because this is a production-grade OpenStack cloud, you're gonna want a load balance for high availability and scale out. It's an inbuilt load balancer, so it's really, it's very simple to deploy. We just deploy it with everything else. Then I can pick one or more clusters that I want to add as my compute capacity, right? Where are the tenant VMs actually gonna land? Right? And then when they land, well, what data storage do I want them to consume their storage from? And we've made it very simple for Glance. Glance can actually just use a vSphere data store as a back-end as well. So you just pick what storage you want to use for that. Now for networking, we've got two different modes. You can use a basic VMware VDS that's built into vSphere, and you can use NSX for full-fledged neutron networking. In this example you see I've populated a couple things, describing how to connect to my NSX manager, what cluster of capacity I'm gonna use for my gateways. So I think in the same room after this is a whole deep dive on NSX, you'll understand what the gateway is by the end of that. Right? You know, for Keystone, right, where am I gonna get my users from? Either local database, or I can point to use LDAP to point to an server. Right? Optional can configure syslog, like a vRealize log insight, or any third-party syslog server. And that's it. So here's all my config, and I can just press finish, and this is sped up, depending on how fast your vSphere storage is, that we're cloning all these VMs onto. I've seen it as fast as about 15 minutes, and as slow as about, you know, 45 minutes well, maybe in a nested environment, or even a little slower than that, but basically it's all depends on, we're just creating VMs and cloning them. So you can see here, and then, you know, if you refresh, right? Nope, now I've got a running VIO instance, and if we click into that, you can see what we've done is we've automated the deployment of a fully integrated, full-scale out, highly available OpenStack control plane as VMs. And so at this point, right, you are more likely all of your cloud tenants, right, can then just use Horizon, or use whatever other tools they want in order to consume OpenStack capacity. Over time, you can add more vSphere clusters or more hosts to those clusters if you need more capacity. So again, very simple, very straightforward for a vSphere admin to deliver OpenStack services to their development teams, and that's really our goal. So just a couple more slides. You know, again, going back to that original core value prop that we talked about, right, it's about these open APIs that developers like on top of this really powerful, reliable OpenStack, sorry, VMware infrastructure that your IT operations team already knows how to run at production grade. And one of the cool things, I don't know, hopefully most of you are at the keynote, you heard about the interop stuff, but there's been a lot of fantastic work by the community to find these rules for OpenStack interoperability. What does it mean to implement the OpenStack APIs properly? So it's very fundamental to the core OpenStack vision. And so there's this thing called Defcore, and we've been very involved. We've got a guy named Mark Volcker from our team who's one of, you know, contributes a lot to that project. And so we're very proud to say, you know, on day one of this announcement, VMware integrated OpenStack is fully compliant in terms of the OpenStack interoperability requirements. And so this is a screenshot. If you go up to the, you know, the OpenStack marketplace you will see that little tested icon. What that means is we have proven through the battery of tests to show that we are fully interoperable from an OpenStack API perspective. That's very fundamental to the commitment VMware's making to our customers that we are implementing standard OpenStack APIs on top of our infrastructure. Not some VMware variant of OpenStack or anything like that. They're fully compliant with the OpenStack standard interoperability definition. So I'm very proud of our team and all the work they've put into not just building the product, but actually using that validation as well. So as I promised I'm going to wrap up. But this is our couple, I'm going to give you a couple slides of places where you can go to learn more. These are all the sessions at the OpenStack summit that are still to come that are related to VMware. How many of you were at the Adobe session just before? That was a great one. You just missed it. So Adobe is one of the early customers using VMware integrated OpenStack. I'd encourage you to go watch the video because that one already happened. So I can't tell you to go there. But we've got a set of sessions. Later today we've got NSX in this room. I think it's the same room. Yeah. And then tomorrow, basically mid-day, we have a set of three sessions in a row that we'll talk about. First it'll be a customer panel which I think I have a dedicated slide there. So it'll be Franz from Adobe again. It'll be Prashant from Wells Fargo and Peter from Nike talking about their experiences with OpenStack running on top of VMware. So I'd really encourage you to check that out. A couple other sessions that will be one deep dive demo that takes you through that whole installer and the operations experience as well. So that's a very powerful thing to see. And then, you know, for once you go home, this is where you go home to download it. So once you go home, you can download it. Like I said, any VMware customer can download and use this for free. It's available via the VMware website. If you want to come by, you can use both chat, ask questions. We can give you a full demo there as well, one-on-one. A couple other areas. So VMware has these things called hands-on labs, which are just amazing. It's actually a full, you know, mini little cloud running OpenStack in VMware. And you click a button in your browser. We spin up in our internal cloud and you can access and poke around and you're driving a real VMware integrated OpenStack installation. So that's available at any point. On that website, it's available. So it's very cool technology. Also starting, I think starting next week, there will be a three-hour, I think it's three-hour about full OpenStack training targeted for VMware administrators who want to get up to speed on OpenStack, learn more about OpenStack. And then there's a whole community that you can actually ask questions and it's a forum. And then obviously you can follow us, you can follow our blog, you can follow us on Twitter as well. I just wanted to wrap up. I just wanted to say we've got some snazzy. We've got OpenStack, Summit, Vancouver and VMware. Hoodies up here if you want to come up. And with that, I'm happy to take some questions. Please use the microphone if you could. Thanks. Hi. Can you hear me? Yeah, thank you. And just if we are installation on this sphere and this center is all version 5, can we start using this or we have to... Version 5? Yeah. 5.5. Just 5? 5.5. So it's a 5.1, so yes you can. Oh, 5.5 you're golden, man. Yeah, you're good, you're good. So basically the question was what vSphere versions... General rules, if you're 6.0 or 5.5, you're golden, don't worry about it. If you're 5.1 or older, come talk to us. There are some ways that I can work with. There are also some caveats that I wouldn't want you to trip up on. Yep. I'm curious about where is vCloud in all the stuff that you mentioned? Should we consider it that? VCloud? Yeah. VCloud Director? Yeah. So vCloud Director actually is already a product that is no longer being offered to enterprise customers. That actually happened well before we announced VMware Integrated OpenStack. So what there is, is there something called VRealize Automation, right? Which is another kind of... I would say it's another kind of solution, more targeted at enterprise IT self-service. Whereas OpenStack is more the kind of the AWS style, very developer, API driven, driven type of a cloud. VCloud Director is still obviously used for our service provider partners though. But in terms of orchestration or automation, what VMware will push from... I mean, if I'm a customer and I approach VMware saying, listen, I want to build a cloud, what do you guys will offer? You guys will offer OpenStack as the choice for orchestration or automation later. At the end of the day, cloud is a generic enough concept, there's not going to be one offering that's right for everyone. The key thing to realize about VMware Integrated OpenStack, right, as well, we have a set of customers who are interested in consuming their infrastructure via OpenStack APIs. We as VMware say, great, we want people to consume our infrastructure or however they see fit. VMware Integrated OpenStack is a way of enabling OpenStack consumption on top of our infrastructure. The same way we've created the Cloud Foundry product and we created a product and spun it out as pivotal way to consume our infrastructure as Cloud Foundry. We have products to make it easy to consume our infrastructure as Hadoop, et cetera. Particularly, I didn't mention this, but I don't know if any of you have seen the announcements around the container stuff, but VMware just announced two open source projects, one in Lightwave. I encourage you to check them out. This is my team as well, so I had to try to get a plug-in. But again, containers, great. We're embracing different ways of running containers and we've got to love to have discussions about our customers about why we think containers run best on top of VMware infrastructure. Any other questions? Cool. I appreciate it. Take care. Come up and get a hoodie.