gchristensen changed the topic of #nixops to: NixOps related talk | logs: https://logs.nix.samueldr.com/nixops/ https://meet.jit.si/NixOpsReview
cole-h has quit [Quit: Goodbye]
typetetris_ has joined #nixops
kalbasit_ has joined #nixops
infinisi1 has joined #nixops
sparogy has quit [*.net *.split]
infinisil has quit [*.net *.split]
kalbasit has quit [*.net *.split]
typetetris has quit [*.net *.split]
typetetris_ is now known as typetetris
kalbasit_ is now known as kalbasit
sparogy has joined #nixops
infinisi1 is now known as infinisil
cole-h has joined #nixops
teto has joined #nixops
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixops
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixops
meh` has joined #nixops
<meh`> are there any docs on using plugins on master? or is this stuff still too unstable? I'm trying to deploy to a remote libvirt
<adisbladis> meh`: The libvirt plugin is not yet up to date. We're still working on getting the aws plugin compatible with master.
<gchristensen> it turned out to be a real big project. a lot of surprising code in the aws plugin
<meh`> adisbladis, is there any way I can speed this up?
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixops
<adisbladis> meh`: I could take a look, but I think it's very similar scope as the vbox one.
<adisbladis> If you want to tackle it look at the nixops-vbox pull request doing the compat fixes
<adisbladis> Updates on the nixops-aws situation: It turned out to be a massive undertaking, but we're almost there!
<adisbladis> Three different PRs required across three different repos:
<{^_^}> nixops-aws#103 (by adisbladis, 18 hours ago, open): Add mypy types
<adisbladis> https://github.com/NixOS/nixops/pull/1355 <- some minor changes required to nixops itself
<{^_^}> nixops#1355 (by adisbladis, 3 minutes ago, open): Nixops aws compat
<adisbladis> https://github.com/nix-community/nixos-modules-contrib/pull/1 <- nixops-aws dependes on autoluks, so make modules-contrib a nixops plugin
<{^_^}> nix-community/nixos-modules-contrib#1 (by adisbladis, 10 minutes ago, open): Add support for using repo as a NixOps plugin
<cole-h> Oooh, shiny
<pistache> is it okay for NixOps backends to use SSH to the host ? I didn't see any other backend doing that
<gchristensen> ideally they'd all use runCommand
<pistache> sorry, not sure if I understand you, I meant to the host that hosts the container I'm deploying to
<pistache> I'm attempting to write a NixOps backend for LXD, and I'd like to allow the containers to share their Nix store with the host
<adisbladis> pistache: Currently, yes.
<adisbladis> Wait a minute
<{^_^}> nixops#1353 (by adisbladis, 1 day ago, open): Add support for pluggable transports
<pistache> oh right
<pistache> right, thanks a lot
<pistache> and thanks for all that recent work on NixOS, the changes look awesome and promising
<pistache> on NixOps*
<adisbladis> =)
<adisbladis> pistache: I'm not 100% sure that's the final design, btw
<adisbladis> For one I'm considering if transports shouldn't be responsible for https://github.com/NixOS/nixops/pull/1353/files#diff-6ea77fd00d5f092f8150c2398eaf53d8R488-R492 themselves
<adisbladis> And https://github.com/NixOS/nixops/blob/e75bbd282cb67429ef870b12920e6e1d8ae4aefb/nixops/backends/local.py#L15 is a bit awkward, it should really be a simple type annotation
<adisbladis> Not an assignment
<pistache> adisbladis: thinking about it again, I don't think the local transport could be used for what I want to do
<pistache> can my backend use two different transports ? one to the container, and one to the container's host
<adisbladis> What do you need to do on the host?
<pistache> I'd like to allow my containers to share their Nix store with the host
<pistache> so I'd want to copy the closure to the host instead of the container
<adisbladis> That could be done
<adisbladis> run_command needs to run in the container context, but copy_closure could do something entirely different
<pistache> ah right, so I'd have to subclass Transport myself to do that
<adisbladis> Nah, Transport is a Protocol
<adisbladis> You'll see LocalTransport doesn't inherit from anything
<adisbladis> It's just an interface
<adisbladis> But yeah, you'll need to implement your own backend with your own transport
<pistache> ah yes, missed that, meant my own transport
<pistache> cool, thanks for the pointers
<adisbladis> This is still not merged, mind you
<pistache> yes, right now I'll continue using my own SSH() and will watch for that pluggable transports PR
<meh`> adisbladis, think I'd be able to tackle this considering I'm 1 week new to Nix?
<meh`> I don't mind putting in the work, I need it :D
<adisbladis> meh`: Maybe, there are quite a lot of pieces so I'm not sure it's the best beginner task
<adisbladis> There has been work done here https://github.com/nix-community/nixops-libvirtd/pull/10
<{^_^}> nix-community/nixops-libvirtd#10 (by grahamc, 7 weeks ago, open): Poetry2nixify
<adisbladis> But there is still a lot to do
<meh`> adisbladis, trying out the pull request, thanks
<adisbladis> meh`: There is still a lot of work to do around parsing, and tbh this is not all too well documented
<adisbladis> Re the xml bits that is documented in https://github.com/NixOS/nixops/blob/master/doc/plugins/authoring.rst
<meh`> adisbladis, understandable, right now I'm only in a hurry to deploy a couple VMs on a hypervisor I set up, made the choice of going with NixOS and NixOps for the infrastructure for my company, and didn't realize until now NixOps was going through such a transition :P
<adisbladis> meh`: You should be fine on NixOps 1.7?
<adisbladis> Is there any reason you're trying to build against master?
<meh`> adisbladis, I'm not a very smart man, and wanted to deploy both hypervisor and guests with nixops, so needed remote libvirt
<adisbladis> And this is not possible on nixops 1.7?
<meh`> adisbladis, nope, the patch for that was merged a couple months after release
<adisbladis> meh`: Try this :) http://ix.io/2nxh/nix
<meh`> adisbladis, I'll give it a shot tomorrow, for now thanks a bunch, time to try and sleep!
meh` has quit [Ping timeout: 260 seconds]
cole-h_ has joined #nixops
cole-h has quit [Ping timeout: 256 seconds]
cole-h_ is now known as cole-h