Files
bootapi-templates/catalog/optiplex-3070.yaml
T
unkinben 06488b8d18
ci/woodpecker/push/pre-commit Pipeline was successful
ci/woodpecker/pr/pre-commit Pipeline was successful
ci/woodpecker/push/validate Pipeline was successful
ci/woodpecker/pr/validate Pipeline was successful
Add optiplex-3070 catalog entry
Six new prodnxsr0014-0019 Dell OptiPlex 3070 hosts were registered on the
legacy cobbler server (profile almalinux9-dell_3070) but the fleet had no
matching bootapi catalog entry, so they would fall to the generic almalinux9
autopart-on-sda path.

- Add catalog/optiplex-3070.yaml: auto-nvme, UEFI-aware, fixed ~31G LVM
- Document the entry in catalog/README.md shipped list and per-model table

Claude-Session: https://claude.ai/code/session_01JUoARVdmhxKQHyyyp1pxeT
2026-08-04 00:24:21 +10:00

24 lines
1.1 KiB
YAML

# Distro catalog entry: AlmaLinux 9 on the Dell OptiPlex 3070.
#
# Ported for the six prodnxsr0014-0019 bare-metal hosts registered on the legacy
# Cobbler server under profile almalinux9-dell_3070. Mirrors optiplex-3060: a
# %pre script auto-selects the internal NVMe (first under 512G), is UEFI-aware,
# sets bootloader --boot-drive, and uses a fixed ~31G LVM (no grow). The Cobbler
# almalinux9_dell3070 kickstart template currently fails to render on cobbler,
# so the closest working per-model profile (3060, same UEFI/auto-NVMe layout,
# fixed LVM) was used as the source of truth. Select it by setting the device's
# `provision_template` custom field to "optiplex-3070" (the device_type slug).
name: optiplex-3070
match:
platforms: [optiplex-3070]
kickstart: almalinux9
version_default: "9"
kernel_url: "{{.ArtifactBase}}/almalinux/{{.Version}}/BaseOS/{{.Arch}}/os/images/pxeboot/vmlinuz"
initrd_url: "{{.ArtifactBase}}/almalinux/{{.Version}}/BaseOS/{{.Arch}}/os/images/pxeboot/initrd.img"
kernel_args:
- inst.text
- net.ifnames=0
vars:
mirror: "{{.ArtifactBase}}/almalinux/{{.Version}}"
storage_mode: auto-nvme