leon/blog
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update some of the structure of the auto-server-setup post

Browse Source
This commit is contained in:
lol3rrr
2026-04-27 22:49:05 +02:00
parent 0594fd2a77
commit 56bdcc6a36
1 changed files with 18 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
content/auto-server-setup/index.md
View File

@@ -46,6 +46,24 @@ So you specify some machine specific things in my tool:
and then the final configuration for the installer is automatically created. and then the final configuration for the installer is automatically created.
# Help for unknown config/server
This is for cases, where a machine that is not currently configured in the software tries to netboot from it.
There are basically 2 cases, where this might happen:
1. A new machine is supposed to be added and I need to add it to the configuration
2. A machine, that is not intended for netbooting, was accidentally configured to try netbooting
## New Machine to add to Configuration
In this case, we want the machine to boot into a sort of exploritory environment, so one can easily find the required information to add the machine to the configuration.
For this purpose I plan to use a barebones linux setup based on this blog about creating a minimal linux kernel[^blog_tiny_linux_from_scrach].
TODO
## Accidental boot
The main concern in this case is to not accidentally wipe an existing machine, like my personal computer.
TODO
# Why not MAAS? # Why not MAAS?
The simple answer is simplicity and that I wanted to understand how these things work. The simple answer is simplicity and that I wanted to understand how these things work.
Basically even what I am outlining here is already overkill, as I am maybe deploying a new server once every 1 or 2 years. Basically even what I am outlining here is already overkill, as I am maybe deploying a new server once every 1 or 2 years.
@@ -55,10 +73,6 @@ Basically even what I am outlining here is already overkill, as I am maybe deplo
Currently this is mostly still an experimental setup, but I actually want to deploy this for my homelab. Currently this is mostly still an experimental setup, but I actually want to deploy this for my homelab.
For this I am planning on setting up 1 or 2 raspberry pies that might also serve some other critical services. For this I am planning on setting up 1 or 2 raspberry pies that might also serve some other critical services.
## Better help for unknown config
Currently it is a bit annoying to get the first configuration for a client going, because you need to find all the serial numbers etc.
In the long run I want to boot into a minimal live linux setup[^blog_tiny_linux_from_scrach], which one can then use to find all the info needed for setting up your config.
# References # References
[^autoinstall]: [autoinstall docs](https://canonical-subiquity.readthedocs-hosted.com/en/latest/intro-to-autoinstall.html) [^autoinstall]: [autoinstall docs](https://canonical-subiquity.readthedocs-hosted.com/en/latest/intro-to-autoinstall.html)
[^cloud-init]: [cloud-init homepage](https://cloud-init.io/) [^cloud-init]: [cloud-init homepage](https://cloud-init.io/)