 Good morning everyone. I'm actually here today to actually talk to you about real life OpenStack deployments that we've seen in the field. We actually ran a market survey and one of the top reasons that you actually use OpenStack for was to actually increase operations efficiency and also to accelerate the organization's entry into being able to deliver new products faster and quicker. But why do you actually need to do all that? If you look at some of the key challenges that you actually face in the enterprise, both if it's actually mode one as it relates to existing apps or mode two, which is the next generation applications they're trying to build, one of the common complaints they've seen on existing apps is it's very slow in delivery. The environments are too complex and when it comes to cloud native apps they're actually not agile enough and the environments are not scalable. Right? I'll actually take you through what real-life customers are actually doing to actually solve these four problems using OpenStack. How do you actually fix delivery? If you're actually an IT consumer, you actually want your IT department to be relevant in this day and age and one of the key things is to actually accelerate delivery to actually stay relevant. One of the common issues you have is as a developer you actually want to build an application. The workflow that you actually have to go through to actually get your environment up and running takes a lot of time today. So this is how a traditional environment looks like without any automation, without any service management functions. If you look at here today it actually takes close to five to six hours average to actually get a VM where the actual time it takes is there's a lot of time spent between queuing between different teams on getting the work done. There's a lot of time lost. So you're actually waiting for a long time. You're actually wasting productive time where you could actually spend time on building applications rather than waiting for infrastructure. But how do you actually fix that? So one of the goals is to actually take all the work that you've delivered in the old days manually and try to actually build service functions or service catalogs to actually speed up the delivery process. You would actually see here that you actually build a request. The request actually gets validated by all the people that are actually involved in delivering the service that gets turned into a catalog item and you actually then take the catalog item as a blueprint and actually turn it into your end user to deploy. When you make those changes, guess what happens? The time it actually took to actually build an environment just came down from 10 hours to 16 minutes and 16 minutes is probably enough time for someone to just go get a cup of coffee and come back and your environments are up and running. So this is actually a live example of a customer. We do have a blog post. You can actually read it at the bottom where the Yale NUS University actually used OpenStack on Dell servers to actually speed up the delivery of the environments within the university. And this has definitely helped them to actually help build rapid solutions and actually innovate faster. The next issue you have is the environment is too complex. There's too many things that run your enterprise. You actually have a legacy virtualization platforms. You have hybrid cloud environments. And as a developer, you need to know where environments are sitting and how to actually build those solutions. One of the goal to actually speed up the environment is to actually optimize your existing environments by using automation and using policy to an automation to actually make sure that the workloads are actually balanced across multiple environments better and you actually automate it to actually increase efficiency. I'll just take you through some of the challenges that you have today. So you actually have a workload that actually runs in an existing traditional virtualization cluster. You need more environments to be built. You end up building a private cloud. You actually go and expand it to run additional private clouds. But the problem that you have is you have too many environments that are stood up. There's no policy and governance around it. So when you actually have to move workloads to actually scale out or scale up, you probably have a problem where you're trying to rebalance workloads from your existing cluster and migrate them to your cloud environments. And because you don't have a way to have governance policies around it, you'll probably see that you probably have problems migrating workloads and your compliance teams will not agree on those migration processes. The goal is to actually have a management platform that actually ensures compliance and helps you reduce cost. For example, we actually have a leading loyalty programs provider in Canada that actually has used OpenStack to actually reduce the cost of the environments from 30% to 50%. They reduce the CAPEX and their operational risk. And we also have a large global credit card company that actually has migrated more than 12,000 VMs from the traditional virtualization platform to OpenStack. And they actually did that by having a common governance framework across mode one and mode two environments and allow them to migrate workloads more efficiently. So how do you actually solve the issue of not being agile? You could probably have all of these great infrastructures. But the problem that you also run into is how do you build applications faster and take advantage of the underlying infrastructure? So one of the issues you have today is you actually have siloed teams that are actually working. You have a developer building applications. You have QA team actually testing code and you have operations trying to build operation functions. When the particular application is ready to go into production, the biggest question that operation has is how do you actually take that piece of code the developer wrote that was QA and actually take it to production? How do you actually set it up to scale up? How do you actually update it? What are the life cycle management functions you have to adhere to? And as your head of development, these are the common issues that you run into, right? Now, how do you actually reduce my dependencies? How do I scale my applications independently? And how can actually move this functionality from development to production faster? Now, you might be thinking, what does OpenStack have to do with this? OpenStack actually brings all the different teams together by giving an optimized infrastructure. And if you're actually the head of development, you probably want to treat your infrastructure as code and make that a part of your application development process. So the siloed teams move to having more cross functional teams. And this is where all the different teams come together. And OpenStack is a great platform to prove that. You have network compute storage, all working together to actually make the platform available. That actually leads to what we're calling today as microservices. Microsoft is a great way of actually speeding up, building applications faster and giving out rapid innovation to actually help build those. And using the concepts of DevOps and the container strategies today, you actually will be able to build those microservices and move those applications faster. So this is an example of how FICO actually used OpenStack and with the use of OpenShift on OpenStack actually helped modernize the development environment and build applications faster and reduce the time to market by 50%. The next challenge you have is non-scalable infrastructure. How do you actually build scalable infrastructure and how does it actually solve your problems? Right? Today, what you actually had is iteration virtualization. You actually have the scale-up model. You need more infrastructure. The solution is throw more dollars at it, buy more infrastructure, and that's your solution. You need more, buy more, right? It's always a scale-up model. Your application is actually built with the underlying hardware, and they actually expect the hardware to support the speed of business. And as you need more faster performance, you actually add more hardware and scale up your applications than scaling out. One of the solutions that actually helps, and the reason OpenStack has been so successful, is it actually allows you that scale-out model. It doesn't allow you to actually build everything up front and then grow vertically. It actually allows you to scale out horizontally by adding additional computing or adding additional storage in the back end and build applications for the cloud to actually help scale out rather than scale up. With standard management functions, you actually can enable that scale-out infrastructure to actually give out all the standard functions that you would give for your enterprise, like ChargeBack, self-service, workflow management, providing audit capabilities and control policies. And OpenStack and all the different projects within OpenStack are great examples of how you actually can deliver that. With projects like Horizon Dashboard for self-service, Heat for Workflow Management, Cilometer for providing telemetry are actually great projects that actually help you give those functionalities to your customers. So this is an example of how you'd actually deliver a scalable infrastructure and provide a single pane of glass across your multiple OpenStack regions. You probably need an enterprise-grade scale-out architecture like OpenStack with a common service portal for your customers to consume from. So you're no longer actually adding more and more compute in one environment. You actually are spreading it across globally and actually providing resiliency as well. And using commodity hardware and open-source solutions, you actually can deploy and deliver enterprise solutions better. This is an example of a customer who actually is providing a high-scalable infrastructure and they actually gone down and increased their operational efficiency by 35%. It actually helped them build as a service environment for their end customers. So what you've seen here today is that OpenStack is there. It's there for prime time. Enterprises are already consuming OpenStack and we feel that OpenStack is ready and it is enterprise-grade right now. From Red Hat, you actually have the Red Hat Enterprise Linux OpenStack platform. It is the officially supported Enterprise-class OpenStack distribution that's actually co-engineered with Red Hat Enterprise Linux. It is released every six months. Our release cadence is two months, approximately two months after the upstream release. And the reason for that is our focus is primarily on the maturity stability and the stability of the platform itself. And we actually provide backpots throughout the life cycle. And our releases are actually supported over three years. We also have the community version of that. It's called RDO. So it is closely aligned to the trunk. And RDO is actually an upstream distribution that's actually packaged to run with Red Hat Enterprise Linux and its derivatives. Why Red Hat OpenStack? You'll probably see that ever since we actually started the partner ecosystem, we actually have more than 350 members since the launch. We have a lot of certified solutions in our partner marketplace. Because it's actually run on standard well, we actually have a lot of different hardware that is actually certified and supported. And we have more than 13,000 applications that are actually available on REL that we consume. Yeah. If you are interested in joining Red Hat, we are hiring. You can meet us at Booth P7. And we also have the Red Hat job social at the Wolfgang Puck Pizzeria between five and seven today. So I think I have three more minutes. So I'm here to take any questions.