proxmox/rpc-translator-138/DEPLOYMENT_STATUS_FINAL.md

Final Deployment Status

Date: 2026-01-05
Status: Supporting Services Complete - Translator Deployment Ready

---

✅ Completed

Supporting Services (100% Complete)

1. Redis (VMID 106) ✅

   • IP: 192.168.11.110:6379
   • Status: Running, responding (PONG)
   • Fully operational

2. Web3Signer (VMID 107) ✅

   • IP: 192.168.11.111:9000
   • Status: Running, health check: OK
   • Version: 25.12.0
   • Java: 21.0.9
   • ChainID: 138
   • Fully operational

3. Vault (VMID 108) ✅

   • IP: 192.168.11.112:8200
   • Status: Running, healthy
   • AppRole configured
   • Credentials generated
   • Fully operational

---

⏳ Remaining: Translator Deployment

Prerequisites Check

Before deploying the translator service, verify:

1. VMIDs 2400-2402 exist and are accessible

   • Check if VMIDs exist: pvesh get /nodes/r630-01/lxc or /qemu
   • Verify SSH access: ssh root@192.168.11.240 (and .241, .242)
   • Ensure Besu is running on each VMID

2. Network connectivity

   • Translator VMIDs can reach:
     • Redis: 192.168.11.110:6379
     • Web3Signer: 192.168.11.111:9000
     • Vault: 192.168.11.112:8200

3. Node.js installed

   • Each VMID needs Node.js 20+ and pnpm
   • Installation: curl -fsSL https://deb.nodesource.com/setup_20.x | bash - && apt-get install -y nodejs && npm install -g pnpm

---

Deployment Steps

Step 1: Deploy Translator Service

Option A: Automated Deployment (Recommended)

cd /home/intlc/projects/proxmox/rpc-translator-138
./scripts/deploy-all-vmids.sh

Option B: Individual Deployment

./scripts/deploy-to-vmid.sh 2400 192.168.11.240
./scripts/deploy-to-vmid.sh 2401 192.168.11.241
./scripts/deploy-to-vmid.sh 2402 192.168.11.242

Option C: Manual Deployment (if scripts don't work)

For each VMID (2400, 2401, 2402):

ssh root@192.168.11.240  # or .241, .242

# Install Node.js 20 and pnpm
curl -fsSL https://deb.nodesource.com/setup_20.x | bash -
apt-get install -y nodejs
npm install -g pnpm

# Create directory
mkdir -p /opt/rpc-translator-138
cd /opt/rpc-translator-138

# Copy files (from deployment machine)
# Option 1: Git clone
# Option 2: SCP/RSYNC

# Install dependencies and build
pnpm install --prod
pnpm run build

Step 2: Configure .env Files

For each VMID (2400, 2401, 2402):

ssh root@192.168.11.240  # or .241, .242
cd /opt/rpc-translator-138
cp env.template .env
nano .env  # Edit with actual values

Required Configuration (from env.template):

# Supporting Services
WEB3SIGNER_URL=http://192.168.11.111:9000
REDIS_HOST=192.168.11.110
REDIS_PORT=6379
REDIS_PASSWORD=
VAULT_ADDR=http://192.168.11.112:8200
VAULT_ROLE_ID=19cbc945-fb7f-9ec7-c262-37c71bbdc610
VAULT_SECRET_ID=7bcb887b-725c-2e70-3367-886cee25ad94

# Besu Upstream (local on each VMID)
BESU_HTTP_URLS=http://127.0.0.1:8545
BESU_WS_URLS=ws://127.0.0.1:8546
CHAIN_ID=138

# Translator Policy
WALLET_ALLOWLIST=0x...,0x...,0x...  # Add wallet addresses when ready
MAX_GAS_LIMIT=30000000
MAX_GAS_PRICE_WEI=100000000000
MIN_GAS_PRICE_WEI=1000000000

Validate configuration:

node scripts/validate-config.js

Step 3: Install Systemd Service

For each VMID:

ssh root@192.168.11.240  # or .241, .242
cd /opt/rpc-translator-138

# Copy systemd service file
cp systemd/rpc-translator-138.service /etc/systemd/system/

# Enable and start
systemctl daemon-reload
systemctl enable rpc-translator-138.service
systemctl start rpc-translator-138.service
systemctl status rpc-translator-138.service

Step 4: Verify Services

Check service status:

# On each VMID
systemctl status rpc-translator-138.service
journalctl -u rpc-translator-138.service -f

Test health endpoint:

curl http://192.168.11.240:9545/health  # or .241, .242

Test RPC endpoint:

curl -X POST http://192.168.11.240:9545 \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
# Should return: {"jsonrpc":"2.0","id":1,"result":"0x8a"} (138 in hex)

---

Service Configuration Reference

Redis Credentials:

• Host: 192.168.11.110
• Port: 6379
• Password: (none configured)

Web3Signer:

• URL: http://192.168.11.111:9000
• ChainID: 138
• Status: Running, ready for signing requests

Vault Credentials:

• Address: http://192.168.11.112:8200
• Role ID: 19cbc945-fb7f-9ec7-c262-37c71bbdc610
• Secret ID: 7bcb887b-725c-2e70-3367-886cee25ad94

---

Next Steps After Deployment

1. ✅ Supporting services - COMPLETE
2. ⏳ Deploy translator to VMIDs 2400-2402
3. ⏳ Configure .env files on translator VMIDs
4. ⏳ Start translator services
5. ⏳ Configure Web3Signer signing keys (when ready)
6. ⏳ Test end-to-end functionality
7. ⏳ Configure edge routing (if needed)

---

Troubleshooting

If deployment fails:

1. Check VMID accessibility:

   ssh root@192.168.11.240  # Test SSH access
   

2. Check Besu is running:

   ssh root@192.168.11.240
   systemctl status besu-rpc.service  # or similar
   curl http://127.0.0.1:8545 -X POST -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
   

3. Check service connectivity:

   # From translator VMID
   curl http://192.168.11.111:9000/upcheck  # Web3Signer
   redis-cli -h 192.168.11.110 ping  # Redis
   curl http://192.168.11.112:8200/v1/sys/health  # Vault
   

4. Check logs:

   journalctl -u rpc-translator-138.service -n 100
   

---

Summary

Supporting Services: ✅ 100% Complete (3/3 operational) Translator Deployment: ⏳ Pending (requires VMID access verification)

All supporting infrastructure is ready. Translator deployment can proceed once VMIDs 2400-2402 are verified to exist and be accessible.