d-bis/proxmox
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
4eead3e53fecdb2b7e629bb9f56b22ff92c61d2e
proxmox/docs/archive/CURRENT_DEPLOYMENT_STATUS.md
defiQUG fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
Details
docs: Ledger Live integration, contract deploy learnings, NEXT_STEPS updates 
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands
- CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround
- CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check
- NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere
- MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates
- LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-12 15:46:57 -08:00

273 lines
7.9 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Current Deployment Status on ml110
**Last Checked**: $(date)
**Proxmox Host**: ml110 (192.168.11.10)
## Summary
**Current Active Deployment** on ml110:
1. ✅ **LXC Containers (1000-2502)**: All 12 containers running
2. ⏸️ **VM 9000**: Shutdown (stopped on $(date))
---
## Deployment 1: LXC Containers (1000-2502)
### Status Overview
| VMID | Hostname | Status | IP Address | Memory | Cores | Notes |
|------|----------|--------|------------|--------|-------|-------|
| 1000 | besu-validator-1 | ✅ Running | 192.168.11.33 | 8GB | 4 | ⚠️ Using DHCP (not static IP) |
| 1001 | besu-validator-2 | ✅ Running | 192.168.11.101 | 8GB | 4 | ✅ Static IP |
| 1002 | besu-validator-3 | ✅ Running | 192.168.11.102 | 8GB | 4 | ✅ Static IP |
| 1003 | besu-validator-4 | ✅ Running | 192.168.11.103 | 8GB | 4 | ✅ Static IP |
| 1004 | besu-validator-5 | ✅ Running | 192.168.11.104 | 8GB | 4 | ✅ Static IP |
| 1500 | besu-sentry-1 | ✅ Running | 192.168.11.150 | 4GB | 2 | ✅ Static IP |
| 1501 | besu-sentry-2 | ✅ Running | 192.168.11.151 | 4GB | 2 | ✅ Static IP |
| 1502 | besu-sentry-3 | ✅ Running | 192.168.11.152 | 4GB | 2 | ✅ Static IP |
| 1503 | besu-sentry-4 | ✅ Running | 192.168.11.153 | 4GB | 2 | ✅ Static IP |
| 2500 | besu-rpc-1 | ✅ Running | 192.168.11.250 | 16GB | 4 | ✅ Static IP |
| 2501 | besu-rpc-2 | ✅ Running | 192.168.11.251 | 16GB | 4 | ✅ Static IP |
| 2502 | besu-rpc-3 | ✅ Running | 192.168.11.252 | 16GB | 4 | ✅ Static IP |
**Total Resources**:
- **Total Memory**: 104GB (8GB × 5 + 4GB × 4 + 16GB × 3)
- **Total CPU Cores**: 40 cores (4 × 5 + 2 × 4 + 4 × 3)
- **All Containers**: ✅ Running
### Service Status
⚠️ **Besu Services**: Currently **inactive** in all containers
The containers are running, but the Besu services (besu-validator, besu-sentry, besu-rpc) are not active. This suggests:
- Services may not be installed yet
- Services may need to be started
- Configuration may be pending
**To check service status**:
```bash
# Check if services exist
pct exec 1000 -- systemctl list-unit-files | grep besu
# Check service status
pct exec 1000 -- systemctl status besu-validator
# Start services (if installed)
pct exec 1000 -- systemctl start besu-validator
```
### IP Address Configuration
**Note**: VMID 1000 (besu-validator-1) is using DHCP (192.168.11.33) instead of the expected static IP (192.168.11.100). All other containers have correct static IPs.
**Expected vs Actual IPs**:
| VMID | Expected IP | Actual IP | Status |
|------|-------------|-----------|--------|
| 1000 | 192.168.11.100 | 192.168.11.33 | ⚠️ DHCP |
| 1001 | 192.168.11.101 | 192.168.11.101 | ✅ |
| 1002 | 192.168.11.102 | 192.168.11.102 | ✅ |
| 1003 | 192.168.11.103 | 192.168.11.103 | ✅ |
| 1004 | 192.168.11.104 | 192.168.11.104 | ✅ |
| 1500 | 192.168.11.150 | 192.168.11.150 | ✅ |
| 1501 | 192.168.11.151 | 192.168.11.151 | ✅ |
| 1502 | 192.168.11.152 | 192.168.11.152 | ✅ |
| 1503 | 192.168.11.153 | 192.168.11.153 | ✅ |
| 2500 | 192.168.11.250 | 192.168.11.250 | ✅ |
| 2501 | 192.168.11.251 | 192.168.11.251 | ✅ |
| 2502 | 192.168.11.252 | 192.168.11.252 | ✅ |
---
## Deployment 2: VM 9000 (Temporary VM with Docker)
### Status Overview
| Property | Value |
|----------|-------|
| **VMID** | 9000 |
| **Name** | besu-temp-all-nodes |
| **Status** | ✅ Running |
| **Memory** | 32GB (32768 MB) |
| **CPU Cores** | 6 cores |
| **Disk** | 1000GB (1TB) |
| **Configured IP** | 192.168.11.90/24 |
| **Gateway** | 192.168.11.1 |
### Current Status
⏸️ **VM Status**: **STOPPED**
VM 9000 has been shutdown to free resources. The VM can be restarted if needed for testing or migration purposes.
**Previous Issues** (before shutdown):
- SSH Access: Not accessible via SSH
- QEMU Guest Agent: Not running
- Network: Connectivity blocked
### Docker Containers Status
❓ **Unknown**: Cannot verify Docker container status due to SSH connectivity issue
Expected containers (if Docker is set up):
- 5 validator containers (besu-validator-1 through besu-validator-5)
- 4 sentry containers (besu-sentry-1 through besu-sentry-4)
- 3 RPC containers (besu-rpc-1 through besu-rpc-3)
**To check VM 9000 status**:
```bash
# Check VM status
qm status 9000
# Try console access
qm terminal 9000
# Check via Proxmox web interface
# Navigate to: https://192.168.11.10:8006 -> VM 9000 -> Console
# Once accessible via SSH:
ssh root@192.168.11.90
docker ps
cd /opt/besu && docker compose ps
```
---
## Resource Comparison
### Current Resource Usage
| Deployment | Containers/VMs | Total Memory | Total CPU Cores | Disk |
|------------|---------------|--------------|-----------------|------|
| **LXC (1000-2502)** | 12 containers | 104GB (106,496 MB) | 40 cores | ~1.2TB |
| **VM 9000** | ⏸️ Stopped | 0GB | 0 cores | 1TB (allocated but unused) |
| **Total Active** | 12 containers | 104GB | 40 cores | ~1.2TB |
### Resource Allocation Notes
- Both deployments are running simultaneously
- Total memory usage: ~136GB across both deployments
- This represents significant resource allocation
- Consider shutting down one deployment if both are not needed
---
## Recommendations
### 1. Fix VMID 1000 IP Configuration
VMID 1000 should have static IP 192.168.11.100 instead of DHCP:
```bash
pct set 1000 --net0 name=eth0,bridge=vmbr0,ip=192.168.11.100/24,gw=192.168.11.1,type=veth
pct reboot 1000
```
### 2. Verify Besu Services in LXC Containers
Check if Besu is installed and start services:
```bash
# Check installation
pct exec 1000 -- which besu
pct exec 1000 -- ls -la /opt/besu
# Check service files
pct exec 1000 -- ls -la /etc/systemd/system/besu-*.service
# If installed, start services
for vmid in 1000 1001 1002 1003 1004; do
pct exec $vmid -- systemctl start besu-validator
pct exec $vmid -- systemctl enable besu-validator
done
```
### 3. Investigate VM 9000 Connectivity
```bash
# Check VM console
qm terminal 9000
# Or access via Proxmox web UI console
# Check if cloud-init completed
# Check if SSH is running
# Verify network configuration
```
### 4. Decide on Deployment Strategy
Since both deployments are running:
- **If using LXC (1000-2502) for production**: Consider shutting down VM 9000 to free resources
- **If using VM 9000 for testing**: Consider shutting down LXC containers to free resources
- **If testing migration**: Keep both running temporarily
**To shut down VM 9000**:
```bash
qm stop 9000
```
**To shut down LXC containers**:
```bash
for vmid in 1000 1001 1002 1003 1004 1500 1501 1502 1503 2500 2501 2502; do
pct stop $vmid
done
```
---
## Quick Status Check Commands
### Check LXC Containers
```bash
# List all containers
pct list | grep -E '^100[0-9]|^150[0-9]|^250[0-2]'
# Check specific container
pct status 1000
pct config 1000
# Check IPs
for vmid in 1000 1001 1002 1003 1004 1500 1501 1502 1503 2500 2501 2502; do
pct exec $vmid -- hostname -I
done
```
### Check VM 9000
```bash
# VM status
qm status 9000
qm config 9000
# Try console
qm terminal 9000
# Check via Proxmox API/CLI
pvesh get /nodes/pve/qemu/9000/status/current
```
---
## Next Steps
1. ✅ Verify current status (done)
2. ✅ Fix VMID 1000 IP configuration (COMPLETED - IP now 192.168.11.100)
3. ✅ Verify Besu services installation in LXC containers (COMPLETED - 11/12 services active)
4. ✅ Investigate VM 9000 SSH connectivity (COMPLETED - Network issue identified, requires console access)
5. ✅ Provide recommendation on which deployment to keep active (See recommendation below)
6. ✅ Start Besu services in active deployment (COMPLETED - Services started)
**See [Next Steps Completed Report](NEXT_STEPS_COMPLETED.md) for detailed completion report**
---
**Related Documentation**:
- [Deployment Comparison](DEPLOYMENT_COMPARISON.md)
- [Deployment Quick Reference](DEPLOYMENT_QUICK_REFERENCE.md)
- [Deployment Status Consolidated](../03-deployment/DEPLOYMENT_STATUS_CONSOLIDATED.md) | [smom-dbis-138-proxmox](https://github.com/Order-of-Hospitallers/smom-dbis-138) (external)
Reference in New Issue View Git Blame Copy Permalink