 So I'm going to get started. I've got five minutes to tell you about VMware Pivotal Container Service, or PKS. So what this is, is a purpose-built container service for operationalizing Kubernetes. So what does that mean? It means that we're taking open-source Kubernetes, so standard open-source bits. We're not changing the bits at all, packaging that, and deploying it on initially vSphere and the VMware Cloud on AWS. What this does is unify the management of VMs and containers in a single platform, including down to the networking level. So part of PKS is the option to deploy NSXT, which gives you networking to the individual VM, but also using a CNI plug-in down to the container level or the pods that you're deploying in Kubernetes. So this is hardened and a production grade platform that takes advantage of the underlying vSphere infrastructure to provide HA, to increase security, provide multi-tenancy and integration with a suite of VMware tools to manage the platform. So it begins with Project Kubo, which was started by Google in Pivotal and then donated to the Cloud Foundry Foundation. So we're using Bosch to deploy Kubernetes clusters and then to give you the ability to deliver Kubernetes on demand. And then you get all of those day two operations that you associate with Bosch. So being able to identify service outages and restart those services to recreate failed VMs, to elastically scale out the nodes or scale in the nodes of a Kubernetes cluster. You also get the ability to do rolling upgrades with little to no downtime. So if you want to go from 1.66 to 1.71 of Kubernetes, you can do that without having application outages. I mentioned high availability before, but also the ability to deploy clusters in multiple availability zones and isolate physical resources for individual clusters. So this is a pictorial view of what we've got. A couple of Kubernetes clusters deployed with Bosch, integrated with Google Cloud Platform Service Broker. So it allows you to leverage things like BigQuery in your Kubernetes applications. It comes with an enterprise container registry built called Project Harbor that was started by VMware. I mentioned NSX is included in this. You get the integration to the vRealize suite of tools for things like logging and network management, monitoring, et cetera. Also, integration to vSAN and basic storage policy in Kubernetes. So you can have an application that can decide they should go on a production storage or on development level storage, that kind of thing. So what is the difference between Kubo and PKS? What's in PKS? Well, you start with several open source products. So you've got Bosch. You have a CPI or a cloud provider interface that gets you to the underlying vSphere platform. We're including Kubernetes. We have a plug-in, CNI plug-in to the networking. So this is really Kubo. What you get with PKS is you get NSXT. You get this Enterprise Register Project Harbor. You get the ability to deploy Kubo and to configure it, to also configure underlying vSphere, the networking resources, and the registry. You also get a new API that's on top of Bosch. So it's specific to deploying Kubernetes. You'll get a CLI and API. You'll get a UI with this as well. So now you can do something like PKS Create Cluster, for instance, and you get a Kubernetes cluster to be deployed. Our plans right now are two different packaging formats. If you have PCF, you're familiar with Ops Manager. You'll get a tile for Ops Manager to do the deployment of PKS. If you're a VMware admin, you'll get an OVA form factor to do that deployment. This is available through VMware, Pivotal, and Dell EMC. And whoever you buy it from, you'll call them for support. And we'll all work together on the back end to support you. This is available as a GA product at the end of December this year. So if you want to get a deeper dive on this, come by our booth. I'll be there. My colleague, Nathan Ness, is doing a 20-minute presentation tomorrow at 3.30 in this room, if you'd like to see that as well. Thank you.