 We're good, thanks. Hi, my name's Ian Jolliff. I'm one of the members of the Technical Steering Committee of the Starling X project. I'm really happy to be here this morning to share with you all the great work that the Starling X team has been doing over the last number of months. Dean, why don't you tell us a little bit about the architecture of Starling X? Okay, thank you, Ian. Starling X pulls together a set of well-known open source products, components such as Ceph, Sentos, Libvert, QEMU, and OpenVSwitch. We add to that an opinionated OpenStack configuration, tailored specifically for edge-style use cases. And then on top of all of that, we add some new services that fill in some of the gaps and does the integration work for all of these individual pieces. This does everything from initial installation and configuration of the complete cloud to adding APIs for hardware and software inventory, for fault and alarm handling and management, to detection and recovery of hardware and process failures, and zero-impact orchestration of patching and upgrades. These are the services in the middle of this diagram that we informally call the flock. They look and feel and act a lot like OpenStack services. They're all written in Python. And it's very similar to what we're all used to. It uses pretty much the same process as in tooling. These services have already proven their value in production use, solving real-world use cases. And I think you've got some more information about those use cases again. Yeah, thanks, Dean. So if you look at the way Starling X is built, it's really to focus on low-latency performance at the edge of the network so that we can really drive down the latency of the solutions. And the use cases are really looking at decoupling hardware and the software stack so that we can get new ways of scaling and leveraging these great cloud technologies that the OpenStack has built over the last number of years. So we're seeing that in 5G with the VRan use case, being able to really drive the consolidation of some of the radio network elements, but also optimizing for very small edge devices further out at the edge of the network. We're seeing that bridge into transportation use cases as well, being able by these 5G network technologies. And we're really seeing some people turning locomotives, for example, or subway systems into rolling data centers so they can optimize their route planning and power consumption over the full railway network, but also using it for safety-critical infrastructure so that they can use artificial intelligence to measure how the video streams off the front of a locomotive are being used to avoid safety incidents. One area that I'm really excited about is health care. Again, imaging systems used to be tightly coupled with their hardware, and so they had a big compute infrastructure associated with a single imaging system. But we're now seeing people decoupling that infrastructure and being able to improve the processing time and overall patient experience and the clinician experience so that they can bring all this rich data set from many imaging systems, many diagnostic technologies all together to really bring that solution end and with low latency and high performance, but also being able to help doctors visualize brain surgery all on these great technologies. The technical leadership for StarlingX is provided by a technical steering committee. We have currently eight members that we see here, many of whom are already part of the OpenStack community. In April, we plan to have an election for four of these seats, and we will add a ninth directly elected. And by the fall of next year, we plan to be a fully elected body. The TSC provides the technical direction, vision, architecture, handles the life cycles of sub-projects, and basically just takes care of all of the top-level technical operation of the entire project. So a few short weeks ago, we had our first release back on October 24. The community was really proud of the work that they did over a short few months. We really look forward to getting user feedback, having people take StarlingX for a run, and seeing where we can take this technology in the future. So thanks for that. You can have an influence on what goes into the upcoming releases. The next one is planned for this spring. StarlingX is still an early stage of its existence as an open source project, and there are plenty of opportunities to get involved and help shape the direction and make a difference in the quality and the content of what we deliver. The code for the flock services is in Garrett. We use Storyboard to track our stories and features and Launchpad for all of the bugs. So we've got a busy day today as well. We've got a number of sessions coming up this afternoon. Please come join us in the forums. We're really looking to engage and have an open dialogue with everybody in the community. We're also going to be around in the OpenStack Foundation Lounge, and look forward to seeing where we can take this next. Thanks very much. Thank you.