summaryrefslogtreecommitdiffstats
path: root/nixos/release.nix
diff options
context:
space:
mode:
authorGraham Christensen <graham@grahamc.com>2021-08-25 09:38:46 -0400
committerGraham Christensen <graham@grahamc.com>2021-08-25 10:42:35 -0400
commitbd38b059eae05871579b2dfd51cd41d058b6a1ec (patch)
treeec8236c3aa59535ed61e0856960b48c177d0a0ca /nixos/release.nix
parent076f6e2d948259e18ddac8e562c62b5b53de9fe6 (diff)
NixOS/amazonImageZfs: init
Introduce an AWS EC2 AMI which supports aarch64 and x86_64 with a ZFS root. This uses `make-zfs-image` which implies two EBS volumes are needed inside EC2, one for boot, one for root. It should not matter which is identified `xvda` and which is `xvdb`, though I have always uploaded `boot` as `xvda`.
Diffstat (limited to 'nixos/release.nix')
-rw-r--r--nixos/release.nix14
1 files changed, 14 insertions, 0 deletions
diff --git a/nixos/release.nix b/nixos/release.nix
index 2367e79e4ad0..264d82bacc8a 100644
--- a/nixos/release.nix
+++ b/nixos/release.nix
@@ -217,6 +217,20 @@ in rec {
}).config.system.build.amazonImage)
);
+ amazonImageZfs = forMatchingSystems [ "x86_64-linux" "aarch64-linux" ] (system:
+
+ with import ./.. { inherit system; };
+
+ hydraJob ((import lib/eval-config.nix {
+ inherit system;
+ modules =
+ [ configuration
+ versionModule
+ ./maintainers/scripts/ec2/amazon-image-zfs.nix
+ ];
+ }).config.system.build.amazonImage)
+
+ );
# Test job for https://github.com/NixOS/nixpkgs/issues/121354 to test