 So, the next person I'd like to bring up here is Troy Topnik. He's from SUSE. So, Troy's actually been in this community for a very long time. I first got to know him when he was with Active State, there was HPE for a while and now he's with SUSE. So, Troy is going to come up here and he's going to demonstrate the open source foundation incubating project called Stratos. It's a UI, web-based UI, that any of you can use, open source users or anyone can install and point at any version of Cloud Foundry and have a really good view of it. So, Troy, come on up. All right. So, go ahead and plug on in there. Excellent. You going straight HDMI? Yeah, there we go. Dungles. They're fun, right? Then we had to change the screen resolution this time. All right. So, you ready to show the demo? I am. Delighted to be showing this demo. This represents a lot of hard work from SUSE's cloud application platform team in Bristol, UK led by Neil McDougal, who couldn't be here, but I'm really happy to up their fantastic work. So, this, as you nicely mentioned, is the open source UI in the community. We donated this to or we proposed it for incubation in December last year and it was rapidly accepted. Thank you, Dr. Max, for getting that through and it's moved into the Cloud Foundry Incubator GitHub org and so it's open for contributions and feedback. I'll get a little bit back to that later, but let's take a look at it. Awesome. And so, just again, this is a user interface by Foundry Project. This is an API-based user interface, so you can deploy this in a number of different ways. You can deploy it as a Helm chart. You can deploy it directly to Cloud Foundry with CF push. You can deploy it via its Bosch release. You can just run it as a Docker container. And the reason you can do that and you have this flexibility as to where it's deployed is it actually connects to a Foundry using its API endpoint only. So it exercises the Cloud Foundry API and whether you're a user, a regular user, or an administrative user, you'll see a slightly different interface. Now, I've logged in here as an administrative user, so I'm going to see some things that a regular user wouldn't, but the UI adapts to the appropriate view. What? Based on role, right? Based on role. It's role-based access control, so we've got a role-based UI. For those of you who have taken a look at Stratos before, you'll notice that what I'm showing here is quite different. We have recently refactored the Stratos UI to use Angular 2, which gives us a more forward mobility and gets us, so it's a lot of refactoring work that's been done in the last little while. This is not quite feature parity with the V1 code base, but I thought it was important to show it, because this is what we want people to start coming in and collaborating on. So the key thing that any Cloud Foundry developer is going to want to do is Cloud Foundry Push. If your UI can do Cloud Foundry Push, you're in good shape. For sure. What I can't show, because it's in the V1 version, but not yet the V1 version, is CF Push from the local file system, but I can show something that's very cool, which is how we deploy this from. So I'm choosing the organization and space, and again, I'm only shown those organizations and spaces that I'm a member of. All this information comes from the API via this API proxy that's working in the back end. And we just specify either a public GitHub URL or a public Git URL or a GitHub project and very neat projects. Just a screen resolution, OK? Choose the branch that I want to deploy and hit deploy. So in the background, the API proxy is going to, actually the Stratos back end is going to Git fetch this and do a shallow clone of it and then deploy it, just like you would from the command line. And the output you see is just the same output you would see staging using the CLI. Very cool. Very cool. Yeah. So we'll let that stage, and we'll take a look at the app overview. Again, we used Google's new UI library, which escapes me at the moment. We'll come back to it. We can come back to it. Let's look at the features. The features, more importantly. So we see an overview here, how long the thing's been up, how many instances are running. We'll see more when it actually comes up. The routes that are assigned. We can add a new route if we want to. That same log stream we saw before is going to carry right through to when the application is deployed, then we'll start seeing the log stream. The services that are attached, I haven't attached any to this one. Again in the v1 version, we could create services and bind services from this part of the interface. That's coming soon. We can see the environment variables and we can add them. We see a stream of the events from the events endpoint of all the things that have happened in the application's life cycle. We then have some things that are not strictly Cloud Foundry-ish. These are the two things that I thought were particularly interesting. I think we've seen in most interfaces we'll have some of what we just saw before, although it's pretty cool that we can SSH into a container from here. That is neat. It is neat. Straight from the web. So we see this one's running on SLES. Of course we also ship our stuff with CF Linux FS2. So the team recently added the GitHub page which exercises the GitHub API so it keeps track of what it has deployed so that if we push new changes we can actually redeploy the app from the head of that branch. Metrics. We have a plug-in system that uses Prometheus, time series database, was the word I was looking for yesterday that I forgot, to store the metrics that we've gotten from the firehose or from the application log stream and the metrics. Keeps that and I'll show how that plugs in. So all of these things, and we can see that this is successfully deployed now, Heroku's 12-factor manifesto, which I used for a demo app, exercises the Ruby build pack. Of course. The one I talked to, a Cloud Foundry user yesterday who uses Stratus UI and has been deploying it to Cloud Foundry, which sets everything up with the Cloud Foundry that you deploy it to. He did not know about this cool feature, which is the ability to specify multiple end points. So when we're actually looking at this application view, we can look at all of them and we can see that, for instance, one of the ones that I deployed was actually deployed to IBM Cloud. Not in this case. Very cool. Can't find it now. I mean, I guess the value, the point here, is that you now have the same experience occurring across SAP Cloud, IBM Cloud, your own Cloud Foundry deployment, as well as Pivotal web services, which is pretty neat. Yeah, so I have just trial accounts on these other ones. So if I go into the Cloud Foundry that we have running on AKS, the Susan Cloud application platform that we're running there, I have a little more ability to go in and change things and add orgs, add spaces within those orgs. And we can see the firehose using the same library that brings us the application logs. And we can filter on that. Again, we'll have substring filtering, like we had in the V1 version of this API coming soon, see what feature flags are enabled and disabled, what build packs we've got installed, what stacks we're using on the system, and what security groups are. And we can see some of this stuff, a similar view, but with less things enabled for those Cloud Foundries where I'm just logged in and connected as a regular user. That makes a lot of sense. So how do people get involved? There are a lot of developers in the room. This seems like we would love to use it. That's the reason we'd love to solicit some feedback and some assistance. We've had really good uptake. We've had pull requests and feature requests from other open source Cloud Foundry users and even other partners. So we'd love to get your bug reports, your feature and enhancement requests. And of course, pull requests are always welcome. We've had some good ones from us, some good stuff coming in from Orange. And you can do that by going to the Cloud Foundry Incubator, Slash Stratos, Slash Stratos, and also equally importantly, the Slack channel that we have, which is quite busy and very responsive and looking forward to your collaboration and input. That's very neat. A UI for everybody. Thank you so much, Troy. Appreciate it. Cheers.