beatzaplenty/nixos
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(ha): add dual VIP — retain 192.168.2.229 LAN alongside 192.168.5.229 storage
Check NixOS configurations / eval-hosts (push) Successful in 10m35s
Details

Browse Source 
Both VIPs fail over together in ha-group:
  vip-lan:     192.168.2.229/24 on ens18 (vmbr0) — LAN iSCSI + NFS access
  vip-storage: 192.168.5.229/24 on ens20 (vmbr2) — storage-client iSCSI + NFS

variables.nix: haServerLanVip = "192.168.2.229"
cluster-init.sh: both VIP primitives in ha-group XML; VIP_LAN var added
ip-addressing.md: both VIP entries documented

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
beatzaplenty
2026-07-29 16:18:45 +10:00
co-authored by Claude Sonnet 4.6
parent 8d43b7039c
commit 6f38ad67e0
3 changed files with 35 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
variables.nix
+2 -1
View File
@@ -119,7 +119,8 @@
haStoragePrefixLength = 29; # cluster subnet prefix length (/29)
haServer1ClientIp = "192.168.5.228"; # storage-client IP, node 1 (vmbr2 / ens20)
haServer2ClientIp = "192.168.5.227"; # storage-client IP, node 2 (vmbr2 / ens20)
haServerVip = "192.168.5.229"; # floating VIP on vmbr2 (Pacemaker IPaddr2)
haServerVip = "192.168.5.229"; # storage-client floating VIP on vmbr2 (Pacemaker IPaddr2 vip-storage)
haServerLanVip = "192.168.2.229"; # LAN floating VIP on vmbr0 (Pacemaker IPaddr2 vip-lan) — LAN iSCSI/NFS access
dockerStorageIp = "192.168.5.225"; # docker CT storage-client IP (vmbr2 / eth1)
serverStorageIp = "192.168.5.226"; # server VM storage-client IP (vmbr2 / ens19)
haClientCidr = "192.168.5.0/24"; # storage-client subnet — internal to pve1 only