 So as it says up there, my name is Dan Wellent. I had up OpenStack product and strategy at VMware. I came to VMware through the NYSERA acquisition. So my background is in networking, but as a result of the NYSERA stuff, I've been at every OpenStack summit since the Austin one. So it's always fun to see the new summits as they get bigger and bigger and bigger, and the keynotes get fancier and fancier and fancier, and suddenly you've got these badass cars in the keynote. It's fun to see how this has grown over time. What I'll be talking about today is just a general overview of OpenStack and VMware, and we won't get into the nitty-gritty technical details. We had some sessions yesterday that did that, and I'll tell you what those were, so you can watch them online if you want. But we'll cover kind of high-level way VMware looks at OpenStack, what we're doing around OpenStack, how different VMware technologies fit into OpenStack. We'll do some quick video demos at the end to give you an idea, and then we're happy to follow up with you in more detail. So if you're a VMware customer and you've ever talked to a VMware sales guy, you've probably seen this slide, so I won't spend much time on it. But VMware as a company is focused on delivering IT outcomes in a way that gives you CapEx reductions, OpEx reductions, gives you good security, gives you good availability for your applications, and lets you improve your business agility. And obviously OpenStack is typically more focused on the bottom end of that market. It's about giving APIs, giving you tools to let your development teams move faster, automate the provisioning of your IT applications. But in an OpenStack cloud, it's important to kind of keep the big picture and remember that OpenStack, unless you're achieving all of these things, likely doesn't really deliver on your full goals. So VMware, our philosophy around how to achieve this is to build something we call the Software to Find Data Center, which is just a software abstraction layer that can go on top of any hardware across compute, network, and storage to virtualize those resources and let you automate and consume that infrastructure. And traditionally VMware is well known for its industry leadership in terms of these traditional scale-up applications, things that need high availability, disaster recovery, really good SLA, strong security, etc. But in the past couple years, we've really started also investing heavily in kind of this next-gen or third-platform application space. And typically the requirements there, they expand because it's not just about you manually provisioning an application once and having it never go down and maybe upgrading it once a year. Suddenly there's people talking about dynamically expanding their applications and doing continuous integration, moving them up and down. And you really are talking about a world of these more modern applications where people want to programmatically talk to the infrastructure. And when you programmatically talk to the infrastructure, that's where these APIs are very important, these APIs and frameworks. How do the developers, the people building and deploying these applications want to think and model that infrastructure? So there's all types of new frameworks for how to do this. There's Spring and Hadoop for certain types of applications. There's Cloud Foundry if you're looking for something that's more at a higher-level pass. And there's OpenStack if you're looking for infrastructure as a service. And you've probably even heard now about things like Docker and Kubernetes. Again, if you want that model of interacting with the infrastructure, VMware is working to make sure that all of these systems run well on top of VMware software to find data center infrastructure. And our basic philosophy around that is three-fold. So first off, you'll notice that a lot, in fact, most of these developer-oriented frameworks are open source, or at least open standards. Some of them, like Cloud Foundry or Spring, are things that VMware created and open sourced. Others, like OpenStack, Docker and Kubernetes are things other people created and open sourced, and we recognize those good ideas and decided to leverage and make sure they run well on our platforms. But in general, because these are developer frameworks, people want to know that they're using a framework that isn't tying them into a particular underlying vendor. And so typically, these are open source, or at least open standards. So VMware's philosophy around this is three-fold. First off, we contribute to the open effort. We'll talk about in more detail later how we're contributing to OpenStack. We then basically integrate our technologies in a very deep way such that the differentiation VMware provides across compute, network storage and management is something you can realize when you're running OpenStack or Hadoop or Cloud Foundry or whatever. At the end of the day, we have to be able to convince you that there's value in running OpenStack on top of VMware versus OpenStack on something else. And then thirdly, we work to enable. We try to make it easy for our customers to be able to leverage these new kind of developer-oriented platforms on top of VMware infrastructure. So often what that means is packaging or other working with partners or building our own solutions that incorporate these, make them easy to deploy on VMware infrastructure, integrating them with VMware management tools, et cetera. Okay, so that's the last kind of 10,000-foot slide. First off, I just want to give a little background in terms of how we think about OpenStack. So, you know, our view of OpenStack is that it's a framework for providing developers with these Cloud-style or Amazon APIs on top of their choice of underlying infrastructure. So effectively what you have is you have a team who's developing one of these new Cloud applications and they need access to resources because that's what their application consumes. But they don't want to have to worry about the individual details of VMware hypervisor, this is HP hardware or anything like that. So what you want to do is you want to abstract those resources using, you know, good, cloudy abstractions and let them automate against them so they can build their own code, they can write scripts against the APIs, they can build their own tools against APIs, they can use third-party tools. Well, the thing that's in common is that they're using these programmatic calls to talk to the infrastructure. They're saying, provision my workload, scale my workload up, let me deploy my workload with a new version. Again, it's all about this programmatic access to the infrastructure. And so if you look at where we've seen customers be successful with OpenStack, it tends to be in these types of applications. You know, could you technically run a traditional IT application on OpenStack? Quite likely. But the point is, is there all that much value to it? Well, often if, you know, it's an application you deploy once and ever touch again, the fact that you have programmatic APIs that isn't all that interesting. But in cases like this, we have a scale-out web application or build-dev-test continuous integration. The ability to have this dynamic way of interacting with the infrastructure is fundamental to the application. And that's really where OpenStack provides a whole new set of opportunities for how you build applications. Another area we've seen a lot of interest in OpenStack with our customers is around things like analytics or batch workloads. When data comes in, you spin up a bunch of jobs, you know, they process the data, they dump it somewhere, they're done. It's this very dynamic environment. And so that's really where we see the vast majority of our customer interest in OpenStack. Again, focused around programmatic consumption of the infrastructure. And so, you know, when you're thinking about OpenStack, how does it relate to different technologies, whether they're VMware technologies or someone else's technologies? Well, you really end up having a full stack of applications on top of OpenStack. You kind of have the application management and automation layer above. This is where your application team is building their own code, writing scripts, using heat, using some other third-party tool to define and run and revise their application. OpenStack provides a set of tools, provides SDKs, CLI, a GUI, if you're not actually automating, all built on top of a standard set of APIs. See what I told you about my hands? I come in and out of the microphone. It's hopeless. So, and then, you know, these standard APIs, they layer on top of infrastructure. And OpenStack, as we mentioned earlier, gives you a choice of that infrastructure. So, it's really important to understand these two different personas. There's the application DevOps team, right, who is worried about building, deploying this application. And they need to, we want to give them standard OpenStack APIs and standard tools that they're decoupled from the underlying infrastructure. And the people running the infrastructure, the cloud operators, they need to worry about what virtualization technology, what hardware technology, what set of operations and tools and management do I need to effectively run this cloud so that it meets the requirements of my application developers. And so, as we go through the talk, we'll talk consistently about cloud application developers and cloud infrastructure operators. And it's important to keep those two personas in mind. And obviously, VMware has technologies that fit in here. This will be a slide that shows all of our technologies and where they fit in. But obviously, depending on your cloud, you can choose to consume them as components. So, we've integrated vSphere Compute into NOVA for the Compute API. We've integrated NSX for networking into the Neutron API. And we've done integrations with Cinder and Glance for storage and image APIs so that any storage you use with vSphere already will automatically work with OpenStack and vSphere. No changes required. No requirement from that vendor to have done a specific OpenStack Cinder driver. And of course, that also means VMware's virtual-sand technology just works out of the box as well. Because that, just like all of our storage partners, uses the same set of underlying storage APIs. On the infrastructure and operations side, we have tools like vRealizeOperations, LogInsight, and IT Business Management. We'll go into more detail later exactly what problems those tools solve. And then at a higher layer, obviously your application development teams can write their own tools, they can get third-party tools, but there's also VMware tools that are OpenStack compatible if you choose to use them. So there's vRealize Automation, which gives you higher-level application management tools, policy, governance, all of that. There's things like Pivotal Cloud Foundry that you can deploy on top to your developers. And lastly, so I apologize all of you have taken pictures of the incremental build. I should have told you which the last slide will be. You know, you can get OpenStack, you know, you can do it yourself, you can get it from third-party vendor, but at VMworld, VMware announced that we'll also offer our own distribution of OpenStack called VMware Integrated OpenStack for those of you that are looking just for kind of a very simple, easy route to running OpenStack on VMware. And we'll talk a lot more about that at the end of this presentation. So again, one of the key points I want to make very clear here is that going back to those two roles, people often ask, well, would I use the vCenter GUI for OpenStack or would I just use the OpenStack API? And the answer is that you're cloud developers, right? They're above the OpenStack API. They need abstract and generic tools that aren't tied to the infrastructure. They would use things like OpenStack API, CLIs and tools to provision and manage their workloads. It's the cloud operator, the person running the underlying infrastructure, the person troubleshooting, adding new capacity, upgrading, et cetera. They get to continue to use those familiar and very robust VMware management tools that they already know and understand, and they can leverage those to run the cloud. So that's kind of where you get to the really core value we see when our customers are using OpenStack, is that their developers want these new cloudy kind of Amazon-like APIs that OpenStack gives them. They want to be able to build their apps with that type of a model. But you have IT infrastructure people who know the power of the VMware platform are very familiar with the tools and want the capabilities it provides to let them run high quality infrastructure. And if you take those two together, what you get is a very powerful combination. You can enable your developers with OpenStack very quickly because your infrastructure operators aren't being forced to learn new tools across compute network storage and management. They can use the tools they're familiar with to deliver a production-grade OpenStack cloud very easily. So for the rest of the talk, we'll kind of use those three areas that I called out earlier to deep-dive in a little more. How VMware contributes and is a major contributor to the OpenStack open-source project. How we differentiate. And obviously we won't have time to get into nitty-gritty details of every little feature on a high-level. Why is vSphere a great hypervisor at OpenStack? Why is NSX a great networking solution for OpenStack? Finally, we'll talk about how we enable it. The different options we're giving our customers to leverage and run OpenStack on VMware. So first off, contribute. So as I mentioned, the history of VMware's involvement in OpenStack actually goes back quite a long way because it was the NYSERA team who was later acquired by VMware that's where I came from who we created the OpenVswitch project back in 2009. OpenStack was founded in 2010. And as I mentioned, we were part of that from the very beginning. And as part of our work on OpenVswitch and with OpenStack we actually created and led the OpenStack, what was used to be quantum back when I was the PTL and it's now called Neutron Project. And so we've led that and we continue to be a major contributor in that project. In 2012 NYSERA joined the VMware family and as a result of that VMware joined the OpenStack foundation as a gold member. And as part of that, you know, at that time I'll be honest, there are a lot of people who are pretty skeptical about what VMware was going to do with respect to OpenStack. It's kind of funny to go back and read those articles now people were saying that we were going to undermine OpenStack and all this stuff and what we did is we said we committed to saying not only are we going to have the NYSERA contributions continue but we're going to expand and integrate all of our technologies into OpenStack. And if you look at what we've done over the past years that's exactly what we did. Starting in 2013 we integrated vSphere into the NOVA Compute project we integrated vSphere storage APIs with our storage ecosystem into the Cinder project. We also started partnering with key members of the OpenStack ecosystem who are starting to have customers that said oh we have customers who want to run OpenStack on vSphere and OpenStack with NSX work with us, validate our OpenStack distributions with your VMware technology components. So in 2013 we announced partnerships with Canonical Morantis. Every year we continue to get involved in more and more projects. We've done glance integration we've done salameter integration we're even starting a new project with other members of the OpenStack community called Congress which is about creating and enforcing policies across projects. For example if you have business rules that you want to make sure are enforced for example workloads with this only workloads with this security-valid based operating system are allowed to be exposed directly to the internet those types of things Congress can do that we've also continued to expand our partnerships we've partnered now with SUSE and Red Hat and HP. Again all these people are seeing customers who want to run OpenStack on vSphere and OpenStack on NSX and these partnerships help enable that and then at VMworld this year we announced VMworld integrated OpenStack which is kind of a well integrated VMworld offering that gives our customers another option in terms of how they want to consume OpenStack and we'll talk in more detail about that later here are some numbers I mean the individual numbers and these change ever release in the Juneau release where the sixth largest contributed to core projects we're always in about that ballpark this is just the individual numbers don't matter we just want to let people know that VMworld is deeply engaged in the OpenStack community reviewing code, contributing code submitting blueprints helping make sure that OpenStack is a great platform for everyone to have kind of a generic set of cloud-aware tooling to build their applications so moving on to the second area around how VMworld integrates its technologies to have a good story about how OpenStack runs based on VMware one of the important things and typically the discussion we always try to have with our customers is to say what are all the ways in which the technology you choose affects your abilities successfully run a production cloud at scale with good lowest total cost of ownership how are you going to troubleshoot how are you going to secure it what type of availability do your applications need does the application really not care if someone just kills it and spins it up somewhere else or do those applications need high availability and these are the discussions the answers from every customer are different but this is always where we start out the discussion because too often people don't think about kind of the big picture when they're starting out their initiative and they kind of can paint themselves into a corner if they're not thinking about all the things they'll need to successfully run an OpenStack cloud so obviously across the core compute network and storage I could talk and some of you have seen me probably talk and now we're on each one of these so I'll try to cover them pretty quickly around vSphere compute we've integrated that into Nova vSphere is the industry standard hypervisor for reliability, performance security has a great track record very battle hardened also has a set of very rich features things like vMotion, DRS, high availability really good isolation resource protections to prevent noisy neighbors low latency capabilities if you have apps that are very sensitive to jitter, the list goes on and on and on probably the most common question we get about our integration is around things like high availability vMotion, DRS people are saying if I use OpenStack with VM I still get those right and the answer is yes, we've been very careful to integrate with Nova to preserve those capabilities the last thing to mention about vSphere that's very important is all of the additional management tools we have in order to make it easy to add capacity and troubleshoot and get alerts and logging and this and that there's been years and years and years of that built into the platform and when it comes to actually running and operationalizing OpenStack cloud that's very important on the NSX side for Neutron I think there's been a long history of NSX which used to be the NYSERA MVP platform and it's involvement in OpenStack, it's been battle hardened again it's been in production in customers as large as Rackspace and eBay for over two years now in fact probably close to three now it provides a very rich feature set in terms of multi-tenancy and firewalling and segmentation it works across multiple hypervisors that works across ESX, KVM Zen server has very advanced network services like load balancing VPN etc and we work very closely with all of our ecosystem partners we have a great great set of NSX ecosystem partners so that if you want a firewall or if you want a load balancer from F5 if you want to integrate some workloads that are on physical Arista switches we can work with those and tie those all together to a single set of logical networking fabric that let you dynamically consume networks without having to talk to your networking team and say oh I need another vlan for this application, that application it's all virtualized, it's all pulled up so it's not just that you can provision VMs on demand, you can provision networks on demand as well on the storage side for Cinder and Glance as I mentioned earlier any storage that works with vSphere will work with OpenStack and vSphere this includes the ability to do all the array acceleration that vendors have done with the vSphere platform to date includes the ability to use storage policies so you can really easily create different tiers of storage my high IO storage, my cheap storage my storage that's backed up 30 days my storage that's backed up 2 days we have customers who have all kinds of very rich storage requirements and it makes it very easy to map those to different Cinder volumes or different NOVA instance types that then map to different storage and VMware has something called virtualSAN which is our way of taking commodity disks and flash in the servers and creating what's effectively shared storage out of that and so if you're interested in that you can check out this link which is a performance study that we had a third party do against comparing to Red Hat storage and showing that actually VMware storage was both very performant and was able to be cheaper because the storage was actually converged on the hypervisor versus requiring dedicated storage appliances so that's a good question the thing is in a cloud abstraction the tenant shouldn't have to think about vMotioning their host their VM should just have an SLA like it doesn't go down so the vMotion in this case would be more done by a backend operator for example if the operator was taking that host out of commission or doing maintenance on it that's a good question you start it within the the actual vSphere client because it's an operator action so I don't know if any of you have seen this blog I would highly suggest you check it out the links down below but you know it also talks about beyond the kind of core compute network storage what are all the problems you need to solve when building an open stack cloud because it's much more than just the core open stack services you need to deliver and all these if you don't have solutions that take care of them it'll end up sucking up a lot of your time so you know vMware has two major advantages in this point first as I mentioned you get to leverage all of your existing build-outs in terms of how you build infrastructure your teams existing experience and your teams existing tools in fact as having a customer discussion just on Monday had a great example of this they were talking about how they use HP hardware and HP's already integrated you know it's own plug-in into vSphere such that when you roll in another rack of HP hardware it just automatically gets created as a new cluster you know if you ever have to do upgrades on it for hardware for bios flashes or anything like that it just automatically goes host by host by host shuts them down vMotion the vM off so just all of those existing rich tool sets and experience that your team has can really help get around a lot of those operational problems you would have if you otherwise kind of started net new on a new platform so this is something that can really help you get open stack to production grade very fast by building on your teams existing capabilities the performance validation they've done the troubleshooting tools they've built etc the other thing is there's also a set of cloud management tools we have there's a new branding name called vRealize that all of these tools use I'm not a marketing person so I won't tell you what I think about that but there's a tool called vRealize operations which is for troubleshooting and capacity planning monitoring etc and what we've done with each one of these tools is we've kind of added open stack awareness to them so for example vRealize operations will not just monitor your traditional vMware infrastructure it'll also monitor your open stack control plane and tell you that oh you have a problem your nova API servers are running down or you know hey your nova scheduler is running at a very high CPU rate for a long time something's probably wrong you should look there and it also helps with troubleshooting for example I can you can pull up a view where you directly see the links between open stack entities like cinder volumes the data stores there on in vMware and the underlying physical hardware that that corresponds to so it really enables very very rich tools for troubleshooting loginsight is a tool similar to Splunk for log collection analysis search and alerts and again we've built open stack awareness into that so there are management packs not only to help you manage your vMware infrastructure there's actually pre-built integration to process open stack logs collect common problems like common errors out of there create charts and graphs for you to use to again make it very easy for you to operationalize an open stack environment and then finally there's IT business management which provides you cost visibility it models what the cost to deliver certain cloud services are and then helps you view who's using them and do show back and charge back if that's something you need and we have a way that actually integrates with Keystone so you can see on a per open stack tenant basis how much resources they're using and how much that's costing you finally enable this is about how do we make how do we give our customers options in terms of how they want to consume open stack so our goal with open stack we talked earlier about all the different partners that we have and you can choose to download the open source bit yourself you can choose to work with a third party distro and now vmware is giving you kind of a third option which is this vmware integrated open stack and the goal with vmware integrated open stack is to make it very easy and very fast to get to a production grade open stack environment on vmware so this isn't the tool for any for everyone but if your goal is to say what's the easiest way for me to enable open stack apis and tools for my developers on top of vmware infrastructure this is a great place to start so as I mentioned we continue to work with all of our ecosystem partners and here's the list here if you want to go take their third party distros and integrate vSphere and or NSX into them you know well how it works is that these companies support the open stack layers and vmware supports the underlying components the real difference with something like vmware integrated open stack is that it's it's kind of a more tightly coupled but therefore kind of single single point of contact solution so you can start with your existing vSphere environment you add vmware integrated open stack which is a validated reference architecture for open stack and we've given you tools to automate the deployment of this entire scale out HA open stack control plane as vm's into an open stack cluster I'm sorry you can do a vmware cluster and you can see here that there's actually tools integrated directly in the vSphere clients to do this to solve that for install to solve it for upgrade and so it makes it very simple to deploy open stack which is kind of step one but we also have all of these tools that I talked about earlier and I'll pre-built integrations in order to give you really the tools to continue to operate that environment at production at enterprise grade and so we wrap this on we test all of these components together to make sure that all the versions work together and everything's compatible and we provide you a single support contact because the reality is often if you boot a vm and there's a problem it's very hard for you as an end user to know is the problem in open stack is the problem in the underlying hypervisor you know open stacks talking to the underlying hypervisor it's very difficult to know that until you've actually gotten to the bottom of the problem so for a lot of people having this single support contact for any problem in the stack is it can be very valuable so with that I'm going to actually pull up just a quick really quick demo so we actually had a full 40 minute session yesterday a deep dive technical demo and that's all recorded so I'll show you that session later if you really want to get the details this is just a quick minute and a half kind of overview that I'll just talk to quickly so to do VMware integrated open stack you just get a single OVA and you download and you deploy it to your vSphere cluster and you can see in the upper right you see that VMware integrated open stack icon pops up then and you can click on that you can just click deploy open stack and what you'll get is a wizard that takes you through and asks you for what IP addresses do you want to use on your open stack cluster etc what compute clusters do you want to use for open stack capacity then it deploys the entire open stack control plane as virtual machines in a scale out highly available way so then your end developers just get a horizon GUI or the CLI tools and can use them just the same way they use any open stack distribution remember your cloud tenants just get those standard open stack tools but because they're running on rich technologies like NSX they can create rich multi-tier applications very easily at the same time use an operator of the infrastructure get to use those VMware tools so we've added for example open stack awareness of the vSphere client so you can search on open stack tenant names and immediately see the VMs that are relevant to them this is vCenter operations I mentioned the relationships between open stack objects and the underlying infrastructure this is an NSX troubleshooting tool if you're having network connectivity problems this is log insight again that log collection aggregation data analysis platform that has built in open stack integration as well so again we have a full deep dive demo that actually talks you through each one of those examples and I strongly encourage you to check it out but hopefully that was just a little something to give you a bit of a visual idea of what we've been doing so this product is now in beta it will go GA vSphere this is the link if you want to go learn more about the product or sign up for the beta I will caution you we've had an unbelievable number of people requesting access to the beta so we really aren't able to fulfill and respond to everyone but we are particularly prioritizing people who have a near term production plans around open stack so if you have that please let us know that you're interested in the beta and we'll hopefully be able to follow up with you soon so one other topic I wanted to touch on is sometimes people say okay great I've got it you've got this platform it makes it really easy to use open stack on VMware technologies I can get my developers open stack at production quality very quickly but everything you've said so far is about VMware and running on VMware hypervisors does that mean I'll never ever have the ability to run on another platform like KVM and the answer is no you will still always be able to run additional technologies now VMware will not directly provide commercial support for those technologies you'll work with our partners in terms of you know someone who delivers and provides support for KVM but what I'll show you here is a way that you can make them work together really nicely and effectively provide your team with what appears to be a single open stack cloud with two chunks of capacity one that's an open stack chunk of capacity or sorry one that's a VMware chunk of capacity and one that's open stack on for example KVM or Hyper-V so to show that in a little more detail if you just deployed VMware integrated open stack this is what you'd have VMware integrated open stack with the standard open stack APIs that your developers interact with but you can also deploy open stack from some other vendor we're using some other hypervisor and again as long as that vendor supports the standard open stack APIs what you can actually do is federate Keystone and use the same identity server across these two clouds so your end users only have one set of credentials can log in once and you can actually even use a shared horizon portal so there's only one portal they need to go to to provision so let me show you a quick demo that we put together on this this is just using a little POC environment you'll see from the size of the hypervisors but it gives you an idea so here you are logging into the console and as you expect you log in there and you see the same standard open stack dashboards and you can look at your hypervisors and here we see we have one cluster of VMware capacity with 32 CPUs and about 250 gigs of RAM again this is all standard VMware integrated open stack that you would see I can click on instances and see that I've got a bunch of instances spun up and they've landed on that VMware cluster so this is where it gets interesting so what I can do is I can go up to the top and actually select a region I can go and I can choose oh well this cloud also is running a KVM region and so if I click on that again using the same user credentials the same portal I can then look at my capacity in the KVM region I can see that I've got another VM with the same image running but if I go and look at the hypervisors this hypervisor is actually of type QMU which is the KVM hypervisor type so again what this shows is as long as what you're using is an open stack solution whether you did it yourself whether you bought it from a vendor that uses standard open stack APIs you can actually use tools like VMware integrated open stack and use them in a very right along side tools from other open stack vendors in a way that's still quite seamless for developers because at the end of the day that's what really matters you want to make sure that your developers get a consistent set of APIs and tools to deploy and manage their workloads so before we wrap up I just want to talk a little bit people often ask me okay well where's this going what's next for VMware integrated open stack and there's three different areas in terms of how I think about our roadmap so the first is how we interact with the open stack community as I mentioned improve and integrate our technologies into open stack we can continue to add new things from a community perspective like congress or new APIs and neutron and with each open stack release that comes out we'll offer a new version of VMware integrated open stack that corresponds to that upstream open stack release after we've had time to harden and test and validate the open stack release in addition to open stack releases VMware technology all the time vSphere 6 is coming out early next year it's going to have a bunch of really cool new features well we want to make sure that you can leverage those really cool new features like virtual volumes and fault tolerance and long distance vMotion in an open stack context so that means we're improving the drivers adding support for these new VMware features in vSphere in NSX you've heard about what we're doing with Evo Rack which is a new converged infrastructure play we'll be looking at adding support for open stack for VMware integrated open stack with Evo Rack and the third area that's very important of VMware is our partners we'll continue to make sure that all of the work our partners have done to integrate with the vSphere platform is work that can be leveraged within VMware integrated open stack I talked a lot about storage partners earlier there's also networking partners like Palo Alto Networks Rista F5 making sure that you can use their technologies inside of open stack in VMware people like Pivotal who we're obviously very close with and we work closely with to make sure that their cloud foundry can work well on top of VMware environments and there's other open stack partners like Canonical, Morantis, SUSE, Red Hat, HP in that scenario we just talked about making sure that their open stack distributions work well alongside and with VMware technologies so with that I'll wrap up and I'll take questions just a couple things to call out on this slide so obviously all of these sessions are done by now but the foundation is great they put all the videos up online so I'd encourage you to check them out especially if you're intrigued by that short demo we gave the second one on the Tuesday slot the VMware integrated open stack technical deep dive it's a really great full deep walkthrough it's all showing real operations on the system you'll get a very good idea to install VMware integrated open stack and use these management tools with it there's also obviously we still we have a booth here there's a page up there if you have questions you can ask just any questions about how VMware works with open stack that's a VMware community if you've heard of hands on labs these are labs VDI environments that you can get with a couple clicks of a button online and we have a full lab that shows you how open stack and VMware works together so if you go to vmware.com slash go slash open stack lab you can check that out that shows both how open stack works with vSphere and works with NSX so a great way to spend you know hour or more just kind of really getting hands on with the technology and again just as a reminder if you're interested in the VMware integrated open stack product or beta that's the link below and the last thing is just we're hiring great engineers product people etc so if you guys set up here is intriguing to you and you might want to be a part of that team I'm happy to talk to you about that afterward otherwise thanks and I'll happily take some questions well it's that's the best way to sum it up but I mean it's obviously it's open stack APIs and the tooling and the ecosystem around it so the vCloud APIs are a different set of cloud APIs in this they're um you know I think the value of the open stack APIs it's a vendor what it's a set of APIs that's value number one and value number two is that these open stack APIs are more modeled on something like Amazon or these kind of more traditional cloud native abstractions and what we find is that a lot of times developers find those a little more intuitive a little more simple so you know at the end of the day open stack and VMware it's a lot about customer choice right we have all kinds of customers from tiny SMBs to you know massive technology companies and we've heard from enough of our customers that these APIs are something different and useful and something that they want to leverage with VMware technologies and so that's why we're working to enable them add a question so how different is the beta from is it like based on ice house do you know how easy would it be for someone to deploy taking the upstream code and driving and be center of ESX so it all depends on your skill set right you know open stack will be the easiest way I can promise you that but it's the tradeoff is really with flexibility right if you want to get in the guts and tweak the code or change every little configuration option out there that's not something you can do with a product like VMware integrated open stack so you really need to think about that kind of tradeoff and what you're looking for but there's you know we contribute the code upstream we have upstream documentation that you can follow in terms of how you want to if you want to get the bits yourself and deploy open stack with vSphere that's the model you want to do that's great we've got customers who are successful with that and is it based on so this product is yeah VMware integrated open stack the current version is based on ice house okay good question open vSwitch on ESXi clusters I think there's a couple models for that I think the model the community is looking at right now is actually running a virtual appliance potentially on top of it that's a very simple model the reality is supporting all of open vSwitch to the vSphere platform is not a simple task at all and in fact in a lot of ways it's incompatible with existing switching modeling and capabilities so it would break a lot of our partner integrations as well so the easiest way to think about it is that it's something you can actually layer on top L2 gateway I mean you can run it as a virtual appliance so a lot of partner technologies run as a virtual appliance on top it's much easier than having them directly integrate into the kernel is there any other questions? alright thanks a lot