fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
4.2 KiB
4.2 KiB
Sankofa Deployment Status Review
Date: 2026-01-20
Status: ⚠️ IN PROGRESS - Network Configuration Issue
✅ Completed Steps
1. Configuration Preparation
- ✅ Created
.env.r630-01from template - ✅ Verified Sankofa project exists at
/home/intlc/projects/Sankofa - ✅ Verified SSH access to r630-01 (192.168.11.11)
2. Container Deployment
- ✅ All 4 containers deployed successfully:
- VMID 7803: sankofa-postgres-1 (10.160.0.13) - PostgreSQL
- VMID 7802: sankofa-keycloak-1 (10.160.0.12) - Keycloak
- VMID 7800: sankofa-api-1 (10.160.0.10) - API
- VMID 7801: sankofa-portal-1 (10.160.0.11) - Portal
- ✅ All containers are running
- ✅ All containers have correct IP addresses assigned
- ✅ DNS configured on all containers (8.8.8.8, 1.1.1.1)
⚠️ Current Issues
Critical: Network Connectivity Problem
Problem: Containers cannot reach gateway 10.160.0.1
Symptoms:
- Containers have correct IP addresses (10.160.0.10-13)
- Containers have correct routing (default via 10.160.0.1)
- ❌ Cannot ping gateway 10.160.0.1
- ❌ Cannot reach internet (needed for package installation)
Root Cause:
- VLAN 160 interface not configured on Proxmox host (r630-01)
- Host has vmbr0 (192.168.11.11/24) but no VLAN 160 interface
- Gateway 10.160.0.1 may not exist or be unreachable
Network Configuration:
Host (r630-01):
- vmbr0: 192.168.11.11/24 (VLAN 11 - MGMT-LAN)
- vmbr0v200: 10.200.0.1/20 (VLAN 200)
- ❌ No VLAN 160 interface
Containers:
- 7800: 10.160.0.10/22 (API)
- 7801: 10.160.0.11/22 (Portal)
- 7802: 10.160.0.12/22 (Keycloak)
- 7803: 10.160.0.13/22 (PostgreSQL)
- Gateway: 10.160.0.1 (UNREACHABLE)
🔧 Required Fixes
1. Configure VLAN 160 on Proxmox Host
Option A: Create VLAN interface on vmbr0
# On r630-01
ip link add link vmbr0 name vmbr0.160 type vlan id 160
ip addr add 10.160.0.1/22 dev vmbr0.160
ip link set vmbr0.160 up
# Make persistent in /etc/network/interfaces
Option B: Verify router/gateway configuration
- Check if 10.160.0.1 exists on router (UDM Pro or ER605)
- Verify VLAN 160 is configured on router
- Verify inter-VLAN routing is enabled
2. Alternative: Use Host as Gateway
If VLAN 160 gateway doesn't exist, configure host routing:
# Enable IP forwarding
echo 1 > /proc/sys/net/ipv4/ip_forward
# Add route for 10.160.0.0/22
ip route add 10.160.0.0/22 dev vmbr0
# Configure NAT if needed
iptables -t nat -A POSTROUTING -s 10.160.0.0/22 -o vmbr0 -j MASQUERADE
📋 Pending Steps
Phase 3: Service Setup (Blocked by Network Issue)
- ⏸️ Setup PostgreSQL (requires internet access for packages)
- ⏸️ Setup Keycloak (requires internet access for packages)
- ⏸️ Deploy API service
- ⏸️ Deploy Portal service
Phase 4: Verification & Documentation
- ⏸️ Verify services are running
- ⏸️ Test health endpoints
- ⏸️ Update cutover plan with actual IPs/ports
- ⏸️ Test internal connectivity from NPMplus
Phase 5: Cutover
- ⏸️ Update NPMplus proxy hosts
- ⏸️ Verify SSL certificates
- ⏸️ Test end-to-end routing
- ⏸️ Update source-of-truth documentation
📊 Deployment Summary
| Component | Status | Notes |
|---|---|---|
| Containers Created | ✅ Complete | All 4 containers deployed |
| Network Configuration | ❌ Blocked | VLAN 160 not configured |
| PostgreSQL Setup | ⏸️ Pending | Requires network |
| Keycloak Setup | ⏸️ Pending | Requires network |
| API Deployment | ⏸️ Pending | Requires network |
| Portal Deployment | ⏸️ Pending | Requires network |
| Cutover Plan Update | ⏸️ Pending | Awaiting service deployment |
🎯 Next Actions
- IMMEDIATE: Configure VLAN 160 on Proxmox host or verify router configuration
- After Network Fix: Continue with PostgreSQL setup
- After Services Deployed: Update cutover plan documentation
- Final: Perform NPMplus cutover
📝 Notes
- Containers are using unprivileged mode
- Network configuration uses static IPs on VLAN 160
- Gateway 10.160.0.1 should be configured on router (UDM Pro or ER605)
- Inter-VLAN routing must be enabled for containers to reach internet
- No Cloudflare tunnels will be used (per user request)