kalipso/infrastructure
1
1
Fork 1
Code Issues 43 Pull Requests 3 Actions Projects 2 Releases Wiki Activity

[docs] update microvm docu
All checks were successful
Evaluate Hydra Jobs / eval-hydra-jobs (push) Successful in 3m45s
Details
Evaluate Hydra Jobs / eval-hydra-jobs (pull_request) Successful in 3m53s
Details

Browse Source
This commit is contained in:
kalipso
2024-11-21 14:55:24 +01:00
parent 100ddf2cd4
commit 39972efc7c
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
doc/src/anleitung/microvm.md
View File

@@ -22,6 +22,8 @@ It seems to be necessary to run this as root so that the according tap interface
To be able to ping the VM or give Internet Access to the VM your host needs to be setup as described below. To be able to ping the VM or give Internet Access to the VM your host needs to be setup as described below.
### Host Setup ### Host Setup
#### Network Bridge
To provide network access to the VMs a bridge interface needs to be created on your host. To provide network access to the VMs a bridge interface needs to be created on your host.
For that: For that:
- Add the infrastructure flake as input to your hosts flake - Add the infrastructure flake as input to your hosts flake
@@ -37,3 +39,14 @@ networking.nat = {
externalInterface = "eth0"; #change to your interface name externalInterface = "eth0"; #change to your interface name
}; };
``` ```
#### Auto Deploy VMs
By default no MicroVMs will be initialized on the host - this should be done using the microvm commandline tool.
But since we want to always deploy certain VMs it can be configured using the ```malobeo.microvm.deployHosts``` option.
VMs configured using this option will be initialized and autostarted at boot.
Updating still needs to be done imperative, or by enabling autoupdates.nix
The following example would init and autostart durruti and gitea:
``` nix
malobeo.microvm.deployHosts = [ "durruti" "gitea" ];
```