proxmox/docs/archive/ACTION_PLAN_NOW.md

Action Plan - What to Do Right Now

🎯 Immediate Actions (Next 30 Minutes)

1. Verify Your Environment (5 minutes)

cd /home/intlc/projects/proxmox

# Check source project exists
ls -la /home/intlc/projects/smom-dbis-138/config/

# Check scripts are ready
ls -la smom-dbis-138-proxmox/scripts/deployment/deploy-validated-set.sh

2. Run Prerequisites Check (2 minutes) ✅ COMPLETE

cd /home/intlc/projects/proxmox
./smom-dbis-138-proxmox/scripts/validation/check-prerequisites.sh \
    /home/intlc/projects/smom-dbis-138

Status: ✅ PASSED (0 errors, 1 warning - config-sentry.toml optional) Result: All prerequisites met, ready to proceed

3. Prepare Proxmox Host Connection (5 minutes)

# Test SSH connection
ssh root@192.168.11.10

# If connection works, exit and continue
exit

4. Copy Scripts to Proxmox Host (10 minutes)

# Run copy script
./scripts/copy-scripts-to-proxmox.sh

# Follow prompts:
# - Confirm SSH connection
# - Confirm file copy
# - Verify scripts copied successfully

5. Test Dry-Run on Proxmox Host (10 minutes)

# SSH to Proxmox host
ssh root@192.168.11.10

# Navigate to deployment directory
cd /opt/smom-dbis-138-proxmox

# Run dry-run test
./scripts/deployment/deploy-validated-set.sh \
    --dry-run \
    --source-project /home/intlc/projects/smom-dbis-138

Expected: Shows what would be deployed without making changes

---

🧪 Testing Phase (Next 1-2 Hours)

6. Test Individual Scripts

# On Proxmox host
cd /opt/smom-dbis-138-proxmox

# Test bootstrap script
./scripts/network/bootstrap-network.sh --help

# Test validation script
./scripts/validation/validate-validator-set.sh --help

# Test health check
./scripts/health/check-node-health.sh 106

7. Verify Configuration Files

# Check config files exist
ls -la config/proxmox.conf config/network.conf

# Verify environment variables
cat ~/.env | grep PROXMOX

---

🚀 Deployment Phase (When Ready)

8. Pre-Deployment Checklist

• Prerequisites checked ✅
• Scripts copied to Proxmox ✅
• Dry-run tested ✅
• Configuration files ready
• Source project accessible
• Backup location configured

9. Execute Deployment

# On Proxmox host
cd /opt/smom-dbis-138-proxmox

# Full deployment
./scripts/deployment/deploy-validated-set.sh \
    --source-project /home/intlc/projects/smom-dbis-138

This will:

1. Deploy containers (1000-1004 validators, 1500-1503 sentries, 2500-2502 RPC)
2. Copy configuration files
3. Bootstrap network
4. Validate deployment

Time: ~30-60 minutes

10. Post-Deployment Verification

# Check all containers
for vmid in 1000 1001 1002 1003 1004 1500 1501 1502 1503 2500 2501 2502; do
    echo "=== Container $vmid ==="
    pct status $vmid
done

# Check services
for vmid in 1000 1001 1002 1003 1004; do
    pct exec $vmid -- systemctl status besu-validator --no-pager | head -5
done

---

🔧 Post-Deployment Setup (Next Hour)

11. Secure Keys

./scripts/secure-validator-keys.sh

12. Set Up Monitoring

# Install health check cron
./scripts/monitoring/setup-health-check-cron.sh

# Test alerts
./scripts/monitoring/simple-alert.sh

13. Configure Backups

# Test backup
./scripts/backup/backup-configs.sh

# Add to cron (daily at 2 AM)
crontab -e
# Add: 0 2 * * * /opt/smom-dbis-138-proxmox/scripts/backup/backup-configs.sh

---

📋 Quick Command Reference

Check Status

# All containers
for vmid in 1000 1001 1002 1003 1004 1500 1501 1502 1503 2500 2501 2502; do
    pct status $vmid
done

# All services
for vmid in 1000 1001 1002 1003 1004; do
    pct exec $vmid -- systemctl status besu-validator --no-pager | head -3
done

View Logs

# Recent logs
pct exec 1000 -- journalctl -u besu-validator -n 50 --no-pager

# Follow logs
pct exec 1000 -- journalctl -u besu-validator -f

Health Check

# Single node
./scripts/health/check-node-health.sh 1000

# All nodes
for vmid in 1000 1001 1002 1003 1004 1500 1501 1502 1503 2500 2501 2502; do
    ./scripts/health/check-node-health.sh $vmid
done

---

⚠️ Troubleshooting

If something goes wrong:

1. Check Troubleshooting FAQ: docs/TROUBLESHOOTING_FAQ.md
2. Check Logs: logs/deploy-validated-set-*.log
3. Verify Prerequisites: Run check script again
4. Rollback: Use snapshots if needed

---

✅ Success Criteria

Deployment is successful when:

• ✅ All containers running (1000-1004 validators, 1500-1503 sentries, 2500-2502 RPC)
• ✅ All services active (besu-validator, besu-sentry, besu-rpc)
• ✅ Peers connected (check with admin_peers)
• ✅ Blocks being produced (check logs)
• ✅ RPC endpoints responding (2500-2502)

---

Ready to start? Begin with Step 1 above!