<ris>
hmmmmm it's worse than that - even if i include the patch to fix the digitalocean curl issue in nixpkgs-20.09's `nixops` or `nixopsUnstable`, the machine fails to come back up after the second reboot
<ris>
or we're otherwise unable to communicate with it
<madonius[m]>
o/
<madonius[m]>
does anyone know a way to split a cidr into usefull chunks?
teto has quit [Ping timeout: 265 seconds]
<madonius[m]>
a.b.c.d/24 to the address, prefix etc?
<madonius[m]>
nvm wrong channel ^^'
teto has joined #nixops
cole-h has quit [Ping timeout: 240 seconds]
genevino has quit [Remote host closed the connection]
genevino has joined #nixops
meh` has quit [Ping timeout: 240 seconds]
<ris>
so are we in a situation now where nobody cares enough about 1.7 to keep it working, but 2.0 isn't ready yet? because if i had been running production systems on this, right now i would be in a very bad place.
<gchristensen>
it may be that 2.0 is ready enough to go, it probably just needs people to be using it to say yes let's ship it. unfortunately I stopped having work time to work on nixops like I did before, and very little time outside of work to take it on :(
teto has quit [Ping timeout: 272 seconds]
teto has joined #nixops
cole-h has joined #nixops
<ris>
DigitalKiwi: i really can't get anywhere with the nixops2 from your links - there just doesn't seem to be any documentation, or even examples of what a working configuration is supposed to look like. i just end up with `NotImplementedError: get_type`
<DigitalKiwi>
the machine type of digital ocean probably changed heh
<DigitalKiwi>
it used to be digitalOcean right now I think it's droplet in master and it's doDroplet in the branch i use :|
<DigitalKiwi>
ris: i think if anyone was using nixops with digital ocean in production before they'd have had problems a long time before now... like not being able to have multiple machines
<ris>
yeah, i've tried droplet and doDroplet
<DigitalKiwi>
did you use the nixpkgs branch or one of the with plugins