diff options
| author | Pjotr Prins | 2023-09-26 14:49:38 -0500 |
|---|---|---|
| committer | Pjotr Prins | 2023-09-26 14:49:38 -0500 |
| commit | a4d7a99478397f8e241dc70b0fe70f804964e93b (patch) | |
| tree | 7e5a973230e91d3b4ec930558dc94d3000ee404b | |
| parent | 1df685beaa10b2fabf696d56e7680d881373947f (diff) | |
| download | gn-gemtext-a4d7a99478397f8e241dc70b0fe70f804964e93b.tar.gz | |
Machine room
| -rw-r--r-- | tasks/machine-room.gmi | 20 | ||||
| -rw-r--r-- | topics/guix-system-containers-and-how-we-use-them.gmi | 2 |
2 files changed, 21 insertions, 1 deletions
diff --git a/tasks/machine-room.gmi b/tasks/machine-room.gmi index 83e562b..6611f40 100644 --- a/tasks/machine-room.gmi +++ b/tasks/machine-room.gmi @@ -16,10 +16,30 @@ + see also ../issues/systems/decommission-machines.gmi * [ ] Install tux04-tux09 * [ ] VPN access and FoUT +* [ ] penguin2 has 32TB of space we can use on NFS/backups +* [ ] tux04 and tux05 give errors Network: * [ ] use fiber optics for subnet Octopus and Tuxes +* [ ] Octopus11 has no fiber +* [ ] tux06 has temp fiber +* [ ] tux07 has no fiber +* [ ] tux08 has no fiber +* [ ] tux09 has no fiber + +Lambda: + +* [X] racked up and runs +* [+] add network (Roger) + link/ether 7c:c2:55:11:9c:ac brd ff:ff:ff:ff:ff:ff + inet 172.23.18.212/21 brd 172.23.23.255 scope global dynamic eno1 +* [ ] get service tag Tamara +* [X] install ubuntu (with Erik) +* [ ] remote access? (with Erik) + * [ ] get BMC password +* [ ] get fiber working +* [ ] add to Octopus HPC Backups & storage: diff --git a/topics/guix-system-containers-and-how-we-use-them.gmi b/topics/guix-system-containers-and-how-we-use-them.gmi index 22cfa3f..26baca8 100644 --- a/topics/guix-system-containers-and-how-we-use-them.gmi +++ b/topics/guix-system-containers-and-how-we-use-them.gmi @@ -1,6 +1,6 @@ # Guix system containers and how we use them -Our preferred way to deploy long-running services is to use Guix system containers. Note that Guix system containers are different from guix shell containers (and the older guix environment containers). guix shell containers are meant for interactive use and are a poor fit for long running services. Other non-Guix ways such as running long-running processes in tmuxes, running long-running services from your development repository, etc. are a quick dirty way to get things done. Note that system containers are quite a bit heavier - they are full Linux boots. +Our preferred way to deploy long-running services is to use Guix system containers. Note that Guix system containers are different from guix shell containers (and the older guix environment containers). guix shell containers are meant for interactive use and are a poor fit for long running services. Other non-Guix ways such as running long-running processes in tmuxes, running long-running services from your development repository, etc. are a quick dirty way to get things done. Guix system containers are fully described by a configuration file that, among other things, specifies the services run in it. These scheme configuration files are built using `guix system container' and produce a script. This script, when run, starts the described container. |