d-bis/proxmox
4
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
b45c2006be629f228d1ae98bc6372e83372653df
proxmox/docs/03-deployment/DEPLOYMENT_STATUS_CONSOLIDATED.md

6.9 KiB
Raw Blame History

Deployment Status - Consolidated

Last Updated: 2025-01-20
Document Version: 2.0
Status: Active Deployment

Overview

This document consolidates all deployment status information into a single authoritative source. It replaces multiple status documents with one comprehensive view.

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)

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 ✅

  • ER605-A WAN1 configured: 76.53.10.34/28
  • Proxmox mgmt accessible
  • Basic containers deployed

Phase 1 — VLAN Enablement ⏳

  • ES216G trunk ports configured
  • VLAN-aware bridge enabled on Proxmox
  • VLAN interfaces created on ER605
  • Services migrated to VLANs

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 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 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

Deployment

Operations

Document Status: Active
Maintained By: Infrastructure Team
Review Cycle: Weekly
Last Updated: 2025-01-20

Reference in New Issue View Git Blame Copy Permalink