| 20 Oct 2024 |
 commiterate | likely a few substituteInPlace patches as well since there's some hardcoded binary paths in the udev rules | 07:37:16 |
 @sielicki:matrix.org | took me a sec to find context on this^ but massive kudos on the eic rewrite, that's completely and totally awesome | 07:37:47 |
| @sielicki:matrix.org | Arian: are you in NA timezones? please ping me tomorrow, let's talk about efa/ena kmods and/or the amazonlinux kernel | 07:40:56 |
| commiterate | I believe they're in Berlin | 07:41:38 |
| commiterate | * I believe they're in Berlin from their GitHub profile | 07:41:46 |
| @sielicki:matrix.org | ah, nice. I'll try in my morning, then. | 07:42:26 |
| @sielicki:matrix.org | you have any low-hanging fruit that I can help out on tomorrow while I have free time? | 07:49:58 |
 Arian | We already package amazon-ec2-utils udev rules afaik | 09:29:01 |
| commiterate | amazon-ec2-utils is packaged, amazon-ec2-net-utils isn't | 20:15:45 |
| commiterate | * amazon-ec2-utils is packaged, amazon-ec2-net-utils isn't | 20:18:24 |
| 21 Oct 2024 |
|  nh2 joined the room. | 04:00:51 |
| nh2 | Arian: Could you help me out with https://github.com/NixOS/nixpkgs/issues/307519 ? | 04:11:09 |
| Arian | There are no 23.05 AMIs | 07:11:37 |
| Arian | Oh i remember what happened here. | 07:12:01 |
| Arian | I think eu-west-2 was accidentally nuked by the infra team | 07:12:23 |
| Arian | * I think eu-west-1 was accidentally nuked by the infra team | 07:14:25 |
| Arian | But that ticket is super out of date. Since 24.05 everything should be available | 07:18:24 |
| Arian | https://github.com/NixOS/nixpkgs/issues/307519#issuecomment-2425821078 | 07:18:37 |
| Arian | How about we make networkd the new default networking backend for 24.11 as a first step to this? | 11:30:04 |
| Arian | I can send a PR for that | 11:30:16 |
| nh2 | In reply to @arianvp:matrix.org
I think eu-west-1 was accidentally nuked by the infra team I see. Note that the same is also the case for eu-central-1 now (when I think it wasn't before), just to make sure you know | 15:39:12 |
| Arian | As I said. That list is deprecated. Use https://nixos.github.io/amis instead | 16:26:20 |
| Arian | We can't use AWS for archival. They don't allow you to make public images available forever. They disappear after max period of a year | 16:26:45 |
| Arian | So use the docs linked to query the latest AMI. Anything else is unsupported | 16:27:01 |
| Arian | I also have no control over that old AWS account. I only have access to the new one. | 16:27:33 |
| Arian | * We can't use AWS for archival. They don't allow you to make public images available forever. They disappear after max period of a year | 16:27:41 |
| Arian | I only took over maintainace for 24.05 onwards. There aren't really any guarantees I can give over the old stuff. | 16:28:17 |
| Arian | Wouldn't be surprised all those images disappear at some point | 16:30:13 |
| Arian | Is there a particular reason why you need a 23.05 image instead of a supported image? | 16:33:08 |
| nh2 | Arian: I see.
Yes, my reason is that I need to migrate some older 23.05 NixOps deployments to newer NixOS.
For that to work well, I intended to start the old and new ones and compatibility-test them.
This does not work, because the AMIs are gone.
It betrays the entire point of fully declarative infrastructure-as-code that one cannot re-deploy the same thing at a later time.
Especially if it's only 1 year old.
I understand this isn't your or any NixOS contributor's fault, especially if AWS deletes public AMIs (no idea why they would do that, what is the point?).
You're referring to this, right?
https://aws.amazon.com/about-aws/whats-new/2022/03/amazon-machine-images-public-visibility-two-years/
But it also means that the way NixOps is written is completely unsuitable, and I'm not sure a lot of NixOps authors, contributors, or users are aware of this.
If public AMIs aren't a thing to last, NixOps should build an AMI itself an upload it.
(Probably people thought that they were a thing to last when that code was written.)
Indeed, no tool trying to provide reproducible deployments should be looking up AMIs from any list -- neither the old file amazon-ec2-amis.nix that you deleted, nor the new list at https://nixos.github.io/amis.
| 23:18:38 |
