 Thank you. So I'm Patrick strict. I'm the product manager for OpenShift dedicated and Azure Red Hat OpenShift, which from now on I'm just going to abbreviate a arrow or arrow because it's a really long name and then as she mentioned, Andrew Katha Katha is right over there and he'll be up for the AMA too. He can come up now if he wants. So the idea that you may be asking yourself what is OpenShift dedicated and what's what's arrow? I've heard this before, but I don't really know what that is. The answer is really simple. It's just OpenShift. The difference is that we manage the provisioning and operations and security of the cluster for you. That's really the only difference. It's exactly the same OpenShift same installer that you would get if you downloaded the IPI installer from try.openshift.com and installed it yourself. So the value we provide is a consistent experience that all of our customers can get and the value of the knowledge that we get from managing all these different customers. And also the price is basically the same as if you didn't, if you just bought the OCP. So if you're comparing between OCP and one of our managed offerings, it's pretty much the same price between the two. So what's our goal? We want to be the preferred way that OpenShift is run in the cloud. How do we get there? We do that by removing any of the friction that you would experience provisioning your cluster, operating the cluster. Or securing the cluster. We want to make sure that it's as easy a process as possible for you. Now, this may look familiar. This is a, you know, if you have OpenShift in your environment, you know, this is kind of a rough topology. You can see from the thing on the left, although it doesn't show up very well, but there's gray boxes beside most of the top of those. And those are the things that you're responsible for in a normal self-managed OpenShift environment, right? You're responsible for user management, quota management, cluster creation, cluster management, logging and monitoring the cluster, network configuration, and software and security updates. And then Red Hat is obviously there for you to support the platform. So this is what it looks like from a managed OpenShift perspective, right? We take everything from cluster creation down and we handle that for you so that you can focus your business on the value-generating aspects, which is getting your applications developed and published and available to your customers. There's a few, so what we're doing to get to where we want to be when OpenShift 4 was released in June last year, we started working on making the product as self-service as possible. So we took OpenShift 4 and we said, what can we do to make it easier for you? And we built a whole infrastructure and web interface. It also has an API and CLI that will be coming out. It's available there, but it's not public that you can use to interact with the cluster, create the cluster and make changes to it, see the stats for it. So we've spent the last six to seven months really focusing on that self-service piece. We wanted to make the experience as easy as possible. Now that we've got the groundwork laid there, and that's in a really good place, we're moving more towards the second two pillars, second two initiatives, which is to showcase everything that OpenShift 4 has to offer for you from a developer experience perspective, and then enhancing the value based on specific configuration needs or new features that may not come from OpenShift itself that you would want and would be helpful for you to grow your business. There's a few highlights of upcoming work, both from OpenShift Dedicated and from Arrow. The SOC2 Type 1 and ISO 27000 are wrapping those up. So if you're interested in those type of compliance certifications, we'll have that very soon. Similarly on the Arrow side, we are wrapping up some initial regulatory compliance, which will also include those SOC and ISO. The second bullet there I added, because it's not something we would normally include on the public roadmap, but because you all operate OpenShift or OKD yourselves, I wanted to talk a little bit about what we're, you know, the things that we do. So we do vulnerability and access control scans today, but they're manual. So the team has to go in and go through a checklist and make sure everything is good. So they're going through and creating a whole automated process to constantly regularly do these vulnerability scans and access control scans. On the Arrow side, you'll notice it says OpenShift 4.3. So today Arrow is 3.11. When Arrow was launched last year, OpenShift didn't support Azure as a cloud platform. So since it has, we've added, we added that support in OpenShift. The team has been working very hard architecting what the design will look like in an Arrow perspective. Because Arrow, if you're not aware, it is a native Azure service. So it's where OpenShift dedicated, you know, we are running this cluster on AWS and we partner with AWS. With Azure, it's a joint team or with Arrow, it's a joint team with the Azure service. And I'm going to show you a little bit about that. So we've been architecting and that will be coming later this year. Another kind of back end thing I wanted to talk about is that OpenShift dedicated is not just something that businesses use, external customers use. We use it ourselves. We use it to service and deliver OpenShift itself. So some of these are code names that you might have heard in different OKD conversations or maybe summit presentations. Tollbooth is where data comes in and get in talks from your cluster to our cluster. Same with the telemetry feedback loop. Cincinnati is the engine that handles the upgrades for the OpenShift clusters, OpenShift four clusters that are in the field. So when you subscribe to the fast channel or the stable channel, those channels and what upgrade graph looks like for each one is hosted in Cincinnati. And then Quay and all your subscription and entitlement management, those all run on OpenShift dedicated. So just a quick, what does it look like to revision OpenShift dedicated? I said we want to remove the friction. So what does that look like? This is a screenshot based demo. So if you go to cloud.redhat.com, which if you have an OpenShift at all, you should go to, I go to OpenShift cluster manager and you'll see a list of your clusters, whether they're OCP or OSD. You'll see all your clusters that are OpenShift four in there. And you can see if there's an update to one, you can update it from there if it's OCP. But if you click create cluster, you'll get to choose which one, depending on your subscription. If you have a subscription for dedicated, you click that. Do you want to install it in your AWS account, which is the customer cloud subscription, or in Red Hat's AWS account? Give it a name, pick which region? Is it a single AZ or multi AZ? Which node type do you want for your compute? How many of those nodes? How much persistent storage? How many extra load balancers if you have a subscription for additional load balancers? And then if you have a CIDR range that you need us to use, you can put that in, especially if you're doing VPN connection back to your own data center. And then click create cluster and that's it. Within 30 minutes, you'll have a fully functional OpenShift four cluster that has CA certs applied to it already. It's fully configured on the AWS side, whether it's your AWS or our AWS, we'll take care of configuring the VPC and making sure that everything is set up. And it'll be also monitored by our SRE team and our SRE team will be getting alerts for it. Once it's up, you can scale the cluster up or down by nodes, load balancers or storage very easily from this interface. And so that's my quick for OpenShift dedicated for Arrow. It's a very similar process, but because it's a Azure service, you can use the AZ CLI. You just do AZ OpenShift create and within a few minutes, Arrow takes about 15 to 18 minutes. It'll be done and you'll have an OpenShift cluster and it will spit out the URL to connect to the console. So I hope that shows a little bit of the ease that we've added in and the reduction in friction that we've added to make getting OpenShift in the cloud easier for you. That's all I've got. Thank you.