From 09d9d71e2bf87439e3022dd6419e63d6556f8a1d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Torjus=20H=C3=A5kestad?= Date: Thu, 5 Feb 2026 02:04:58 +0100 Subject: [PATCH] docs: note to establish hostname naming conventions before migration Co-Authored-By: Claude Opus 4.5 --- docs/plans/host-migration-to-opentofu.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/plans/host-migration-to-opentofu.md b/docs/plans/host-migration-to-opentofu.md index 14c66a6..4a54292 100644 --- a/docs/plans/host-migration-to-opentofu.md +++ b/docs/plans/host-migration-to-opentofu.md @@ -188,3 +188,8 @@ the same cleanup steps as the jump host. the new one is provisioned (or use a temporary IP and swap after verification) - Stateful migrations should be done during low-usage windows - After all migrations are complete, the only hosts not in OpenTofu will be ca (deferred) +- Since many hosts are being recreated, this is a good opportunity to establish consistent + hostname naming conventions before provisioning the new VMs. Current naming is inconsistent + (e.g. `ns1` vs `nix-cache01`, `ha1` vs `auth01`, `pgdb1` vs `http-proxy`). Decide on a + convention before starting migrations — e.g. whether to always use numeric suffixes, a + consistent format like `service-NN`, role-based vs function-based names, etc.