gchristensen changed the topic of #nixops to: NixOps related talk | logs: https://logs.nix.samueldr.com/nixops/ https://meet.jit.si/NixOpsReview
pbb has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
pbb has joined #nixops
meh` has quit [Ping timeout: 256 seconds]
andi- has quit [Ping timeout: 272 seconds]
andi- has joined #nixops
Ariakenom has joined #nixops
Ariakenom has quit [Ping timeout: 272 seconds]
Ariakenom has joined #nixops
meh` has joined #nixops
Ariakenom has quit [Quit: WeeChat 2.7.1]
Ariakenom has joined #nixops
Ariakenom has quit [Quit: WeeChat 2.7.1]
Ariakenom has joined #nixops
meh` has quit [Ping timeout: 258 seconds]
Ariakenom has quit [Ping timeout: 246 seconds]
Ariakenom has joined #nixops
Ariakenom has quit [Ping timeout: 260 seconds]
virus_dave has quit [Quit: virus_dave]
dongcarl has joined #nixops
Ariakenom has joined #nixops
meh` has joined #nixops
Cadey1 has quit [Quit: Idle for 30+ days]
Ariakenom has quit [Ping timeout: 264 seconds]
Ariakenom has joined #nixops
Ariakenom has quit [Ping timeout: 260 seconds]
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixops
<{^_^}> nix-community/nixops-libvirtd#9 (by onixie, 13 weeks ago, open): Network resource support for libvirt backend
<gchristensen> I love it when my problems are solved for me
<gchristensen> ok libvirtd is good actually
<adisbladis> gchristensen: You can in fact haz review :)
<gchristensen> =)
<gchristensen> I'mma need to rebase this one: https://github.com/nix-community/nixops-libvirtd/pull/9 b/c I need this feature yesterday (I bodged it for yesterday)
<{^_^}> nix-community/nixops-libvirtd#9 (by onixie, 13 weeks ago, open): Network resource support for libvirt backend
<adisbladis> gchristensen: Hmm
<adisbladis> God, the docs around this are confusing
<adisbladis> Lgtm and seems to work
<cole-h> Not necessarily nixops related, but I'm rebuilding my kernel (and with it v4l2loopback) so I'll be able to hop on next time a review session happens ;^)
<adisbladis> But I'm not sure I grok the what `allocation` is really supposed to represent
<gchristensen> adisbladis: literally no clue
<gchristensen> adisbladis: can you hit the approve button, or smash the merge?
<adisbladis> Wow, you sniped my merge click :P
<adisbladis> The button literally disappeared under my pointer
<gchristensen> oops
<gchristensen> sorry :P
<adisbladis> Haha =)
<adisbladis> gchristensen: Btw, really nice catch
<adisbladis> I guess why I never caught it is because I'm using tmpfs for pretty much everything
<gchristensen> for goodness sakes it was a wild guess and I was steaming with rage when I confirmed it, haha
<adisbladis> I'd never have thought compression would be a culprit for.. Anything
<gchristensen> same
<gchristensen> I also don't understand why qemu calls the size on disk actual size
<gchristensen> like at this point what even is actual size
<adisbladis> Nobody knows
<gchristensen> thanks for the review :)
<gchristensen> #9 doesn't look like a nice one to rebase.... maybe later :P
meh` has quit [Ping timeout: 246 seconds]
meh` has joined #nixops
meh` has quit [Ping timeout: 260 seconds]
<monokrome> hmm... I set deployment.targetUser but it still tries to use root... Any ideas?
<gchristensen> what command are you running?
<monokrome> nixops deploy -p cluster
<monokrome> I created cluster with `nixops create`
<gchristensen> oh whath is -p?
<gchristensen> and what version of nixops?
<monokrome> tbh I have no idea what I'm doing, so just trying to get it to deploy to a server I just made here
<monokrome> I meant -d
<monokrome> somehow I read it upside down lol
<gchristensen> (gotcha, cool)
meh` has joined #nixops
<monokrome> v1.7
<monokrome> I just set up a regular nixops machine here in my room
<monokrome> and it has SSH enabled
<monokrome> but I don't want to enable SSH root login
<gchristensen> ah, targetUser requires bleeding edge nixops master :)
<monokrome> oooh >.<
<monokrome> what
<monokrome> so I guess I should permit root login? O_o
<gchristensen> yeah
<monokrome> ok
<monokrome> ty ^.^
<monokrome> when I run "nixops deploy -d mycluster", what password is it asking for?
<monokrome> oh I guess it's just my SSH password
<monokrome> gchristensen: Does it replace the entire nixos configuration?
<monokrome> or does it just add whatever is over /etc/nixos/configuration.nix?
<gchristensen> it completely ignores /etc/nixos/configuariton.nix and any other nix config on the target machine
<gchristensen> you'll need to replicate both configuartion.nix and the hardware-configuariton.nix in to your network.nix
<danderson> I... think I asked this before, but: is there some escape hatch where the configs are _somewhere_ on the machine, so I can do and nixos-rebuild if I have to for whatever reason?
<danderson> (no specific scenario in mind, I just have trust issues with deployment tools, from bitter experience :D)
<monokrome> can I still use the same imports?
<gchristensen> danderson: no
meh` has quit [Ping timeout: 258 seconds]
<monokrome> hmm seems like maybe I can =^.^=
<monokrome> that's pretty cool
<gchristensen> danderson: you could carefully construct your configuration to work like that, though
<monokrome> wow it worked =^.^= !!!!
<monokrome> how cool!
<gchristensen> just copied the files over and imported them?
<monokrome> yeah
<monokrome> then I did
<monokrome> host = (import ./myhostname/default.nix);
<gchristensen> nice
<monokrome> although I need to figure out how to make some of the values in there more abstract
<monokrome> like setting deployment.targetHost to the imported networking.hostName
<monokrome> guessing I can do that with `with` keyword or something
<gchristensen> you could do host = { config, ... }: { deployment.targetHost = config.networking.hostName; imports = [ ./myhostname ]; };
<monokrome> oooh I didn't know I can just set `imports = []`
<monokrome> thanks!
<gchristensen> yep
<monokrome> { config, ... } will come from the import?
<gchristensen> yeah, { config, ... }: the `config` parameter contains the final system configuration
<gchristensen> (that means you can't do { config, ... }: { foo = "${config.foo}bar"; } because you can't access something and change it too)
<monokrome> well that's some wild recursive magic
<monokrome> :D
<gchristensen> haha yeah it is
<monokrome> wow this is so cool!
<monokrome> thanks for showing me :)
<gchristensen> gladly =)
<monokrome> The hashedPassword can't be shared between machines can it?
<gchristensen> sure
<energizer> builds happen on the local machine, not the remotes, right?
<gchristensen> right
<monokrome> oh weird
<energizer> what's the reason for that?
<gchristensen> { myhost = { foo = "bar"; }; otherhost = { nodes, ... }: { foo = nodes.myhost.foo; }; }
<gchristensen> energizer: well, usually I want to build on my powerful build machine and deploy from there -- using minimal remote resources. an option to build on the remote would probably be pretty cool.
<energizer> gchristensen: ah, so the idea is it builds "locally", but in common cases local builds are actually run on separate build machines
<energizer> right?
<energizer> and the target machines can be given access to some build cache where the build machines placed the completed builds, so my little laptop doesn't need to actually transfer any of the built artifacts to the remotes
<energizer> is that the normal workflow?
<monokrome> gchristensen: So, just to make sure, when I reboot my physical machine it'll boot into the new builds from nixops now?
<monokrome> like I can just delete /etc/nixos?
<energizer> supposing you say yes. is there some flag i can use to ensure the data doesn't flow through my laptop, like --force-targets-use-caches
<gchristensen> you never needed /etc/nixos to boot anyway :)
<monokrome> yeah but I just wanted to make sure it was overwriting the config like I think
<monokrome> and not doing something weird
<monokrome> seems like it is :D
<monokrome> so cool
<energizer> still interested in the answers to those questions if anybody has ideas
globin_ has quit [Ping timeout: 260 seconds]
globin_ has joined #nixops