33d50fb91e
Some checks failed
API CI / API Lint (push) Successful in 47s
API CI / API Type Check (push) Failing after 47s
API CI / API Test (push) Successful in 1m0s
API CI / API Build (push) Failing after 50s
API CI / Build Docker Image (push) Has been skipped
Build Crossplane Provider / build (push) Failing after 5m51s
CD Pipeline / Deploy to Staging (push) Failing after 29s
CI Pipeline / Lint and Type Check (push) Failing after 36s
CI Pipeline / Build (push) Has been skipped
CI Pipeline / Test Backend (push) Failing after 1m33s
CI Pipeline / Test Frontend (push) Failing after 30s
CI Pipeline / Security Scan (push) Failing after 1m16s
Crossplane Provider CI / Go Test (push) Failing after 3m23s
Crossplane Provider CI / Go Lint (push) Failing after 7m27s
Crossplane Provider CI / Go Build (push) Failing after 3m27s
Deploy to Staging / Deploy to Staging (push) Failing after 30s
Portal CI / Portal Lint (push) Failing after 21s
Portal CI / Portal Type Check (push) Failing after 21s
Portal CI / Portal Test (push) Failing after 21s
Portal CI / Portal Build (push) Failing after 22s
Test Suite / frontend-tests (push) Failing after 30s
Test Suite / api-tests (push) Failing after 49s
Test Suite / blockchain-tests (push) Failing after 30s
Type Check / type-check (map[directory:. name:root]) (push) Failing after 23s
Type Check / type-check (map[directory:api name:api]) (push) Failing after 21s
Type Check / type-check (map[directory:portal name:portal]) (push) Failing after 19s
Validate Configuration Files / validate (push) Failing after 1m52s
CD Pipeline / Deploy to Production (push) Has been skipped
Co-authored-by: Cursor <cursoragent@cursor.com>
2.1 KiB
2.1 KiB
VM Deployment In Progress
Date: 2025-12-13
Status: 🟡 DEPLOYMENT IN PROGRESS
Deployment Status
Summary
- Total VMs: 30
- Deployed in Kubernetes: 30
- Created on Proxmox: In progress
- Expected Completion: 30-60 minutes
Deployment Phases
✅ Phase 1: Core Infrastructure
- nginx-proxy-vm (ML110-01)
- cloudflare-tunnel-vm (R630-01)
✅ Phase 2: Phoenix Infrastructure
- dns-primary (ML110-01)
- git-server (R630-01)
- email-server (R630-01)
- devops-runner (R630-01)
- codespaces-ide (R630-01)
- as4-gateway (R630-01)
- business-integration-gateway (R630-01)
- financial-messaging-gateway (R630-01)
✅ Phase 3: Blockchain Infrastructure
- Validators (4x) - R630-01
- Sentries (4x) - ML110-01 (2x), R630-01 (2x)
- RPC Nodes (4x) - R630-01
- Services (4x) - R630-01
- management
- monitoring
- services
- blockscout
Monitoring
Real-Time Monitoring
# Watch all VMs
kubectl get proxmoxvm -A -w
# Check deployment progress
./scripts/monitor-vm-deployment.sh
# View provider logs
kubectl logs -n crossplane-system -l app=crossplane-provider-proxmox -f
Check VM Status
# List all VMs with status
kubectl get proxmoxvm -A -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.status.vmId}{"\t"}{.status.state}{"\n"}{end}'
# Count VMs with VMID
kubectl get proxmoxvm -A -o jsonpath='{range .items[*]}{.status.vmId}{"\n"}{end}' | grep -v "^$" | wc -l
Expected Timeline
- Per VM: 2-5 minutes
- Small VMs (2 CPU, 4 GiB): 2-3 minutes
- Medium VMs (4 CPU, 16 GiB): 3-5 minutes
- Large VMs (500 GiB disk): 5-10 minutes
- Total Time: 30-60 minutes for all 30 VMs
Provider Status
- Pod: Running (1/1 Ready)
- Authentication: Token-based (working)
- Sites: site-1 (ML110-01), site-2 (R630-01)
Next Steps
- ✅ All VMs deployed in Kubernetes
- 🟡 Provider processing VM creation
- ⏳ Monitor deployment progress
- ⏳ Verify VMs created on Proxmox
- ⏳ Post-deployment verification
Last Updated: 2025-12-13
Status: 🟡 DEPLOYMENT IN PROGRESS