From dd4147a7e051e939a5ba722496fa5e8c52eee70f Mon Sep 17 00:00:00 2001 From: Muhittin Kesikli Date: Tue, 11 Aug 2026 08:33:29 +0200 Subject: [PATCH] add link to iso generation repo --- docs/04-For Operators/03-deployment-guide.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/04-For Operators/03-deployment-guide.mdx b/docs/04-For Operators/03-deployment-guide.mdx index ce58e0e0..b42851f3 100644 --- a/docs/04-For Operators/03-deployment-guide.mdx +++ b/docs/04-For Operators/03-deployment-guide.mdx @@ -573,7 +573,7 @@ The Edgerouters has to fulfill some requirements including: ### Management Servers -The second bastion hosts are the management servers. They are the main bootstrapping components of the Out-Of-Band-Network. They also act as jump hosts for all components in a partition. Once they are installed and deployed, we are able to bootstrap all the other components. To bootstrap the management servers, we generate an ISO image which will automatically install an OS and an ansible user with ssh keys. It is preconfigured with a preseed file to allow an unattended OS installation for our needs. This is why we need remote access to the IPMI interface of the management servers: The generated ISO is attached via the virtual media function of the BMC. After that, all we have to do is boot from that virtual CD-ROM and wait for the installation to finish. Deployment jobs (Gitlab-CI) in a partition are delegated to the appropriate management servers, therefore we need a CI runner active on each management server. +The second bastion hosts are the management servers. They are the main bootstrapping components of the Out-Of-Band-Network. They also act as jump hosts for all components in a partition. Once they are installed and deployed, we are able to bootstrap all the other components. To bootstrap the management servers, we generate an [ISO](https://github.com/metal-stack/bootstrap-debian) image which will automatically install an OS and an ansible user with ssh keys. It is preconfigured with a preseed file to allow an unattended OS installation for our needs. This is why we need remote access to the IPMI interface of the management servers: The generated [ISO](https://github.com/metal-stack/bootstrap-debian) is attached via the virtual media function of the BMC. After that, all we have to do is boot from that virtual CD-ROM and wait for the installation to finish. Deployment jobs (Gitlab-CI) in a partition are delegated to the appropriate management servers, therefore we need a CI runner active on each management server. After the CI runner has been installed, you can trigger your Playbooks from the the CI. The Ansible-Playbooks have to make sure that these functionalities are present on the management servers: