Add VRRP failover infrastructure documentation (Nobara)
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
Deployed automatic failover for critical services (Traefik, Vaultwarden, Authentik, AdGuard) from Unraid to Nobara workstation via Keepalived VRRP with VIP 192.168.10.250. ~4 second failover time. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
12
CLAUDE.md
12
CLAUDE.md
@@ -7,6 +7,17 @@ When user says "connect unraid", use this command:
|
||||
ssh -i ~/.ssh/id_ed25519_unraid root@192.168.10.20 -p 422
|
||||
```
|
||||
|
||||
## Connect to Nobara (Failover Node)
|
||||
|
||||
```bash
|
||||
ssh nobara
|
||||
# or: ssh -i ~/.ssh/id_ed25519_nobara jazzymc@192.168.10.103
|
||||
# sudo password: (same as SSH login)
|
||||
```
|
||||
|
||||
Failover stack: `/home/failover/docker-compose.yml`
|
||||
Keepalived: `systemctl status keepalived`
|
||||
|
||||
## Connect to MikroTik HAP ax³
|
||||
|
||||
SSH port is **2222** (not 22):
|
||||
@@ -56,6 +67,7 @@ infrastructure/
|
||||
├── 07-WIFI-CAPSMAN-CONFIG.md # WiFi and CAPsMAN settings
|
||||
├── 08-DNS-ARCHITECTURE.md # DNS failover architecture
|
||||
├── 09-TAILSCALE-VPN.md # Tailscale VPN setup
|
||||
├── 10-FAILOVER-NOBARA.md # VRRP failover to Nobara
|
||||
├── CHANGELOG.md # Change history
|
||||
├── archive/ # Completed/legacy docs
|
||||
│ └── vlan-migration/ # VLAN migration project artifacts
|
||||
|
||||
Reference in New Issue
Block a user