gchristensen changed the topic of #nixops to: NixOps related talk | logs: https://logs.nix.samueldr.com/nixops/ https://meet.jit.si/NixOpsReview
<DigitalKiwi> ixxie: hi sorry i've been busy day in and day out with this pool/retaining wall/deck
<DigitalKiwi> ixxie: maybe close to being done though...at least until the deck boards come in someday...since they were supposed to be dropped off like 2 months ago :|
cptMikky has quit [Ping timeout: 246 seconds]
b42 has quit [Ping timeout: 260 seconds]
b42 has joined #nixops
cptMikky has joined #nixops
kalbasit has joined #nixops
kalbasit has quit [Read error: Connection reset by peer]
kalbasit has joined #nixops
kalbasit has quit [Ping timeout: 258 seconds]
raghavsood has joined #nixops
<raghavsood> Is nixops able to build the initial installer with a remote builder? I'm getting https://gist.github.com/RaghavSood/510348431c05a52a62e3e94347535043 only when deploying new machines. Updating existing ones works fine
<raghavsood> Disabling the remote builder made the deployment go through
cole-h has quit [Quit: Goodbye]
<ixxie> DigitalKiwi: no worries :)
<ixxie> DigitalKiwi: just keeping you updated
mananamenos has joined #nixops
<ixxie> adisbladis: you here?
meh` has joined #nixops
meh` has quit [Ping timeout: 256 seconds]
raghavsood has quit [Remote host closed the connection]
<ixxie> gchristensen: hate to bug again, but do you have a moment?
<gchristensen> barely a moment, what's up?
<ixxie> well, not sure if this is the kind of thing that can be solved quickly
<ixxie> this is weird because adisbladis got this working before, and I can't reproduce that
<gchristensen> yeah, definitely would be hard, can you ping adisbladis?
<ixxie> I've tried, I'll wait it out maybe he comes online later
<ixxie> have a good day dude
<gchristensen> thanks, man, I'm feeling like I need maybe an extra couple weekends (:| zzz)
<ixxie> oh man
<ixxie> vacation time gchristensen!
<ixxie> I can imagine with all the work and the FOSS you get burned out
<ixxie> heroes need R&R too!
<adisbladis> ixxie: Re the `network` attribute error you can set a `network.description = "something";`
<adisbladis> In my test deployment I did set a network attribute
<ixxie> adisbladis: right, that resolved it
<ixxie> adisbladis: is it normal that deployment's _must_ specify a network?
<adisbladis> Yes
<adisbladis> But as none of the network params are required maybe we should fix that
n3t has quit [*.net *.split]
infinisil has quit [*.net *.split]
infinisil has joined #nixops
n3t has joined #nixops
<ixxie> adisbladis: its working now!
<ixxie> adisbladis: I'm still curious why its not picking ip the authToken attribute (I had to set the env var)
<adisbladis> ixxie: Do tell if you need some help debugging
<ixxie> adisbladis: well, it seems to work now
<adisbladis> Even authToken ?
<ixxie> adisbladis: no, not that
<ixxie> there is an anomoly though
<ixxie> some weird error, about activation, even though the machine is created just fine
<ixxie> I'm running the deploy a second time to check if this is reproducible
<ixxie> regarding the authToken, I am not sure what's going on
<adisbladis> I'm not sure that last error you're seeing is strictly nixops related
<adisbladis> It's pretty hard to tell what went wrong
<ixxie> alright
<ixxie> so what's up with this authToken thing 🤔
<ixxie> ( adisbladis - I reproduced that error )
<ixxie> maybe I should make an issue for this on the nixops repo?
<adisbladis> Is it really a NixOps issue?
<adisbladis> I doubt it
<adisbladis> I'm not saying 100% that it's not, but my gut feeling is that it's in the DO plugin
<adisbladis> Let me just finish what I'm doing first, then I'll take a look :)
<ixxie> oh I misread your earlier comment :D
<ixxie> okay, lets have a look when you are read :)
meh` has joined #nixops
<ixxie> DigitalKiwi: are you around?
meh` has quit [Ping timeout: 264 seconds]
<adisbladis> ixxie: This is taking longer than expected, so I might as well take some time to help you out
<ixxie> adisbladis: cheers!
<ixxie> adisbladis: yeah I'm not sure what's happening... the other attributes work just fine.
<ixxie> adisbladis: in case you didn't spot it, this is the latest: https://github.com/Kiwi/nixops-digitalocean/pull/2
<{^_^}> Kiwi/nixops-digitalocean#2 (by ixxie, 23 hours ago, open): NixOps 2.0 Upgrade
<ixxie> adisbladis: although its pretty much exactly your branch, with the earlier work divided into proper commits
<adisbladis> I'm taking a look right now :)
<ixxie> cool :)
<adisbladis> I think I know what it is already, lets confirm :)
<adisbladis> Yep, that's it
<adisbladis> I don't know why mypy didn't catch this...
<ixxie> what was it?
<ixxie> speaking of mypy, there were also some errors it flagged which I couldn't figure out, I guess you already spotted them
<adisbladis> Well, of course it's not gonna be caught by mypy, what am I thinking
<adisbladis> The second one doesn't fix anything, it just aids mypy a bit
<ixxie> adisbladis: aha! I *thought* that was weird, but it was like this before so I left it
<adisbladis> There is one more thing we need to fix though
<ixxie> adisbladis: the last errors from mypy?
<adisbladis> No, those are unknown generics
<ixxie> hmm which unknown generics?
<adisbladis> You can just pull my entire nixops-2.0-upgrade
<ixxie> what is set_common_state?
<ixxie> yep, got it!
<ixxie> thanks adisbladis
<ixxie> so I can just ignore the last mypy errorS?
<adisbladis> I'm gonna take a stab at fixing those last mypy errors
<DigitalKiwi> ixxie I sent you a text
cole-h has joined #nixops
<DigitalKiwi> I have a few minutes but on my phone
<ixxie> DigitalKiwi: adisbladis is helping me now, and it looks like we are just about done!
<ixxie> DigitalKiwi: the volume stuff doesn't work though, and I think I will make a seperate branch without it for a PR
<ixxie> DigitalKiwi: that way we can merge the working 2.0 release and keep working on volumes later
<DigitalKiwi> That's fine there wasn't much to it iirc anyway I/someone can add it back later
<ixxie> yep
<ixxie> Its not working and I don't wanna block a release
<ixxie> DigitalKiwi: you should have a PR today
<DigitalKiwi> I'd like a fuller implementation with more testing of it too since right now it only creates and deletes and I am not sure how reliable deleting was. It had a problem at some point I think I fixed
<ixxie> DigitalKiwi: btw, there was a request from a few of us to move this repo to the nix-community org, if that's okay with you
<ixxie> DigitalKiwi: adisbladis can help with that
<DigitalKiwi> That would make it more visible at least since it used to be part of nixops anyway...
<DigitalKiwi> Do I still get commit bit :(
<ixxie> DigitalKiwi: we would get the same rights, I am sure
<ixxie> DigitalKiwi: I imagine its organized using teams etc.
<adisbladis> ixxie: Done :)
<adisbladis> I pushed it to the same branch
<DigitalKiwi> Then yeah I would like that I was going to ask Graham to about it at some point
<adisbladis> I could help you out with moving right now if you'd like
<adisbladis> Of course you retain the same privileges as you have now :)
<DigitalKiwi> 👍
<ixxie> adisbladis: 🎉🎉🎉
<ixxie> thanks!
<ixxie> adisbladis: I'd love to know how you figure this stuff out
<ixxie> its a total mystery to me
<adisbladis> ixxie: Blood, sweat, tears and no small amount of experience
<cole-h> Years of experience :P
<ixxie> heh
<ixxie> 'he sensed a disturbance in the stack'
<adisbladis> It's type errors all the way down
<ixxie> is a resources directory required for a plugin?
<adisbladis> No
<adisbladis> Why are you asking?
<adisbladis> We don't enforce any specific plugin structure
<adisbladis> But you're really free to structure your plugin however you see fit
<ixxie> right
<ixxie> just wondering because I am now removing the unfinished volume features from this branch but suddenly the plugin isn't listed under `nixops list-plugins`
kalbasit has joined #nixops
ixxie has quit [Quit: Lost terminal]
meh` has joined #nixops
meh` has quit [Ping timeout: 272 seconds]
tokudan has quit [Remote host closed the connection]
tokudan has joined #nixops
ixxie has joined #nixops
<ixxie> DigitalKiwi: ping?
<DigitalKiwi> hi
<{^_^}> Kiwi/nixops-digitalocean#2 (by ixxie, 1 day ago, open): NixOps 2.0 Upgrade
<ixxie> adisbladis, gchristensen - it seems we are in good shape now, there is only one anomaly I can't figure out yet, documented here https://gist.github.com/ixxie/36c3830e931bcf8e03f86f893f79bf99#anomaly-in-the-deployment
<ixxie> I'm not sure whether or not this warrants an issue in the NixOps repo or whether this is an issue with the plugin
<adisbladis> I'm not even sure it's a bug in either
<ixxie> yeah I was wondering if I have something misconfigured
<ixxie> adisbladis: what is max_concurrent_activate?
<cole-h> I'd guess the maximum number of resources that can be activated... concurrently.
<DigitalKiwi> but what is the value
<adisbladis> What cole-h said
<DigitalKiwi> 8? 16? $cpus?
<DigitalKiwi> 1 million
<DigitalKiwi> activate all the things
<adisbladis> The default is -1 (for unlimited)
<cole-h> ^
<cole-h> (too fast)
<DigitalKiwi> ALL THE THINGS
<ixxie> adisbladis: but I didn't change the default
<adisbladis> ixxie: I think you're looking in the wrong place
<ixxie> trying to figure out where this is actually used
<ixxie> and in script_defs
<ixxie> adisbladis: so probably I am looking in the wrong place yes :D
<adisbladis> I mean I don't think it's a very interesting thing to look at, it's extremely unlikely that it's gonna help you find out what's wrong
<ixxie> I guess the key think for me to understand at this point is, is this an issue with the plugin or not?
<ixxie> Because we need to decided if the PR is ready or not
<adisbladis> I think it's not
<ixxie> Otherwise, it seems everything works, I'm just annoyed I don't understand this and I wonder whether I need to actually do something about this
<ixxie> DigitalKiwi: so, you can check the PR and merge if you deem fit
<DigitalKiwi> lgtm
* DigitalKiwi hasn't looked at it
<DigitalKiwi> we don't have users yet right? >.>
<ixxie> hah
<ixxie> yeah I guess not
<ixxie> DigitalKiwi: once merged we should tag 1.0.0
<ixxie> DigitalKiwi: maybe its good you look at it, even if only a glance, just so you know what is happening?
<DigitalKiwi> i might not be working on the pool tomorrow and it's not even 19:00 here yet so i'll try and look at stuff
<ixxie> cool
<ixxie> and then you can also potentially move it to nix-community today or tomorrow
<cole-h> 1.0.0 or 0.1.0? :^)
<ixxie> cole-h: well, hard choices right :D
<cole-h> The hardest choices require the strongest of wills.
<ixxie> DigitalKiwi: aaah lol didn't even notice
<DigitalKiwi> if i can't write haskell i'll at least version like it right?
<ixxie> cole-h: I recon 1.0.0 because its been already for a while available but unversioned, so intuitively that was the v0 era :D
<cole-h> But are you satisfied with its functionality? Is it fully-featured?
<ixxie> cole-h: it can deploy NixOS VMs, that is a reasonable MVP in my book
<cole-h> MVP != 1.0 IMO
<ixxie> cole-h: and we will follow semantic versioning
<DigitalKiwi> it used to be in nixops
<cole-h> But it's your project :)
<ixxie> DigitalKiwi: what do you think? 0.1.0?
<ixxie> I don't care much
<ixxie> I guess its a better reflection of the current status quo
<DigitalKiwi> that's the last project i had with a significant amount of users ;)
<cole-h> >2011
<cole-h> Noice
<DigitalKiwi> ok the last foss project >.>
<DigitalKiwi> i had mobile apps/web apps/websites with a lot more users
<DigitalKiwi> but for $WORK
<ixxie> DigitalKiwi: oh I forgot still to rename droplet to doDroplet
<DigitalKiwi> afaik the only serious problem anyone ever had was they removed pacman...which removed libalpm
<DigitalKiwi> which, while technically clyde didn't rely on pacman, and pacman and libalpm *could* have been split off, they were not...
<ixxie> DigitalKiwi: I guess we can do it later
<DigitalKiwi> and even that the fix i think is to just use bsdtar to extract a pacman.pkg.xz or w/e it is
<DigitalKiwi> i haven't even showered yet so i'm not really ready to *think*
* DigitalKiwi tracks down food