 So, here is my, let me log into it. So my system controller, or my, is the font big enough or can increase the font? So the system controller is at 10, 10, 10.3. Everything is virtualized. So we have a virtual system controller and a virtual subcloud. The subcloud is a Simplex. System controller is by definition has to be a duplex. I have only one of them running right now, mainly because the system that I have doesn't have enough resources to run that. It's a 10-year-old laptop, which basically says that in any recent build server you should be able to have a complete duplex running as well as a Simplex to play with the distributed cloud. So we log in under the system controller, and as a first thing always we do a system host list, and it comes back, the D-grade that here basically says that it's because one of the controllers is down, but from a system controller perspective we have to have two because it has to be HA, it has to be redundancy. The way we access the subcloud, or we can display the subcloud is with subcloud list, the C subcloud list, and what you notice here is that it's online and it is in sync. And if we now go to the subcontroller, a subcloud, this subcloud is available and it is unlocked, right? Now we want to see, and I hope that I set up the tunnel correctly right now, is that a game? I cannot get to it. I can unfortunately not show the GUI version of it, but we can walk through what needs to be done. So a couple of things I want to emphasize, put the emphasis on, okay. So starting point, starting X, as we all know by now, is an integrated system, it's a fully integrated system, meaning that the Linux kernel, open source software, root file system, along with starting X components as well as the Kubernetes portion of it, have all been integrated into a single image, into a single ISO image that you get to use to install the first controller. Documentation of that, where to start the documentation, build guide, it's a very good build guide, I mentioned that, yeah, I have that here. The build guide basically goes through the build, you use the same, and requires you to download and use the starting X tools project. The starting X tools project gives you a number of features. One of them is the starting X build tools, which gives you a consistent software development environment for a specific version of the tools. The advantage of that is, you always have the right tools, you're building the starting X from using the correct tools that everyone else is using. It also has deployment examples and deployment tools that I am using here. The deployment tools give you, by default, a duplex or a same-text model. You can extend those, which you can extend with worker nodes, storage nodes, or as in this case, we are extending that with distributed cloud. Basically what we do is, and here's the, I referred to this earlier today, so what the starting X tools gives you on the right is the central controller, that comes with, that comes with, from the tools. We are not adding any modifications to that. To the left, we have the sub-clouds, again, comes as a same-text, again, it comes by default as is from the tools. No modifications needed. The plumbing in between is to turn this to, to connect this to via a gateway. I'm sure that there might be another better way than what I have done here, please let me know. But by doing this, we basically put them on two different sub-nets, routable, and turn one of them into a sub-cloud for testing, for validation, or just to play with them. I wish I could get this to work now a bit. Much of this can be automated. So if we go to step screen zero, from here, I wrote a small script. So the readme file in this directory, basically in this project of this, oh, I have to turn it around here. So pretty much this step is outlined here, what you need to do to create the VMs. You do simply an export, you give the bridge name, the name of the bridge, and you set the IP networks for the, that you want your controller or your system card to have. Once you have this, which is essentially what we are doing here. So there are two steps in this. So you start off with the export, then you set up the network, and you set up the configuration. Setup configuration is going to run through and you set up the configuration by giving it the ISO image. In this case, I'm using the default Starlink X image, and you basically tell it what you want it to be, a duplex or a simplex. We do this twice, and after that, the rest of this script, it will be part of the PowerPoint. It will be posted, which you can download. Going through the installation, so let's go ahead through the process and create a simplex and see the installation and that. And you can ignore this comment. So let me, so when you first boot it, when you first put in the ISO image, the three options that you have, standard controller, all-in-one controller, as well as all-in-one low latency controller configuration. Console by default, we choose serial port because that makes it obviously easier. How we push this, it's going to go through the, it boots it up, and it does the installation by itself automatically. It doesn't ask any questions. And that is mainly because in an environment, in an IT environment, you want to make sure that once it is installed, it is fully automated. On this screen, you can move control B, and it's going to take a couple of minutes, a couple seconds, and it's going to create a partition under system. So the first time we install StarlinkX, it's going to create a partition that will not be touched on any subsequent installation. That partition is platform backup. We can use that to store container images, container images that are used by the, doing the bootstrap process to speed it up. So we download, if I'm not mistaken, it's somewhere between, depending on the system that you're installing, we can download, the download size can be up to a few gigs, which can be difficult in case of low throughput networks. So that's why we have a pre-staging platform backup, which is here. Once that is installed, and this installation will take a little bit of time, let me see if I can get the, and there are about 1200 packages, let me, I'm sorry I cannot show the GUI interface of that, but if we can go through the script, if need be, would that be okay? Or if you have any questions at this point, we can dive into answering, I can dive into answering questions. Why don't you come here? Passport is, there's a search comment is here. Which one? Yeah. Yeah, I'm not sure what's, might be that, it's a cheat wheel. Yeah. Yeah, unfortunately. Yeah, sorry, it's, yeah, it's okay, I'm working on that one. Well, it does read it. Pardon me? Yeah, but the other portion is not, unfortunately. We use it another laptop. Okay, thanks. Firefox, yeah. Okay. So, finally we made it, thanks, Ellie, S-T-A-T-R-L-I-N-G. That's the default password of Starling X. We saw this graphic of this earlier today. When you log in into the horizon of the system controller, the first thing that you see is the subcard, it is this page. If you want to go to the system controller, you basically choose region one, and we see that what system is down, what system, the state of each system. We dive into that system, and you know this information probably much better than I do. But what it also does is, from a sub-cloud perspective, so once we log in onto the sub-cloud, we can see that the sub-cloud is completely in sync. It is online, and that we can dive into the host detail and the level of information that is shared from the sub-cloud, or that we can extract from the sub-cloud into the system controller, the amount of memory storage. So, we don't have self-configured on this as well as the ports. The default system basically, the default weird model that you get from the tools project comes with four ports or four interfaces, and two of which are accelerated, as you can see here, VFIO. And two of them are just generic. We allocate one of them to the management. It is possible to also use only one port for that purpose. I know there is no way for me to go complete it over this, simply because we don't have the time, but are there any questions at this point? Sorry, I didn't hear you. The requirement for... Oh, hardware requirement. The default hardware requirements for Starling X or Outland, basically, but our Outland on the Starling X page, it wants you to have a number of these storage devices like 500 gig for the primary, and if you want to use SAF, it recommends to have another two SSDs, 200 or 250 gig each, depending on how much you store. You can have installed without SAF, and you can reduce the size of the primary disk. Memory requirement for each VM is about 18 gig. Again, that is something that can be played with. The interfaces, here the interfaces are virtual, but you can always pass in physical interfaces. You won't have SRIOV. Or you will not be able to create SRIOVs, but you are able to pass in physical device, create a PCI pass through. That would be one. And you can do the same thing, not only just with NICS, but also with other devices like GPU. You can pass a GPU as well. Fortunately, my demo doesn't work, which is... Yeah, I noticed. Yeah, I mean, you are familiar with the horizon. Any questions on this front? Let me switch back to my own laptop, and I'd like to point out a couple of them. So one area that I want you to take away with is this page. That is basically the documentation. If we go to the build, it's a pretty good... I think so. I think that would be a better approach to do that than... And I will do that. Here, basically, the requirement is outlined for the workstation, 32-gig of RAM and 500-gig for disk. That is for the build. So pretty much the same system can be used for running the test or for playing with Starling X installation. Once the build is completed, it produces a boot image.iso. Takes a little while for it to complete, but it produces a boot image.iso that you will need to pass in using the script that I pointed out. And I will post everything on Starling X or via PowerPoint. I can, unfortunately, not complete the demo, but that was one that I wanted to show. Then the other thing that I wanted to show is the download page that is this guy. And then Starling X documentation is also a pretty good documentation that you can... That outlines pretty much where I get most of my info from. And it starts with the installation guides. And we are at Starling X6. And these are the different models. Distributed cloud is somewhere down here. So, yes, so we will work on... I will work on recording this demo and posting that on Starling X.io. Thank you. It's all my fault, I know. I will sacrifice beer tonight after the meeting. Okay. Thank you.