| 8 Feb 2024 |
 adamcstephens | I think I envision something like microvm.nix that configures what resources incus should have, but then also doesn’t tightly couple the guest configs to the host | 01:50:43 |
| adamcstephens | I have a homegrown deployment tool but it’s effectively using nixos rebuild target host | 01:51:18 |
 mkg20001 | In reply to @adam:robins.wtf
I think I envision something like microvm.nix that configures what resources incus should have, but then also doesn’t tightly couple the guest configs to the host there is already have the virtualisation.diskSize, etc options from qemu which may be what you want. that could be generalized. | 01:52:01 |
 aanderse | ah | 01:52:12 |
| aanderse | yeah so i found myself needing terraform resource values in my nixos config... but at the same time needing nixos values inside my terraform config | 01:53:15 |
| aanderse | this is something nixops did well | 01:53:32 |
| aanderse | i hacked a little script together and am trying it out for deployments | 01:53:59 |
| aanderse | it pairs colmena and terraform together | 01:54:18 |
| aanderse | specifically I'm using it with lxd though | 01:54:29 |
| adamcstephens | Are you planning to stick with lxd or migrate to incus? | 01:55:38 |
| aanderse | so you write a colmena deploy like normal
but
you can add terraform in the same file, just write the terraform as nix instead of hcl
in addition your nixos gets access to your evaluated terraform objects and your terraform objects get access to you nixos configs | 01:56:22 |
| aanderse | we run lxd on Ubuntu
we provide our own images
so we'll stick to Ubuntu for now because their decisions don't impact us yet
we're keeping an eye on the situation though | 01:57:15 |
| adamcstephens | Ok, so if I float deprecating lxd server on nixos it won’t impact you :) | 01:57:51 |
| aanderse | yeah i mean i kinda wish we could keep both.. but I'll definitely support you if you want to remove it
no impact here | 01:59:23 |
| mkg20001 | looked at colmena, it's really nice. might switch to it | 01:59:27 |
| mkg20001 | btw, if anyone has the need to use nixos things on non-nixos to let's say run incus I'm working on a solution for that at work https://github.com/mgit-at/nix-unify | 02:00:24 |
| mkg20001 | basically just symlinks the systemd services into the host's /etc/systemd, plus some other stuff (adding users, etc) | 02:00:53 |
| adamcstephens | I’m not opposed to keeping lxd in tree, but I wont be running it anymore so someone else would need to step up to own it | 02:00:58 |
| adamcstephens | In reply to @mkg20001:mkg20001.io
btw, if anyone has the need to use nixos things on non-nixos to let's say run incus I'm working on a solution for that at work https://github.com/mgit-at/nix-unify Neat! | 02:01:50 |
| aanderse | mkg20001: did you look at system manager by numtide? | 02:02:09 |
 hexa | In reply to @adam:robins.wtf
I’m not opposed to keeping lxd in tree, but I wont be running it anymore so someone else would need to step up to own it ideally we wouldn't let it linger if nobody stepped up to maintain it | 02:02:28 |
| adamcstephens | Agreed. | 02:02:40 |
| adamcstephens | My current plan is deprecate prior to 24.05 branch off and remove shortly after. | 02:03:25 |
| hexa | feel free to create an issue and add it to 24.05 blockers | 02:03:49 |
| mkg20001 | In reply to @aanderse:nixos.dev
mkg20001: did you look at system manager by numtide? no. had a look on it. the idea with nix-unify is to use things as if already using nixos (e.g. use the existing modules), while system manager allows just managing some state the nixos way. | 02:04:42 |
