 Good afternoon, everyone. My name is Chris Martin, and I'm here with my colleague Julian Pistorius. We are the co-founders and developers of Exosphere. Exosphere is an open-source software project that delivers a user-friendly interface for cloud computing. So if you can imagine OpenStack Horizon being redesigned for researchers and data scientists rather than IT professionals. The pitch for users and institutions is that you easily run your workload on big virtual computers. You launch instances, you get a one-click shell and a desktop in your browser. You don't have to worry about virtual networks, security groups, SSH keys, anything like that. So it makes the cloud more accessible. It just works with existing OpenStack Clouds. It's completely a client-side web app, and we strive for very easy adoption and integration. We also strive for no-user interface lock-in, which means that if you want to jump between Exosphere, the command line of the APIs, then Exosphere will get out of your way. If you want to pick it up again, then it shows all of your resources that you made using the other interfaces. Exosphere is free, open-source, localizable, and white-labelable. We have a deployment for Jetstream 2, which uses their branding and their nomenclature. It's very easy to customize and you can offer Exosphere to your users today with your own institutions, branding, etc. So we're going to jump right into changes since our last lightning talk in April. Julian, take it away. Thanks, Seymour. One of the things that was close to completion last time but wasn't quite ready was the graphical remote to desktop in the browser. This is powered by the same open-source project that powers the in-browser terminal called Apache Guacamole. Seymour clicks on there. It supports copy and paste from the browser and is nice and responsive and doesn't require the way we deploy. It doesn't require any extra servers. Everything runs on the instance itself using Docker. My browser is struggling to keep up with these tabs. Let's go back to that one. What's our next feature? The other one is a new feature based on the DigitalOcean user interface for launching virtual machine images in a nice friendly way instead of having to go through a big catalog. Cloud Deployer could customize Exosphere using JSON file and then instead of having to troll through a whole back catalog, you can have curated images that are very easy to select based on just an operating system distribution and version. I guess your browser is really struggling. My browser is struggling with Google Meet going. It's half loaded. If I weren't running a Google Meet, you would see some logos here. The other thing that I spent a bit of time on this last six months was integrating data science workbenches. This builds on the binder projects, reproducible execution environment specifications. Any binder-compatible repository can be launched when you launch a server. Then you end up with a persistent Jupyter Notebook or RStudio environment that can run potentially on instances with GPUs, lots of memory, lots of cores. It's pretty good for doing reproducibility in workshops where you don't want to rely on the free MyBinder service. Everything standard under the hood. Again, everything you could do the same thing with the command-line tools, repo to Docker. I think if you want to see if the... There we go. It's eventually going. There we go. Here's an RStudio environment. So this is... Oh, now I launched a billion of them. But this is running on the instance that you launched with Exosphere. It requires no configuration on the user's part. We facilitate secure TLS encrypted connections from the browser to the instance. And there is a Jupyter Hub one as well. There we go. You want to see if the remote desktop works this time? Yep. I think my browser has caught up graphical desktop with any luck. Oh, I think we'll be lucky. All right. So this is a CentOS 8 instance running GNOME. You can run any graphical application on here. It's in your browser. You can copy and paste between the browser and the host operating system. Again, no configuration required on the user's part to set this up. They just launch an instance and say, I want graphical desktop. Finally, I guess a whole bunch of UI enhancements. Julian, if you want to run through those quickly. We used to have a sidebar that's no longer there. That's my timer. We have a new logo. We have these pretty resource usage graphs. Just a bunch of tweaks to make the app less intimidating to users. Make it look better as well as work better. Hurrying along, we have a feature roadmap. Some of the things that we just showed you are actually on the roadmap. They're in the works. Some GPU powered features. Better support for containers as first-class objects. More single sign-down integrations. We already do OpenID Connect for JetStream Cloud. Cutting right to the end, Julian, take it away. Call to action. Yeah. All of you probably have access to OpenStack Clouds. I would love you to try it. I think what's not in the demo was we have a Nectar Cloud working. We have Tombstone Cloud from Cybers working. There's a commercial Cloud Fuga that we got working. But if you need access to JetStream, let us know. We can give you demo access to that. And then, yeah, we have a matrix chat. Please, real-time chat where you can talk to us. And thanks again for all the help from JetStream and Indiana University for their support. And also a bunch of new contributors that we got from the community in the last six months or so. Any questions? Feel free to ask them here. Chat or afterwards. Thank you.