proxmox/rpc-translator-138/DEPLOYMENT_STATUS.md

Deployment Status - RPC Translator Supporting Services

Date: 2026-01-04
Status: ✅ Scripts and Documentation Complete
Ready for: Container Deployment on r630-01

---

✅ Completed Items

1. Documentation

• ✅ VMID_ALLOCATION.md - VMID and IP allocation documented
• ✅ DEPLOYMENT.md - Complete deployment guide (automated + manual)
• ✅ DEPLOYMENT_CHECKLIST.md - Step-by-step deployment checklist
• ✅ LXC_DEPLOYMENT.md - Detailed LXC container deployment guide
• ✅ VERIFICATION_SUMMARY.md - Template and node verification guide
• ✅ DOCUMENTATION_UPDATES.md - Documentation update summary

2. Deployment Scripts

• ✅ verify-node-ready.sh - Node readiness verification script
• ✅ deploy-supporting-services.sh - Automated container deployment script
• ✅ Scripts are executable and ready to use

3. Configuration Templates

• ✅ env.template - Environment variable template with actual IPs
• ✅ systemd/rpc-translator-138.service - Systemd service file
• ✅ All configuration files ready

4. VMID and IP Allocation

• ✅ Redis: VMID 106, IP 192.168.11.110
• ✅ Web3Signer: VMID 107, IP 192.168.11.111
• ✅ Vault: VMID 108, IP 192.168.11.112
• ✅ All allocations documented in VMID_IP_ADDRESS_LIST.md

---

⏳ Pending Deployment Steps

Phase 1: Verify Node Readiness (On Proxmox Host)

Run on r630-01 or Proxmox host with API access:

cd /path/to/proxmox/rpc-translator-138
./verify-node-ready.sh r630-01

This will verify:

• Node r630-01 is online
• Storage (local-lvm) is available
• LXC templates (ubuntu-22.04) are downloaded
• Network bridge (vmbr0) exists
• Sufficient resources (6GB+ RAM, 50GB+ disk)
• VMIDs 106, 107, 108 are available

Phase 2: Download Template (If Needed)

If template is missing, download via CLI:

pveam download local ubuntu-22.04-standard_22.04-1_amd64.tar.zst

Or via Web UI:

1. Datacenter > Storage > local
2. Templates tab
3. Download Templates
4. Select ubuntu-22.04-standard
5. Download

Phase 3: Deploy Supporting Services

Automated Deployment (Recommended):

./deploy-supporting-services.sh r630-01

Manual Deployment: See DEPLOYMENT.md or LXC_DEPLOYMENT.md for manual steps

Phase 4: Start and Configure Containers

Start containers:

pct start 106  # Redis
pct start 107  # Web3Signer
pct start 108  # Vault

Configure each service:

• Redis: See DEPLOYMENT.md section "Redis VMID 106"
• Web3Signer: See DEPLOYMENT.md section "Web3Signer VMID 107"
• Vault: See DEPLOYMENT.md section "Vault VMID 108"

Phase 5: Verify Services

Test connectivity from translator VMIDs (2400-2402) or Proxmox host:

# Test Redis
redis-cli -h 192.168.11.110 ping

# Test Web3Signer
curl http://192.168.11.111:9000/upcheck

# Test Vault
curl http://192.168.11.112:8200/v1/sys/health

Phase 6: Deploy Translator Service

After supporting services are running:

1. Deploy translator to VMIDs 2400-2402
2. Configure .env files with supporting service IPs
3. Start translator services
4. Test end-to-end functionality

---

📋 Quick Reference

Container Specifications

Service	VMID	IP	RAM	Disk	Port	Status
Redis	106	192.168.11.110	512MB	10GB	6379	⏳ Pending
Web3Signer	107	192.168.11.111	2048MB	20GB	9000	⏳ Pending
Vault	108	192.168.11.112	2048MB	20GB	8200	⏳ Pending

Required Resources

• Memory: 6GB+ free
• Disk: 50GB+ free on local-lvm
• Template: ubuntu-22.04-standard
• Network: vmbr0 bridge

Key Files

• Verification: verify-node-ready.sh
• Deployment: deploy-supporting-services.sh
• Guide: DEPLOYMENT.md
• Checklist: DEPLOYMENT_CHECKLIST.md
• LXC Guide: LXC_DEPLOYMENT.md

---

🔗 Related Documentation

• Main Deployment Guide: DEPLOYMENT.md
• Deployment Checklist: DEPLOYMENT_CHECKLIST.md
• LXC Deployment Guide: LXC_DEPLOYMENT.md
• VMID Allocation: VMID_ALLOCATION.md
• Verification Guide: VERIFICATION_SUMMARY.md

---

Next Actions

1. SSH to r630-01 (192.168.11.11)
2. Run verification script: ./verify-node-ready.sh r630-01
3. If verification passes, run deployment: ./deploy-supporting-services.sh r630-01
4. Follow configuration steps in DEPLOYMENT.md

All scripts and documentation are ready. The deployment can proceed once executed on the Proxmox host.