Files
proxmox/docs/03-deployment/DEPLOYMENT_STATUS_CONSOLIDATED.md
defiQUG fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
docs: Ledger Live integration, contract deploy learnings, NEXT_STEPS updates
- 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>
2026-02-12 15:46:57 -08:00

261 lines
7.5 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Deployment Status - Consolidated
**Last Updated:** 2025-01-20
**Document Version:** 2.0
**Status:** Active Deployment (legacy consolidated view)
**For current container inventory by host (SSH-reconciled), use [DEPLOYMENT_STATUS_MASTER.md](DEPLOYMENT_STATUS_MASTER.md).** This document is the legacy consolidated table; refer to MASTER for inventory updates (e.g. 25062508 destroyed, VMID allocation).
---
## Overview
This document consolidates deployment status into a single table view. For authoritative per-host inventory and recent changes, see DEPLOYMENT_STATUS_MASTER.md.
---
## Current Deployment Status
### Proxmox Host: ml110 (192.168.11.10)
**Status:** ✅ Operational
### Active Containers
| VMID | Hostname | Status | IP Address | VLAN | Service Status | Notes |
|------|----------|--------|------------|------|----------------|-------|
| 1000 | besu-validator-1 | ✅ Running | 192.168.11.100 | 11 (mgmt) | ✅ Active | Static IP |
| 1001 | besu-validator-2 | ✅ Running | 192.168.11.101 | 11 (mgmt) | ✅ Active | Static IP |
| 1002 | besu-validator-3 | ✅ Running | 192.168.11.102 | 11 (mgmt) | ✅ Active | Static IP |
| 1003 | besu-validator-4 | ✅ Running | 192.168.11.103 | 11 (mgmt) | ✅ Active | Static IP |
| 1004 | besu-validator-5 | ✅ Running | 192.168.11.104 | 11 (mgmt) | ✅ Active | Static IP |
| 1500 | besu-sentry-1 | ✅ Running | 192.168.11.150 | 11 (mgmt) | ✅ Active | Static IP |
| 1501 | besu-sentry-2 | ✅ Running | 192.168.11.151 | 11 (mgmt) | ✅ Active | Static IP |
| 1502 | besu-sentry-3 | ✅ Running | 192.168.11.152 | 11 (mgmt) | ✅ Active | Static IP |
| 1503 | besu-sentry-4 | ✅ Running | 192.168.11.153 | 11 (mgmt) | ✅ Active | Static IP |
| 2500 | besu-rpc-1 | ✅ Running | 192.168.11.250 | 11 (mgmt) | ✅ Active | Static IP |
| 2501 | besu-rpc-2 | ✅ Running | 192.168.11.251 | 11 (mgmt) | ✅ Active | Static IP |
| 2502 | besu-rpc-3 | ✅ Running | 192.168.11.252 | 11 (mgmt) | ✅ Active | Static IP |
**Total Active Containers:** 12
**Total Memory:** 104GB
**Total CPU Cores:** 40 cores
### Network Status
**Current Network:** Flat LAN (192.168.11.0/24)
**VLAN Migration:** ⏳ Pending
**Target Network:** VLAN-based (see [NETWORK_ARCHITECTURE.md](../02-architecture/NETWORK_ARCHITECTURE.md))
### Service Status
**Besu Services:**
- ✅ 5 Validators: Active
- ✅ 4 Sentries: Active
- ✅ 3 RPC Nodes: Active
**Consensus:**
- ✅ QBFT consensus operational
- ✅ Block production: Normal
- ✅ Validator participation: 5/5
---
## Deployment Phases
### Phase 0 — Foundation ✅
- [x] UDM Pro (replaced ER605); Spectrum Business Internet
- [x] Proxmox mgmt accessible (ml110, r630-01, r630-02)
- [x] Basic containers deployed
- [x] ER605, ES216G removed; UDM Pro only
### Phase 1 — VLAN Enablement ⏳
- [ ] UDM Pro VLAN configuration (ES216G/ER605 removed)
- [ ] VLAN-aware bridge enabled on Proxmox (if using VLANs)
- [ ] Services migrated to VLANs (optional)
### Phase 2 — Observability ⏳
- [ ] Monitoring stack deployed
- [ ] Grafana published via Cloudflare Access
- [ ] Alerts configured
### Phase 3 — CCIP Fleet ⏳
- [ ] CCIP Ops/Admin deployed
- [ ] 16 commit nodes deployed
- [ ] 16 execute nodes deployed
- [ ] 7 RMN nodes deployed
- [ ] NAT pools configured
### Phase 4 — Sovereign Tenants ⏳
- [ ] Sovereign VLANs configured
- [ ] Tenant isolation enforced
- [ ] Access control configured
---
## Resource Usage
### Current Resources (ml110)
| Resource | Allocated | Available | Usage % |
|----------|-----------|-----------|---------|
| Memory | 104GB | [TBD] | [TBD] |
| CPU Cores | 40 | [TBD] | [TBD] |
| Disk | ~1.2TB | [TBD] | [TBD] |
### Planned Resources (R630 Cluster)
| Node | Memory | CPU | Disk | Status |
|------|--------|-----|------|--------|
| r630-01 | 512GB | [TBD] | 2×600GB + 6×250GB | ⏳ Pending |
| r630-02 | 512GB | [TBD] | 2×600GB + 6×250GB | ⏳ Pending |
| r630-03 | 512GB | [TBD] | 2×600GB + 6×250GB | ⏳ Pending |
| r630-04 | 512GB | [TBD] | 2×600GB + 6×250GB | ⏳ Pending |
---
## Network Architecture
### Current (Flat LAN)
- **Network:** 192.168.11.0/24
- **Gateway:** 192.168.11.1
- **All services:** On same network
### Target (VLAN-based)
See **[NETWORK_ARCHITECTURE.md](../02-architecture/NETWORK_ARCHITECTURE.md)** for complete VLAN plan.
**Key VLANs:**
- VLAN 11: MGMT-LAN (192.168.11.0/24) - Legacy compatibility
- VLAN 110: BESU-VAL (10.110.0.0/24) - Validators
- VLAN 111: BESU-SEN (10.111.0.0/24) - Sentries
- VLAN 112: BESU-RPC (10.112.0.0/24) - RPC nodes
- VLAN 132: CCIP-COMMIT (10.132.0.0/24) - CCIP Commit nodes
- VLAN 133: CCIP-EXEC (10.133.0.0/24) - CCIP Execute nodes
- VLAN 134: CCIP-RMN (10.134.0.0/24) - CCIP RMN nodes
---
## Public IP Blocks
### Block #1 (Configured)
- **Network:** 76.53.10.32/28
- **Gateway:** 76.53.10.33
- **ER605 WAN1:** 76.53.10.34
- **Usage:** Router WAN + break-glass VIPs
### Blocks #2-6 (Pending)
- **Block #2:** CCIP Commit egress NAT pool
- **Block #3:** CCIP Execute egress NAT pool
- **Block #4:** RMN egress NAT pool
- **Block #5:** Sankofa/Phoenix/PanTel service egress
- **Block #6:** Sovereign Cloud Band tenant egress
See **[NETWORK_ARCHITECTURE.md](../02-architecture/NETWORK_ARCHITECTURE.md)** for details.
---
## Known Issues
### Resolved ✅
- ✅ VMID 1000 IP configuration fixed (now 192.168.11.100)
- ✅ Besu services active (11/12 services running)
- ✅ Validator key issues resolved
### Pending ⏳
- ⏳ VLAN migration not started
- ⏳ CCIP fleet not deployed
- ⏳ Monitoring stack not deployed
- ⏳ Cloudflare Zero Trust not configured
---
## Next Steps
### Immediate (This Week)
1. **Complete VLAN Planning**
- Finalize VLAN configuration
- Plan migration sequence
- Prepare migration scripts
2. **Deploy Monitoring Stack**
- Prometheus
- Grafana
- Loki
- Alertmanager
3. **Configure Cloudflare Zero Trust**
- Set up cloudflared tunnels
- Publish applications
- Configure access policies
### Short-term (This Month)
1. **VLAN Migration**
- Configure ES216G switches
- Enable VLAN-aware bridge
- Migrate services
2. **CCIP Fleet Deployment**
- Deploy Ops/Admin nodes
- Deploy Commit nodes
- Deploy Execute nodes
- Deploy RMN nodes
3. **NAT Pool Configuration**
- Configure Block #2-6 (when assigned)
- Set up role-based egress NAT
- Test allowlisting
### Long-term (This Quarter)
1. **Sovereign Tenant Rollout**
- Configure tenant VLANs
- Deploy tenant services
- Enforce isolation
2. **High Availability**
- Deploy R630 cluster
- Configure HA for critical services
- Test failover
---
## References
### Architecture
- **[NETWORK_ARCHITECTURE.md](../02-architecture/NETWORK_ARCHITECTURE.md)** - Complete network architecture
- **[ORCHESTRATION_DEPLOYMENT_GUIDE.md](../02-architecture/ORCHESTRATION_DEPLOYMENT_GUIDE.md)** - Deployment guide
- **[VMID_ALLOCATION_FINAL.md](../02-architecture/VMID_ALLOCATION_FINAL.md)** - VMID allocation
### Deployment
- **[VALIDATED_SET_DEPLOYMENT_GUIDE.md](VALIDATED_SET_DEPLOYMENT_GUIDE.md)** - Validated set deployment
- **[CCIP_DEPLOYMENT_SPEC.md](../07-ccip/CCIP_DEPLOYMENT_SPEC.md)** - CCIP deployment
- **[DEPLOYMENT_READINESS.md](DEPLOYMENT_READINESS.md)** - Deployment readiness
### Operations
- **[OPERATIONAL_RUNBOOKS.md](OPERATIONAL_RUNBOOKS.md)** - Operational runbooks
- **[TROUBLESHOOTING_FAQ.md](../09-troubleshooting/TROUBLESHOOTING_FAQ.md)** - Troubleshooting guide
---
**Document Status:** Active
**Maintained By:** Infrastructure Team
**Review Cycle:** Weekly
**Last Updated:** 2025-01-20