Data disks and larger machines
A compute pool can now attach a data disk on AWS, Google Cloud, and Azure, not only on Machines. Give a range, and each deployment picks its own size, the same way it picks its machine type and count:
const compute = new alien.ComputeCluster("runtime")
.pool("general", {
requirements: {
cpu: 4,
memory: "16Gi",
dataDisk: { size: { min: "50Gi", default: "200Gi", max: "4Ti" } },
},
scale: { type: "autoscale", min: 1, max: 10 },
})
.build()A fixed size: "200Gi" still works. With a default of 0Gi, the pool has no
data disk unless the deployment picks one. The size is chosen in initial setup
and changed later in Change compute.
The machine catalog now comes from the AWS, Google Cloud, and Azure APIs and grows from 99 to 365 types, including current families such as c8i, m8i, and r8i up to 96xlarge with nested virtualization. The machine picker shows suggested machines first, then families, then each family's sizes, and only offers machines that can run the pool. Initial setup checks that the region offers the machine and that the quota covers it.
- Changing the disk size replaces every machine in the pool, and data on the old disks isn't kept. The dashboard warns before it does this
- Limits: 65,536 GiB on AWS and Google Cloud, 32,767 GiB on Azure. Kubernetes doesn't support data disks
- Automatic selection picks from the same machines as before, so no existing deployment changes machines