# Deployment Complete - Supporting Services

**Date**: 2026-01-04  
**Status**: ✅ **Containers Created and Started**

---

## Deployment Summary

Successfully deployed all three supporting service containers on r630-01:

| Service | VMID | IP | Status |
|---------|------|----|--------|
| Redis | 106 | 192.168.11.110 | ✅ Created & Started |
| Web3Signer | 107 | 192.168.11.111 | ✅ Created & Started |
| Vault | 108 | 192.168.11.112 | ✅ Created & Started |

---

## Deployment Details

### Container Specifications

- **Template**: ubuntu-22.04-standard
- **Storage**: local-lvm
- **Network**: vmbr0 bridge

### Redis (VMID 106)
- **IP**: 192.168.11.110
- **Hostname**: redis-rpc-translator
- **Resources**: 2 cores, 512MB RAM, 10GB disk
- **Port**: 6379

### Web3Signer (VMID 107)
- **IP**: 192.168.11.111
- **Hostname**: web3signer-rpc-translator
- **Resources**: 2 cores, 2048MB RAM, 20GB disk
- **Port**: 9000

### Vault (VMID 108)
- **IP**: 192.168.11.112
- **Hostname**: vault-rpc-translator
- **Resources**: 2 cores, 2048MB RAM, 20GB disk
- **Port**: 8200

---

## Next Steps

### 1. Configure Redis (VMID 106)

```bash
# Enter container
pct enter 106

# Install Redis
apt-get update
apt-get install -y redis-server

# Configure Redis
nano /etc/redis/redis.conf
# Set: bind 192.168.11.110
# Set: requirepass <password-from-env>
# Set: protected-mode yes

# Start Redis
systemctl enable redis-server
systemctl restart redis-server

# Test
redis-cli -h 192.168.11.110 ping
```

### 2. Configure Web3Signer (VMID 107)

```bash
# Enter container
pct enter 107

# Install dependencies
apt-get update
apt-get install -y openjdk-17-jre-headless wget

# Download Web3Signer
cd /opt
wget https://artifacts.consensys.net/web3signer/web3signer-23.10.0/web3signer-23.10.0.tar.gz
tar -xzf web3signer-23.10.0.tar.gz
cd web3signer-23.10.0

# Configure Web3Signer
# See DEPLOYMENT.md for detailed configuration

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

### 3. Configure Vault (VMID 108)

```bash
# Enter container
pct enter 108

# Install Vault
apt-get update
apt-get install -y unzip wget
wget https://releases.hashicorp.com/vault/1.15.0/vault_1.15.0_linux_amd64.zip
unzip vault_1.15.0_linux_amd64.zip
mv vault /usr/local/bin/
chmod +x /usr/local/bin/vault

# Initialize Vault (see DEPLOYMENT.md for production setup)
vault server -dev -dev-listen-address="192.168.11.112:8200"

# Configure AppRole (see DEPLOYMENT.md)
vault auth enable approle
# ... (see DEPLOYMENT.md for full configuration)

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

### 4. Verify Connectivity

From translator VMIDs (2400-2402) or Proxmox host:

```bash
# 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
```

### 5. Deploy Translator Service

After supporting services are configured:

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

See `DEPLOYMENT.md` for detailed instructions.

---

## Configuration Files

All secrets should be stored in `.env` files (one per service/VMID):
- Container configuration secrets
- Service passwords
- API tokens
- Vault credentials

**Never commit `.env` files to git** - they are in `.gitignore`.

---

## References

- **Deployment Guide**: `DEPLOYMENT.md`
- **LXC Deployment Guide**: `LXC_DEPLOYMENT.md`
- **VMID Allocation**: `VMID_ALLOCATION.md`
- **Deployment Checklist**: `DEPLOYMENT_CHECKLIST.md`

---

## Deployment Logs

Containers were deployed using:
- **Script**: `deploy-supporting-services.sh`
- **Node**: r630-01
- **Template**: ubuntu-22.04-standard (downloaded during deployment)
- **Method**: Direct deployment via SSH

All containers are created and started, ready for service configuration.
