 Test, test. All right, so welcome everybody. This is the Nutanix presentation at the Marketplace Theater. So if you're interested in learning more about Nutanix, please come sit down. My name is Lucas Lundell, and I am the Global Director of Solutions at Nutanix. So I run a team of individuals that writes our best practices, reference architectures for any solutions that our customers use, whether it's SQL, SAP, Oracle, VDI, and general server virtualization. I want to start off with a little bit about my background. Before Nutanix, I was actually a data center architect, and I designed data centers for the federal government and financial services companies with Accenture. I worked in their research and development lab. A bit more about Nutanix. Today, we have over 1,750 customers. We have appliances in 70 countries. And our team has grown to over 1,100 employees. And this is just in the last four years that we've been selling a product. So we've seen some very fast growth in the last four years. We also are very proud of our net promoter score. So net promoter score is customer satisfaction for your support team. So we have over a 91 net promoter score, which is highest in the industry. So this is Gartner Magic Quadrant for integrated systems. Nutanix was placed as a leader in the Gartner Magic Quadrant this year. And it's actually the farthest right company. So it's great recognition from the industry and the growth that we've seen from Gartner. So we're very happy with that. And there's actually a Gartner symposium this week in Tokyo as well. So we're very excited to be participating in both of these events. Now, what does Nutanix actually do for those of you who aren't familiar with our product? In obviously a normal standard enterprise virtualization environment, you would normally have three types of gear. You'd have your servers, your compute, your storage area network, or your physical IP network, Ethernet network. And then you have your storage, whether it's a NAS or a SAN appliance. Now, you manage each of these pieces of gear separately. They're usually produced by different companies. You're responsible for ensuring you're running the right versions of code, BIOS, any software firmware that runs at every layer. And it's very difficult to scale. So as you fill up an existing storage array, you have to buy a new one. Now, what we've done is we've taken all the intelligence of a centralized storage array and built it into a distributed software system. So we have our own distributed file system that we sell as an appliance, as a building block for the data center. And the reason that we did this is we look at the data centers of companies like Amazon and Google, Microsoft. There's no such thing. Most of these data centers, they don't have centralized storage arrays. They run software on Commodity x86 hardware. And that's what we've done. We've taken that intelligence to the storage array and baked it into a distributed file system for enterprise virtualization. Now, what do we actually sell? So we have an array of different appliances. Each appliance has compute and it has storage. It has memory. So we use two different types of disks on every appliance. So we have SSDs and HGDs. And our software is intelligent enough to auto-tier data between those SSDs and HGDs, depending on frequency of access and what data is the hottest. There's also an in-memory read cache. Now, this single appliance, it does all the storage. The storage pooling, so you add more appliances. It's able to pull all that storage together and present it to whatever hypervisor that you want to use. So we support VM or ESX. We support Hyper-V. And we also support KVM. Now, on each of these appliances, on each of the nodes in a cluster, we run our software as a virtual machine. That virtual machine has access to the SSDs and the HDDs. And those virtual machines communicate with each other to form the distributed file system. And on top of that file system, we present it to the hypervisor. And however, using whatever mechanism that makes sense for each hypervisor. For VM, where we use NFS to present that pool. For Hyper-V, we use SMB protocol. And for KVM, we actually use iSCSI. So depending on what hypervisor we're using, we're presenting that pool of storage to the hypervisor in a different way. But on the back end, it's all managed and controlled by our distributed file system. And these are a couple of our enterprise customers, data centers here. What's nice about our solution is you don't have three different types of gear to manage anymore. You have a single building block that scales out as you want to add more compute or storage capacity. You simply add more nodes. And we've had some great success here, some of the customers of ours in every industry. But I want to move on and talk a little bit more about what we're doing with OpenStack. And then also answer any questions that you guys have about our solution. So on top of the KVM hypervisor in particular, we've actually built our own management stack. And this management stack runs on the same distributed system as our file system. So we have our own hypervisor management capability that allows you to create VMs. It allows you to create storage, store files for these VMs, do snapshots, do duplication, compression, high availability. So if a host fails, allow those VMs to start on another host. Motion. So if you're trying to move VMs between hosts, it supports all those capabilities. Now, we also have customers who are very interested in using OpenStack and a lot of the advantages that OpenStack provides. Things like the easy to use interface with Horizon, some of the networking capabilities with Neutron, users in quota management, single sign-on. So what we've done is we've integrated our Acropolis technology with the OpenStack services. And how did we go about doing that? First of all, why did we go about doing that? A couple of the key reasons is our file system has many pieces of functionality that haven't quite been implemented. Things like auto-tiering, so flash and H2D auto-tiering. Things like VM data locality. So when you're running VMs on a Nutanix system, the data for a VM, even if you're using something like Cinder, you're actually using NDFS on the back end. And it allows the data for each VM to sit on the flash tier local to that VM. And in the background, we're also replicating that data to a different node. So unlike Amazon EBS and native implementations, we have the concept of VM data locality. And we've seen that reduce network consumption and also improve performance and scalability of any sort of distributed system. We also have things that will transparently happen within our file system, like compression. You can turn on compression, deduplication, and get all of those benefits without actually having to worry about configuring that within our own file system. In-memory caching is another feature that we have. So there's a lot of things that we're doing in our file system that help scale an open stack infrastructure deployment. Now, how do we go about integrating Acropolis and some of the OpenStack technology? We've actually developed another VM, which we call our Acropolis OVM, that sits in between any OpenStack distribution and Nutanix. So you have this VM. And this VM is able to export a Cinder service and a Nova service and serve as an endpoint for those services. So you'll run an OpenStack VM, which we call an OpenStack controller. You can run one or many of those controllers, depending on the scale of your deployment. You'll run an Acropolis OVM, which handles the integration between the OpenStack APIs and our Acropolis APIs. And that'll allow you to use our file system as a resource provider for both Nova, Cinder, Glance, and Neutron. Now, the OpenStack controller will continue to take the dashboard, the orchestration, quota management, user groups and roles, and SSO. So all of that looks the same. It looks like you're managing an OpenStack environment. You have the OVM, which handles the integration. And then you have our cluster and NDFS, which provides all those basic infrastructure services, along with the features of the file system. Now, this is just kind of the high level of what it looks like. You'll have your OpenStack controller. That exposes all the OpenStack APIs. And then it does RPCs with our VM, which exposes all those services and all the resources that we have within the Acropolis cluster. Now, in terms of how the different services break down and what VM holds primary responsibility for each of the services, this is a map. So as you can see, the OpenStack controller is responsible for Keystone, Horizon, Swift, Glance, Heat, and all the other services. And with Acropolis and NDFS, we expose Nova, Cinder, Glance, and Neutron services through Acropolis. So the APIs look the same as a resource provider for each of those services, even though on the back end within Acropolis, we're using Nutanix technology to manage the clustering and also obviously the storage with our file system. Now, as you want to scale a deployment, like I mentioned, you can have more than one OpenStack controller VM. You can also have more than one Acropolis OVM. And if you want to scale it across multiple sites, you can use load balancers across multiple sites to run a multi-site deployment. As you want to add resources to Cinder or Nova, it's as simple as adding nodes to the Nutanix cluster. So we automatically discover, as you add nodes to the same layer or two network, we automatically discover those nodes. You can go to our interface, which is called Prism, add those nodes in, and we'll automatically register it as a resource through Cinder and Nova so that you can run VMs, provision VMs, either through Acropolis or from the Horizon dashboard. So all of this information, we've actually made available. We have a site called the Nutanix Bible, which goes through all of the details on our file system and on our technology. We're very transparent about the functionality and features that we have. So we've written up our OpenStack integration within the Bible. So if you're interested in more information about how Nutanix integrates with OpenStack, we've made it available at that website, which is just nutanixbible.com. Now, why OpenStack is capable of a lot of these things, a lot of, I think there's a lot of benefits towards using both solutions together and integrating Nutanix with OpenStack. It gives you a very simple building block for building out your OpenStack environment. It's also something that we support. So we have a team. We have support teams located across the globe. We actually have one in Tokyo. This is a solution that's fully supported by Nutanix. So as you deploy an OpenStack environment, we help you with the deployment. We help you with the integration. And it's easy to scale. Now, as I mentioned, with the distributed file system, you get a lot of benefits that don't exist in other distributed file systems, including data locality, snapshots, using our snapshot technology, deduplication, compression, and other benefits of our file system. All right, so that's a summary of our OpenStack integration. I want to leave five minutes. If anyone here, any folks in the audience had any questions, we also obviously have our booth here I think it's T70. And if you're any questions from the audience about Nutanix or OpenStack, NDFS. Sure, for the SDN part, so networking within Acropolis, we've kept it very simple. Within Acropolis, you can create different VLANs. So you have VLANs, you have VLAN IDs. And then as you create VMs and their network interfaces, you can associate those with different VLANs. So it's a pretty simple networking model. The SDN side of it, like switch management and all of that, is not something that we take on. So you can use Neutron, you can use Cisco ACI or any other NSX, NYSERA. All those technologies can work with us because all that we need to run our system is a simple layer two network. So once you have a layer two network, doesn't matter. Yes, because you can run Neutron and whatever Neutron's capable of, you can do. So as long as you give our technology a layer two network at the end of the day, we can function. So we've kind of left it up to the customer to choose how they want to do networking. We haven't done a lot in that area besides simple, when you create VMs in Acropolis, assigning those VMs to a VLAN. That's it. That's all you really have to do. We don't manage the network topology or do any layer three overlays or anything like that. Good question. All right. Yeah, so the way that we expose Acropolis to OpenStack is done in a way that it just looks like a Cinder or a Nova resource. So you can use it with whatever distribution. I mean, we've tested it with Canonical as a partner of ours, Ubuntu. We like that distribution. We have customers using that integration. But yeah, I mean, we haven't found a distribution that doesn't work with this model yet. I can't say we've tested them all. But certainly, we wouldn't preclude you from using any distribution that you want. Sure. How do you do backup? So I mean, there's a lot of ways that we support backup or that folks do backup. I mean, there's snapshots, which isn't really necessary. The question was, how do you do backup with Nutanix? There are third-party backup providers that work with ESX. We're working with other third parties to develop integration with our KVM solution. So I mean, some of the more popular ones, obviously, Symantec, Commvault, Veeam. We're working to support all those solutions with Acropolis. We already support those with Hyper-V and ESX were appropriate. All right, any other questions here? I think I have about a minute left. If anyone else has anything, we also have, if you want to pen and want to get your badge scanned, we have some reference material here that we're handing out. All right, so we're very excited to be here in Tokyo. I appreciate everyone for listening to my presentation. And have a great week here. Thank you very much.