33 lines
1.6 KiB
YAML
33 lines
1.6 KiB
YAML
---
|
|
# ============================================================================
|
|
# expand-root-lv role defaults
|
|
# ============================================================================
|
|
# Extends the root LVM logical volume to fill its volume group, then grows
|
|
# the underlying filesystem to match. Idempotent: when there's no free PE
|
|
# in the VG (i.e. the LV already fills the VG), the lvextend step is a
|
|
# no-op and resize2fs/xfs_growfs simply confirms the filesystem is at
|
|
# capacity.
|
|
#
|
|
# Designed for Ubuntu cloud-image-style installations where the autoinstall
|
|
# template provisions an LV at half the disk size (the Ubuntu Server
|
|
# installer's longstanding default). Run once after VM provisioning to
|
|
# reclaim the unallocated PE; safe to leave in a day1 playbook so future
|
|
# disk expansions are picked up automatically.
|
|
# ============================================================================
|
|
|
|
# The LV and VG names follow the Ubuntu Server installer's convention.
|
|
# Override per-host if your template differs.
|
|
expand_root_lv_vg_name: ubuntu-vg
|
|
expand_root_lv_lv_name: ubuntu-lv
|
|
|
|
# The partition that backs the physical volume. After a Proxmox disk grow,
|
|
# growpart must resize this partition before pvresize/lvextend can claim
|
|
# the new space. This is the full device path (e.g. /dev/sda3).
|
|
# If undefined, the growpart/pvresize steps are skipped.
|
|
expand_root_lv_pv_partition: /dev/sda3
|
|
|
|
# Mount point we expect to be backed by the target LV. Used purely for
|
|
# the resize2fs / xfs_growfs decision — the role inspects this path's
|
|
# filesystem type and dispatches to the correct grow command.
|
|
expand_root_lv_mountpoint: /
|