| 24 Jun 2022 |
dantefromhell | In reply to @schnecfk:ruhr-uni-bochum.de I'm not really helpful here, but just for clarification: Are you referring to these Issues? https://github.com/zhaofengli/colmena/issues/42 and https://github.com/zhaofengli/colmena/issues/68 thx for clarification: Yes. In particular #68 but #42 includes some hints towards bootstrapping/ first OS install. | 02:10:10 |
dantefromhell | I am not looking to automate provisioning of cloud resources (aka their creation) with colmena but the first OS installation (bootstrapping) of cloud and physical servers. | 02:11:17 |
lemmalamma | Redacted or Malformed Event | 02:33:58 |
lemmalamma | In reply to @dantefromhell:matrix.org thx for clarification: Yes. In particular #68 but #42 includes some hints towards bootstrapping/ first OS install. I had no idea people use Nix for this. I used to do PXE boot. But now most IaaS bundle those 2 things together. For example, you ask for (provision) an EC2 instance running an AMI image (bootstrap). Is your use case like a local bare metal setup? | 02:38:38 |
hexa | hm, when I set up wireguard tunnels through networkd and I store secrets in /run/keys, with colmena I have a wireguard-privatekey-key.service unit | 10:46:21 |
hexa | how do I tie that into networkd while making sure that networkd does in fact setup the WAN networking so I can provide those keys | 10:46:48 |
hexa | with morph I had an action to restart networkd post upload | 10:49:35 |
hexa | and let networkd fail on bootup | 10:49:45 |
hexa | with a networkd-restart.service that waits for wireguard-privatekeys-keys.service? 😄 | 11:04:39 |
Linux Hackerman | hexa: set postStart on the key unit, to run networkctl reconfigure $if? | 11:04:52 |
Linux Hackerman | Not sure a restart is even needed? | 11:04:59 |
hexa | oh yeah, that sounds neat | 11:05:11 |
Linux Hackerman | Or yeah a separate service could be cleaner. | 11:05:18 |
hexa | I can't really be arsed to enumerate the repositories | 11:05:22 |
hexa | * I can't really be arsed to enumerate the interfaces | 11:05:30 |
Linux Hackerman | Just reconfigure then :D | 11:05:44 |
hexa | well, now it feels obvious 😄 | 11:08:14 |
hexa | I think I was stuck in my head somewhere | 11:08:21 |
Linux Hackerman | Happens :D | 11:09:32 |
hexa | ❯ colmena build
[INFO ] Using configuration: /home/hexa/git/hexa/nixos-servers/config/hive.nix
[INFO ] Enumerating nodes...
error: attribute 'type' missing
at /nix/store/agbalx3d9vi1sd132w5qs4p6i3brya1f-nixos-22.05-src/lib/modules.nix:615:26:
614| else if optionDecls != [] then
615| if all (x: x.options.type.name == "submodule") optionDecls
| ^
616| # Raw options can only be merged into submodules. Merging into
Did you mean _type?
(use '--show-trace' to show detailed location information)
[ERROR] -----
[ERROR] Operation failed with error: Child process exited with error code: 1
| 11:28:23 |
hexa | this is a fun one. | 11:28:34 |
hexa | because nowhere in the trace there is a reference to the module in question | 11:28:54 |
hexa | do people tend to write scripts around colmena for:
- apply boot
- reboot
- unlock
- upload secrets
| 13:15:17 |
hexa | with morph I could do morph deploy default.nix boot --reboot --upload-secrets | 13:15:32 |
hexa | and colmena seems to upload secrets uploadAt=post-activation on applies with goal=boot directly after uploading the closure | 13:16:39 |
hexa | which is quite pointless when the secrets are volatile | 13:16:49 |
hexa | * and colmena seems to upload secrets with uploadAt=post-activation on applies with goal=boot directly after uploading the closure | 13:17:07 |
hexa | ah, reboot handling is part of 0.4.0 | 13:22:30 |
hexa | In reply to @linus:schreibt.jetzt Just reconfigure then :D lol nope. can't reconfigure interfaces that don't exist, because of missing prerequisites | 15:10:01 |
hexa | so restarting networkd it is | 15:10:05 |