97 lines
2.7 KiB
Markdown
97 lines
2.7 KiB
Markdown
# Quick Start - Validated Set Deployment
|
|
|
|
## Step 1: Copy Scripts to Proxmox Host
|
|
|
|
First, copy the deployment scripts to the Proxmox host:
|
|
|
|
```bash
|
|
# From your local machine
|
|
cd /home/intlc/projects/proxmox
|
|
./scripts/copy-scripts-to-proxmox.sh
|
|
```
|
|
|
|
This will copy all scripts to `/opt/smom-dbis-138-proxmox` on the Proxmox host.
|
|
|
|
## Step 2: Run Deployment
|
|
|
|
Then SSH to the Proxmox host and run deployment:
|
|
|
|
```bash
|
|
ssh root@192.168.11.10
|
|
cd /opt/smom-dbis-138-proxmox
|
|
sudo ./scripts/deployment/deploy-validated-set.sh \
|
|
--source-project /home/intlc/projects/smom-dbis-138
|
|
```
|
|
|
|
**Note**: The source project path `/home/intlc/projects/smom-dbis-138` must be accessible from the Proxmox host. If the Proxmox host is a different machine, you may need to copy the config files separately or mount a shared directory.
|
|
|
|
## What Gets Deployed
|
|
|
|
- **Validators**: 5 nodes (1000-1004)
|
|
- **Sentries**: 4 nodes (1500-1503)
|
|
- **RPC Nodes**: 3 nodes (2500-2502)
|
|
- **Total**: 12 Besu nodes
|
|
|
|
## Deployment Phases
|
|
|
|
1. ✅ **Deploy Containers** - Creates LXC containers
|
|
2. ✅ **Copy Configs** - Copies genesis, configs, keys
|
|
3. ✅ **Bootstrap Network** - Generates and deploys static-nodes.json
|
|
4. ✅ **Validate** - Validates all validators and services
|
|
|
|
## After Deployment
|
|
|
|
```bash
|
|
# Check all services
|
|
for vmid in 1000 1001 1002 1003 1004 1500 1501 1502 1503 2500 2501 2502; do
|
|
pct exec $vmid -- systemctl status besu-validator besu-sentry besu-rpc --no-pager 2>/dev/null | head -3
|
|
done
|
|
|
|
# Validate validators
|
|
sudo ./scripts/validation/validate-validator-set.sh
|
|
|
|
# Check node health
|
|
sudo ./scripts/health/check-node-health.sh 1000
|
|
```
|
|
|
|
## Help
|
|
|
|
```bash
|
|
# Main script help
|
|
./scripts/deployment/deploy-validated-set.sh --help
|
|
|
|
# Individual script help
|
|
./scripts/health/check-node-health.sh # shows usage
|
|
```
|
|
|
|
## Full Documentation
|
|
|
|
See `docs/VALIDATED_SET_DEPLOYMENT_GUIDE.md` for complete details.
|
|
|
|
## Important: Source Project Path Accessibility
|
|
|
|
When running on the Proxmox host, the source project path must be accessible from that machine.
|
|
|
|
**Option 1: If Proxmox host can access the path**
|
|
```bash
|
|
# On Proxmox host
|
|
sudo ./scripts/deployment/deploy-validated-set.sh \
|
|
--source-project /home/intlc/projects/smom-dbis-138
|
|
```
|
|
|
|
**Option 2: If Proxmox host is remote, copy config files first**
|
|
```bash
|
|
# From local machine, copy config files to Proxmox host
|
|
scp -r /home/intlc/projects/smom-dbis-138/config root@192.168.11.10:/tmp/smom-config
|
|
scp -r /home/intlc/projects/smom-dbis-138/keys root@192.168.11.10:/tmp/smom-keys
|
|
|
|
# On Proxmox host, use the copied location
|
|
sudo ./scripts/deployment/deploy-validated-set.sh \
|
|
--source-project /tmp/smom-config
|
|
```
|
|
|
|
**Option 3: Use NFS or shared mount** (if configured)
|
|
```bash
|
|
# Mount shared directory on Proxmox host, then use mount path
|
|
```
|