 Well, good morning. Thanks for having us here. So Cloud Foundry has always been about the developer. Developers want a platform that lets them focus on their work, focus on the problems that they're trying to solve. And through innovations like CF push and service brokers, the kind of detailed work of running an application and connecting it to the rest of the world is handled for you. But time has also taught us that applications rarely exist alone. They're part of a larger system, and they need to work together with other components and other technologies. And the application developers' build have to be operated and secured as part of that larger system. That's why we find projects like Irini so exciting. Irini allows us to take the high productivity developer experience of Cloud Foundry and deeply integrate it with Kubernetes, allowing the creation of a single environment where the right tools can be used by the developer. Now, yesterday, you saw Irini itself in action. Jules did a demo of the Irini project itself. Today, we'd like to show you how we've implemented Irini in IBM Cloud and how real developers can get value from it. So it's pretty incredible what developers can create when you give them some time and the right tools. So recently, we challenged our development teams to use IBM Cloud to solve pressing global problems. And our team in the UK stepped up to that challenge and created an app to help with disaster relief. Now, this is an issue that especially hits home to me. I live in North Carolina, and this is an actual screenshot from my phone. A few years ago, I had the opportunity to be in the eye of the storm. Now, look, if you live on the coast, a Category 1 hurricane is no big deal. To me, it was a terrifying experience. The sound of the wind was deafening. The rain hit the windows sideways. And simple things like pine cones became dangerous projectiles. In the aftermath of a hurricane, there's flooding. There's down power lines. And when you lose power, there's just no way of knowing when it will return. And that makes communication a real challenge. So our team built an app on the IBM Cloud in their spare time over the course of six days to make the aftermath of a hurricane just a little bit easier. So let's take a look at what they built. When a natural disaster strikes, communication with first responders is essential and can mean life or death. But a disaster can take down the network. Recupero is a mobile app that enables continued communication via peer-to-peer technology until someone finds a working network connection. So during a crisis, you can notify loved ones that you're safe with the simple tap of a button. Or if you're not OK, the app will forward your location to responders. They can find you in the map view and make sure that help is on the way. As you saw, the team built an app to communicate in a disaster, letting family, friends, and coworkers know if they need help or to reassure that they're OK. And it's important in a disaster situation to plan for unpredictable demand and infrastructure damage. So the team built a solution that can handle scale and internet outages. So now let's take a look at how the app was built. So here you see the architecture of the application. It's pretty straightforward. It starts with a mobile application. The mobile application allows users to record whether they're OK or whether they need help. The mobile application talks to other users over a peer-to-peer network. That peer-to-peer network allows the application to pass information from user to user in the event that they can't get access to the internet, which is something that might happen in a disaster. Eventually, somebody will be able to connect to the network, collect all of the information from all the users, and upload it to the cloud. The back end of that mobile application was built on Cloud Foundry, in our case, using our Cloud Foundry Enterprise Environment on IBM Cloud. We want to share sensitive information about users' location and health status. And so the isolated offering of Cloud Foundry was a great fit in this use case. The Cloud Foundry application takes the mobile data, formats it, and sends it to a pair of microservices that are running on a scalable Kubernetes cluster. The Kubernetes microservices have two primary jobs. First, to serve up an interface for the rescue workers, the map view that you saw in the video, that allows the rescue workers to understand whether you're OK or whether you need help and where you are. The second function of the microservices on Kubernetes was to store and retrieve the data from a blockchain. These are the major components of the application that allowed the team to come together and solve this problem. Now, when this app was first built, Ireeni didn't exist yet. And so we ended up with an architecture that had two separate runtime environments, a Cloud Foundry cluster for running the mobile back end, and a Kubernetes cluster for running the microservices for interacting with blockchain. But now, thanks to Ireeni, we could architect this application differently. We could have a much more efficient environment where all of the microservices run together in a single environment that has the Cloud Foundry interface and a Kubernetes back end. Why does this matter? It matters because it greatly simplifies the operation of the application. There's only one environment to manage, one environment to secure and monitor, one environment to maintain instead of two. It also allows the application components to communicate with each other more easily and in a more secure fashion within that single cluster environment. So let's take a look at this unified environment. OK, so here we are on the IBM Cloud. And we are going to spin up a Cloud Foundry Enterprise environment. Here's the overview page. And as you can see, we now have a technical preview of Ireeni. I'm going to click on that. And I'm going to name my cluster CF Summit. And this is just a technical preview, so we only have it available in a couple of locations. When we GA, we'll have it worldwide. But I'm going to pick Dallas 10 as my location. And here you can also choose the size. This is going to be two cells with four cores. And I'm going to create this cluster. Now, I'm an inpatient person, so we've actually already created this environment. So I'm going to go here. So if you're a Cloud Foundry admin, this is where you would go to look at the status of your clusters. And here you can check the health. Looks like we are all clean, and there are no issues. Now, as a developer, you may want to use your Stratus console to look at the health of the backend, the mobile backend. Let's see. This is a native Stratus environment. Let's check here. All right, now I can see all my stats of the mobile backend of the application. So here we have an environment. We saw how to quickly create a Cloud Foundry environment, leveraging Irene running on a Kubernetes cluster. Maybe we can look at the back end of this and look at it in more detail. So here we are at the command line. And for all of us here in the room who are familiar with Cloud Foundry, of course, I can simply look at my applications from a Cloud Foundry perspective. So if I do CF apps, I can see the mobile backend application that was running through Cloud Foundry that you saw in the architecture. But now that this is running on Irene, I can also look at this from the perspective of Kubernetes. So I can, for example, get list pods from Kubernetes and see the same container that you see through Cloud Foundry also through Kubernetes. I can also see that the microservices for interacting with the blockchain and serving up the mobile interface are available to me. So I can, for example, look at a different namespace and see here's the two pods that make up those services. So all three containers that make up the core architecture of this application are available in this same Kubernetes environment. Why does that matter? It means that I can use common tools to interact with them. I can leverage the technologies that are emerging in other communities, like the Kubernetes community. I can use monitoring tools and logging tools consistently across Cloud Foundry applications and Kubernetes applications. And I can secure and manage this environment a single time. So in a disaster, we might have to plan for unpredictable demand. We might have to scale up the app. How would we do that? Yeah, so both Cloud Foundry and Kubernetes, of course, are really good at doing autoscaling of workloads. So maybe we can just do that through Cloud Foundry and kind of watch it happen through Kubernetes. So I'm going to go down here, and I'm just going to ask Kubernetes to watch this namespace. So it'll print out a line anytime there's a change in status of any pods running in that namespace. And I can come into Cloud Foundry through the Cloud Foundry command line and scale the mobile back end of the application. I'll go from one to three just to keep it simple. And you can see Cloud Foundry has initiated that scaling activity. And behind the scenes, you can see that Irene is interacting with Kubernetes to launch those additional containers. And from a Kubernetes perspective, you can see the same things that are happening. So here, I have the ability to mix and match these two environments together and leverage the best of both. Great. So basing our Cloud Foundry offering on Kubernetes through projects like Irene that we're all working on together, I think is a great step towards our vision of a unified platform for containers and container-based development. As new technologies emerge, like Istio and Knative, we can work to evolve and mature them and fit them into that platform. I think we're working on a world where all styles of container-based development, direct consumption of containers with Kubernetes, high productivity development with Cloud Foundry for things like 12-factor applications, and serverless programming and functions-based systems can all act together within the context of this single platform. And so we're really excited about this evolution. I think it allows developers who love the Cloud Foundry experience to be able to leverage the latest and greatest of other technologies that are happening in the broader container space and be able to build some really amazing life-saving applications. We are so proud to offer a technical preview of Irene. Check it out on the IBM Cloud. We can't wait to see what you will build. Thank you so much. Thank you.