 That was awesome. Thank you for that update and for everything that you do. Now I want to just welcome up next Alan Meadows and Matt McEwen to tell you about airship. Good morning Berlin. Can we go back a couple slides? I'll try again. Good morning Berlin. So for those of you who haven't heard of airship, we're a pilot project within the OpenStack Foundation and both of us are here today to give you a project update and to tell you about an important milestone that we've reached. So first what is airship? Airship is a platform for the full life cycle management of open infrastructure. It treats containers and helm charts as the fundamental units of cloud software delivery and deployment. Airship takes a collection of declarative site manifests, yamls, and then feeds them through a single front door API and then uses them to drive the provisioning end-to-end of a full site from bare metal provisioning to the definition of network and policy through standing up a full OpenStack cloud. Doing an upgrade is as simple as changing one of those manifests and get and then running the whole collection back through that front door API. Airship takes the guesswork out of cloud software deployment and upgrades. Thanks for the overview, Matt. We also wanted to briefly walk you through the history of airship, how it started as a project. So in 2016, we started the OpenStack Helm project and that's worth mentioning because although these two projects are completely independent, they are sister projects in a way. Once we had OpenStack functioning as a helm-based application, we wanted to start building a declarative platform that would enable us to quickly stamp out new environments as well as manage the life cycle of all of our helm-based applications. We initiated airship Upstream and GitHub in 2017, starting with an application to declaratively workflow large collections of helm charts, moving on to tackling deploying Kubernetes on bare metal infrastructure and finally filling in all the other orbiting sub-projects that make airship what it is today. We brought this collection of airship services to the OpenStack Foundation as a pilot project in the Vancouver Summit and today our announcement is really all about introducing our 1.0 release candidate. So a number of different organizations have been collaborating to build airship and you can see a few of them here. As you can see, many of them are already using airship for real-world use cases or plan to use it very soon, things like 5G, edge computing and continuous delivery. So airship has published a release candidate. It's to act as a stable reference for the community while we continue on our way to an official 1.0 release and there are a number of features in the release candidate up on the screen. I'm just going to mention a few of them. Airship was built by operators for operators and our expectation there is that airship end users should be able to operate airship without having to write additional orchestration or wrappers around it to operate it in a hands-free way. It should work that way out of the box and it's able to achieve this because of a singular deployment workflow API that functions the same whether you are deploying a site, releasing a minor configuration change or even upgrading OpenStack itself. An airship also delivers predictable upgrades. So something you should be able to test once and be able to release into any number of sites and it should function exactly the same way. Finally, airship is helping end users today stamp out new environments. So at AT&T we have over 20 environments deployed and managed by airship and our deployment engineers are now able to replicate these sites more predictably and quickly than ever before. The functionality that we're prioritizing for our 1.0 release focuses on making airship easier to get started with and on expanding its use cases for more people. We want to streamline the initial configuration experience. We want to integrate Ironic for bare metal provisioning and we want to allow for multiple operating systems. We really would love it if you would get involved in airship. We welcome you to go to airshipit.org and take our demo environment for a ride to join our weekly design calls or IRC meetings and give us feedback and to help us reach our 1.0 goal in advance of the Denver summit next year. So up on the screen we've got some great sessions, workshops and forums that all relate to airship in some way at the summit this week if you want to learn more about the project. We really invite you to attend these and ask us questions about how airship could help your organization. So please come to the rest of the sessions that we have and join our mailing list, visit airshipit.org and enjoy the rest of the summit. Thank you. All right. Thank you so much. Airship's off to an exciting start.