iPSK Manager High Availability
1. Overview
High availability configuration for iPSK Manager portal to ensure guest and IoT device self-service registration remains available during maintenance or failures.
2. Architecture
2.1. Current Deployment
| Component | Primary | Secondary |
|---|---|---|
Hostname |
ipsk-manager.inside.domusdigitalis.dev |
ipsk-mgr-02.inside.domusdigitalis.dev |
IP Address |
10.50.1.30 |
10.50.1.31 |
Role |
Active |
Standby |
VLAN |
100 |
100 |
2.2. Target Architecture
User/Device
│
▼
┌─────────────┐
│ pfSense VIP │ ← Virtual IP for HAProxy
│ 10.50.1.32 │
└──────┬──────┘
│
├─────────────────┐
▼ ▼
┌─────────────┐ ┌─────────────┐
│ iPSK-Mgr-01 │ │ iPSK-Mgr-02 │
│ (Primary) │ │ (Secondary) │
└──────┬──────┘ └──────┬──────┘
│ │
└────────┬────────┘
│
┌────────▼────────┐
│ PostgreSQL DB │
│ (Primary) │
│ + Replication │
└─────────────────┘3. Implementation Phases
3.1. Phase 1: Database Replication
-
Configure PostgreSQL streaming replication
-
Set up automatic failover with Patroni
-
Test replication lag and consistency
-
Document recovery procedures
3.2. Phase 2: Application Layer HA
-
Deploy iPSK Manager on secondary node
-
Configure shared session storage (Redis)
-
Synchronize PSK policies between nodes
-
Test application failover