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 [Ping timeout: 258 seconds]
nuncanada has joined #nixops
nuncanada has quit [Quit: Leaving]
spudly1 has quit [Ping timeout: 240 seconds]
spudly1 has joined #nixops
cole-h has joined #nixops
<adisbladis> DigitalKiwi: Indeed :D
<DigitalKiwi> adisbladis: ohhi
<adisbladis> After taking a longer break from NixOps I'm doing a push to get a 2.0 release in before 21.05. I would love for some interested parties to join in on a call some time this week (maybe thursday/friday?) to go through remaining blockers and maybe do some review
<adisbladis> cc aminechikhaoui, (and of course tewfik), gchristensen, cole-h, aanderse
<adisbladis> This is an open invitation to everyone
<DigitalKiwi> some are more invited than others
<adisbladis> :D
<adisbladis> I explicitly invited people who have been on previous review calls
<DigitalKiwi> it's ok :( i'll just go watch the stonks
<adisbladis> DigitalKiwi: You are also invited
<adisbladis> Don't do stonks
<adisbladis> Do NixOps
<adisbladis> It's more valuable
<cole-h> I could certainly attempt to make a Thursday call. If, for whatever reason, I can't, my proofreading services are free :) Ping me on any PRs and I'll get to them Soon™
<cole-h> (Though, FWIW, I don't use nixops anymore -- switched back to plain ole nixos-rebuild :P)
<DigitalKiwi> adisbladis: lol but the stonks are up!
<cole-h> (IIRC that's what most of my contributions were on the calls: comic relief and nitpicking wording to the moon and back)
cole-h has quit [Ping timeout: 240 seconds]
srk has quit [Remote host closed the connection]
srk has joined #nixops
<adisbladis> Also cc manveru
<manveru[m]> not sure how much help i'll be :)
<adisbladis> I was just looking at https://github.com/NixOS/nixops/pull/1319
<{^_^}> nixops#1319 (by manveru, 40 weeks ago, open): add nixops eval subcommand
<adisbladis> That's why I CCed you
<manveru[m]> ah ok
<manveru[m]> haven't used nixops in a long time myself ^^; but we still use it a lot at our company
<adisbladis> I'm not sure about the entire use case for this?
<adisbladis> Also I'd like to switch NixOps to use the Hydra evaluator, which may change the implementation entirely
<manveru[m]> the use-case was mostly to simplify scripts that need info from the cluster
<manveru[m]> unfortunately the only project we use nixops eval in isn't public... so can't give you much more info :|
<manveru[m]> but i wouldn't be upset if you don't merge it either
<adisbladis> Ok, that's good. Then at least I won't let that be a blocker for 2.0
<adisbladis> We can always introduce something similar in a point release
<manveru[m]> yeah :)
<srk> adisbladis: would you point me in the right direction regarding networking.extraHosts (&virtd)? - https://github.com/nix-community/nixops-libvirtd/issues/21#issuecomment-768982055
meh` has joined #nixops
<adisbladis> Hm, I wonder if there is any point to keeping nixopsUnstable around
<adisbladis> Or rather, instead of assigning 2.0 to nixops2Unstable, we would make it nixopsUnstable
<adisbladis> I think I'm going with nixopsUnstable as going with nixops2Unstable would eventually make that attribute stale
<DigitalKiwi> it's nixops 1.8 anyway
<adisbladis> It says unstable right there on the tin anyway
<adisbladis> cc gchristensen
<gchristensen> not sure
<gchristensen> maybe not, people can jump to a new unstable ni the future if they need to
<adisbladis> gchristensen: Let's reframe it then, is the current unstable attribute useful over the not unstable one?
<adisbladis> If it is, I'm fine with keeping it
<adisbladis> If not, let's remove it
<adisbladis> I'm not convinced by the current unstable attr pointing to an old hydra tarball
<adisbladis> gchristensen: They're actually pointing to the same commit
<adisbladis> So the current nixopsUnstable has no value
<gchristensen> agreed
<adisbladis> :)
<adisbladis> https://github.com/NixOS/nixpkgs/pull/83548 anyone wants to take a quick final check?
<{^_^}> #83548 (by adisbladis, 44 weeks ago, open): nixopsUnstable: 1.7pre2764_932bf4 -> 2.0.0-pre
<adisbladis> DigitalKiwi: You maybe?
<DigitalKiwi> what am i checking
<DigitalKiwi> This branch is 2 commits ahead, 32974 commits behind NixOS:master. :(
<adisbladis> DigitalKiwi: I've just rebased it and touched it up today
<adisbladis> DigitalKiwi: I just want someone who isn't me to take a look before I push the big green button
<adisbladis> In case I screwed up something I'm blind to
<aminechikhaoui> adisbladis re having a call: that sounds good, if you have a specific time in mind let us know and I'll check with Tewfik as well if he's available
<adisbladis> aminechikhaoui: Some time on friday. I'll check my schedule.
<adisbladis> Friday 16:00 CET ?
<aminechikhaoui> adisbladis that's 10am EDT right ? sounds good to me, let me quickly check with Tewfik as well
<aminechikhaoui> yeah Tewfik is also available
<adisbladis> aminechikhaoui: Yes, correct
<adisbladis> Great
<adisbladis> Let's set that time
<aminechikhaoui> thank you
<adisbladis> NixOps related talk | logs: https://logs.nix.samueldr.com/nixops/ https://meet.jit.si/NixOpsReview | NixOps 2.0 planning call 2021-03-05 15:00 UTC
<adisbladis> Ugh.. :P
<adisbladis> gchristensen: Could you set "NixOps related talk | logs: https://logs.nix.samueldr.com/nixops/ https://meet.jit.si/NixOpsReview | NixOps 2.0 planning call 2021-03-05 15:00 UTC" as topic?
<adisbladis> I don't have the permissions to do so
adisbladis changed the topic of #nixops to: NixOps related talk | logs: https://logs.nix.samueldr.com/nixops/ https://meet.jit.si/NixOpsReview | NixOps 2.0 planning call 2021-03-05 15:00 UTC
<adisbladis> Thanks <3
<johnny101> I'd like to join the call also.
<adisbladis> johnny101: You're more than welcome :)
<johnny101> Awesome, thanks!
<adisbladis> It's the jitsi link in the topic
<johnny101> adisbladis: you meant to have the call this Friday? The info in the header says March 5th.
adisbladis changed the topic of #nixops to: NixOps related talk | logs: https://logs.nix.samueldr.com/nixops/ https://meet.jit.si/NixOpsReview | NixOps 2.0 planning call 2021-02-05 15:00 UTC
<adisbladis> I don't know what you're talking about! ;)
<johnny101> haha... :)
meh` has quit [Ping timeout: 240 seconds]
cole-h has joined #nixops
<cole-h> adisbladis: I won't be able to make it Friday (likely sleeping in before work), but feel free to ping me on anything you'd like an extra set of eyes on.
spudly1 has quit [Read error: Connection reset by peer]
spudly- has joined #nixops
spudly- has quit [Changing host]
spudly- has joined #nixops
spudly1 has joined #nixops
spudly- is now known as spudly