| 28 Feb 2025 |
drewhaven | Exactly. The goal is to make the system so simple that the vast majority of issues can be fixed with a reboot or rollback. | 01:02:19 |
drewhaven | Now to keep designing the rest of the system and make sure everyone's onboard with NixOS. Not everyone's as comfortable with Nix as I am, but it's a huge step up from the years-out-of-date Fedora they were using where every system could be a bit different. | 01:03:31 |
commiterate | If you're using Cfn to manage your immutable infra setup, ASG instance refresh in Cfn stack updates is planned for this year and I'm chasing them to allow Cfn-managed S3 -> EBS snapshot imports. Latter is still waiting for a meeting with a PM though. | 01:05:43 |
commiterate | Once both of those are in place, AWS CDK-based apps should be able to build a raw NixOS disk image wtih Nix, mark it as a CDK asset, and reference it in the AMI import resource. | 01:06:37 |
commiterate | * If you're using Cfn to manage your immutable infra setup, ASG instance refresh in Cfn stack updates is planned for this year and I'm chasing them to allow Cfn-managed S3 -> EBS snapshot imports. Latter is still waiting for a meeting with a PM though.
- https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/2119
- https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/2175
| 01:07:42 |
commiterate | * Once both of those are in place, AWS CDK-based apps should be able to build a raw NixOS disk image with Nix, mark it as a CDK asset, and reference it in the AMI import resource. | 04:17:49 |
Arian | Wild that they dont have instance refresh | 07:28:33 |
Arian | In all fairness. Terraform's implementation is bugged. So we trigger instance refresh with the CLI too | 07:28:52 |
commiterate | I'm surprised Cfn support wasn't a launch requirement since that's basically required for most AWS services. | 17:11:39 |
commiterate | Though instance refresh is a bit different since it's an action rather than a resource. | 17:12:01 |
commiterate | Cfn-managed S3 to AMI import is another head scratcher. | 17:12:31 |
commiterate | It would make their own lives a lot easier for internal services and for AWS-managed AMIs (e.g. Amazon Linux, Windows). | 17:13:13 |
Arian | https://github.com/MercuryTechnologies/terraform-aws-ssm-nixos-deploy-document
https://github.com/MercuryTechnologies/aws-ssm-update-association-action
https://github.com/MercuryTechnologies/aws-ssm-send-command-action
| 19:57:26 |
Arian | just hit the open source button on these | 19:57:41 |
Arian | We have similar terraform module and github actions for instance-refresh. They’ll be open sourced at a later date | 19:58:15 |
| 6 Mar 2025 |
| Marcus joined the room. | 16:17:47 |
| 12 Mar 2025 |
| vidariondr joined the room. | 21:08:00 |
| shivaraj-bh joined the room. | 23:49:59 |
| 21 Mar 2025 |
Arian | I'm trying to build the Amazon linux 2023 kernel in Nixpkgs (for some firecracker testing) but it seems the tags that Amazon linux use don't belong to any branch. So fetchFromGtHub doesn't work | 11:05:27 |
Arian | E.g. https://github.com/amazonlinux/linux/tree/microvm-kernel-6.1.128-3.201.amzn2023 | 11:06:11 |
Arian | It says "doesn't belong to any branch or repo" | 11:06:19 |
Arian | Anybody got an idea why the repo is in such a weird state? | 11:06:38 |
adamcstephens | I think it’s because GitHub considers that repo a fork | 11:41:38 |
adamcstephens | Can you fetch that branch or commit with git directly? | 11:41:54 |
adamcstephens | * Can you fetch that tag or commit with git directly? | 11:42:11 |
Arian | Nope. I can't :/ | 15:12:46 |
Arian | Unable to checkout refs/tags/microvm-kernel-6.1.8..... | 15:13:09 |
Arian | Oh I made a typo | 15:13:34 |
Arian | Okay trying with fetchgit now. Just very slow | 15:14:36 |
Arian | Yep worked. Thanks | 15:15:22 |