 Hello anyway. My name is Andrea Fasano, and I work as a principal software engineer in Red Hat issue in the Core Installer Team. Anyone here familiar with the OpenShift installation process? Cool, so today I'm going to talk and introduce to you the own base installer which is a relatively new project, we have developed aspl Woman, who noticed, for simplifying the installation of open shift. And I like to try, let you know, its main features, and I tried to give a quick glance of how it works, under the hood, to let you understand if it's something that could suit your need or not.... Since it's a lightning tool, I tried much as possible faster, without dipnенных much into the tata. Hvala razgleda vrst, da sem razkazal po prostju, in po vsi zašličenje sem jaz sem poznat po vsega. Načimiljamo, kdo je tudi izgledan izgledan izgledan izgledan izgledan. Vsešč mi je zemljena, da vso respečno izgledaj tudi prejdičenje, znečenje, z sodateljnji izgledan izgledan izgledan z vsem teknologijom, z njemnim radom, ki je vzgleda in izgleda. Vzgleda in izgleda in z vzgleda ne tako in za internet vzgleda. In več in prizvam, da sem taj početnju naredila in izgleda. Zelo, da je bilo več vzgleda od pomečnjih, še vstvarne vzgleda in tudi tudi vzgleda. Prvom je vseču stavljenje z vsoj izu, da ima vsečenje srečenje za snedljenje. Danes izu je zelo vznat kaj je vršnjenj srečenje, vsak ki je vzelo v pomečnju, in vsečo zelo vzelo vzelo v pomečnju, in zelo. Zelo se naredati na srečenje kaj je zelo, 3 stepo, da vse zelo prišlično. Ako je začala, da vse pridem, nekaj, nekaj, kar kako se prišlično. Prvom, je to zelo, da je obitelj, da je vsoječen. Nače bi je zelo, da je vsečen. Zelo, da je, da je, da je, da nekaj, priročen. Nače je, da je, da je, da je, da je, da je, Bootsrap node. So, this means that you don't need an additional machine for the installation. Probably one of the most relevant part is the ability to run a high number of preflight validations, thanks to the assisted installer technology. And these will help you to understand if the upcoming installation is going to succeed or not. In, tisto, je vseč vseč automatično, če je, da, različno je način, nami ne bi se vseči vseči, in je zelo, da je vseči in vseči in v ter partijorke srednosti. In zelo, da je ovo je bolj, da vseči je vseči, da je vseči vseči, zelo, da je vseči, da je vseči, da je vseči, da je vseči, da je, da ne, implementacijo. Poblok je praco in tudi, da v velikom počinakove zvori však ne potrebno. Kaj su to zdajanje pa? Poblok je, da zelo, da se ne musel spravo čusti, ki pa tega. Ne zelo, da bo jo izblokno počinak, kar se našli, changing tist Dr. Tama je, čas je, izpravljena, tudi mobilize, ne je, da nesel počinakov. kompozivno z vsego noga, in dopozivno vsega, permetal in vsega platforma. Vsega na vsega premizija. Tukaj počutimo, kako se vsega vsega vsega vsega vsega vsega vsega vsega vsega vsega vsega vsega vsega vsega vsega vsega vsega vsega pristostnem počutim, kako se naše obšta vsega vsega najsstavne. Držatimo dovolj do academija. Sveš vidiš, da sem poznala alkoholik vsega vsega. Fzikta vsega vsega vsega vsega vsega pristolja počutim pri vsega klasne. Vsega potrebe od svega vsega vsega vsega vsega. We have a new entry, the agent config. This is an additional piece of configuration that will let you define a couple of interesting things. The one that it takes away for you is the rendezvous IP. This is mandatory. So here you have to define the IP that will act as a bootstrap during the installation. All the other properties are optional. For example, the possibilities, as we said, to define static network integration for each host involved in the installation. This could be useful, for example, if you want to define a static IP addressing. Once you are ready, you can use a new command, sub command available in the OpenShift installer, which is agent create image. It will perform a number of static checks, and if everything goes fine, it will generate an agent iso. What is the agent iso? It's nothing else than a live ARCOS image with a customized ignition file prepared by us containing all the ingredients for baking up the automatic installation subsequently. I think that you could already start to appreciate the fact that the iso could be generated in an environment that is completely different from the one where you are going to deploy the cluster and potentially by also a completely different person. Okay, let's say that we have the iso, so let's move to the environment that will host the deployment of the newly created cluster. We assume to have an isolated network. We assume to have enough nodes, machines available, in this case, three nodes. Master zero has been colored with a different coloring just to highlight the fact that later it will be identified as a rendezvous host. And since we are in a disconnected environment, the other assumption is the ability to have a registry with a release payload already mirrored into it. Given that, we take our iso, we load it into each node and we boot them up. So let's now dive into each node, let's try to understand what happens after the boot process starts. First of all, since it's a live iso, everything will be loaded in memory. So the first thing is that the ignition file that is embedded within the iso get applied and all the necessary files and services are copied and started and they will be fundamental for the subsequent steps. At the very early stage during the boot process, it will happen two important things will happen. First of all, if you provided the static network configuration, it will be applied. So in this case, we assume that VIPs have been statically assigned. Secondly, it will start to check if the release payload is reachable in the environment. Why this? Because if you cannot get the release payload, you cannot start the installation. This will be performed by an agent UI or textual user interface. So a sort of interface that will be visible in the console of the instance. And in case of problem, it will give you some additional information to troubleshoot the problem. And you will have all stability to tweak the network configuration for a last-minute fix. That's important because if there was a small misconfiguration, you could fix it without the need of rebuilding the iso. If everything goes well, at this point, the agent service or the assisted installer is launched on every node. And this will be the soldier that will perform most of the back activity. At this point, a special thing happened on the master zero. On master zero, which was identified to be around the worst, the assisted service is launched. The assisted service is the main orchestrator of the installation. It's the one that will take care of deciding what are the next steps. And at this point, the agents have been collected hardware information about each node and they try to discover and connect to the assisted service registered on the master zero. Once all the agents have been registered, the assisted service will start the pre-flight validation to ensure that, for example, every node has enough memory, enough CPUs, enough disk space and so on. And eventually it will inform the user to fix the problem before moving on with the installation. Let's assume that everything went fine. At this point, a number of simultaneous things happens. First of all, still on the, around the worst, the cluster bootstrap is launched and it will load the temporary control plane for the installation. But I remember that we are still working in memory. We still need to write the arcos image on every instance. So the assisted service issues the command to write the image on every node. And the image is retrieved from the release payload if available. So again, fully compatible with disconnected environment. As soon as the image has been written on the nodes, the assisted service issues a command to the other nodes to reboot themself. So they reboot and they try to join the control plane following the normal installation steps. If everything goes fine and so if master one and master two were able to join the control plane, assisted service issues the command to reboot itself. And again, if everything goes fine, master zero will join the control plane, will throw away everything that was in memory and will become just a yet another node as the other. From a user point of view, there is another useful command, agent wait for install complete that will let you monitor the progress of the installation. This is an example extracted where you can see the kind of validations that are performed and how they are printed on the console. And if everything goes well, it will inform that the installation is completed and you will give you the coordinates to attach to the cluster. So this brings to the end of my presentation. What's next? We are still working on supporting OKD. There is an excellent community also here that is working on this part. And I hope we'll have it available very soon. We are also working on pixie support so that you will not be limited just to the eyes but also to use pixie for booting the instances. And I would like to acknowledge the original team that more than one years ago started to work on this new project. Thank you. Are there any questions in the room? How long the user is valid? How long is the user valid? Because it's at the castle so no longer valid. How long is the user valid that I can avoid? OK, you ask it how long the user is valid. Well, I think the certificates, if I'm not wrong, should be ten years. If I'm not wrong, but should be verified. Other questions? Yes. You mentioned something about ZTP, I've been involved into that. I mean, I'm interested how does this integrate with the whole flow of ZTP. Maybe I don't mind the question. Yeah, in reality, the question is, sorry, is how does it work and how it integrates with ZTP. In reality, we aim to maintain full interoperability with ZTP. When we started from install config in agent config internally, they are converted in ZTP manifests. And they are uploaded. When we talk with sister service, we talk in terms of ZTP manifests. The idea is that if you already deployed a cluster also with ZTP, ideally you could take your ZTP manifest and apply them with agent-based installer with almost zero problem refactor. How does it know what the inventory history is for the payload? Is that something you configured in the demo? Yes. It's configured in the install config for disconnected environment. There is a section, the ICSP section, where you can configure how to eventually reach a mirror-red environment. The idea is that in the registry, it's there a complete release space so that you don't have to touch or to reach completely outside the internet for the installation. Can you use the default registry? Yes, of course. It depends on if you put it or not in the install config. If you can repeat the... Yes, the question is how do we know how to reach the registry. Is there any other... Very much, then. Thank you.