proxmox/docs/archive/status/NEXT_STEPS_COMPLETION_STATUS.md

# Next Steps Completion Status

**Date:** December 26, 2024  
**Status:** In Progress

---

## ✅ Completed Tasks

### 1. Container Renaming
All 8 containers have been successfully renamed on ml110:
- ✅ 1504 → `besu-sentry-ali`
- ✅ 2503 → `besu-rpc-ali-0x8a`
- ✅ 2504 → `besu-rpc-ali-0x1`
- ✅ 2505 → `besu-rpc-luis-0x8a`
- ✅ 2506 → `besu-rpc-luis-0x1`
- ✅ 2507 → `besu-rpc-putu-0x8a`
- ✅ 2508 → `besu-rpc-putu-0x1`
- ✅ 6201 → `firefly-ali-1`

### 2. Proxmox VE Post-Install Script
- ✅ Connected to pve (192.168.11.11)
- ✅ Downloaded script from community-scripts/ProxmoxVE
- ⚠️ Script is interactive and requires manual execution

---

## ⏳ Pending Tasks

### 1. Container Migrations (CRITICAL)

**Status:** All containers still on ml110 (migrations failed)

**Issue:** Storage incompatibility
- Containers use `local-lvm` on ml110
- Target nodes (pve/pve2) only have `local` storage
- Direct migration fails due to storage type mismatch

**Required Actions:**

**Option A: Manual Migration via Proxmox Web UI** (Recommended)
1. Access Proxmox web UI
2. Navigate to each container
3. Use "Migrate" option
4. Select target node and storage
5. Proxmox will handle storage conversion

**Option B: Backup/Restore Method**
```bash
# For each container on ml110:
ssh root@192.168.11.10

# Create backup
vzdump <VMID> --storage local --compress zstd

# Copy backup to target node
scp /var/lib/vz/dump/vzdump-lxc-<VMID>*.tar.zst root@<TARGET_NODE>:/var/lib/vz/dump/

# On target node, restore with different storage
qmrestore /var/lib/vz/dump/vzdump-lxc-<VMID>*.tar.zst <VMID> --storage local
```

**Target Locations:**
- **To pve:** 1504, 2503, 2504, 6201
- **To pve2:** 2505, 2506, 2507, 2508

### 2. Proxmox VE Post-Install Script Completion

**Status:** Script downloaded but needs interactive execution

**Required Action:**
SSH into pve and run interactively:
```bash
ssh root@192.168.11.11
# password: password

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/post-pve-install.sh)"
```

The script will present interactive menus to:
- Configure Proxmox VE package sources
- Set up repository settings (enterprise vs no-subscription)
- Perform system updates
- Apply Proxmox VE optimizations

### 3. Verify Container Hostnames

**Status:** Hostnames show as "hostname" in config - may need verification

**Required Action:**
Verify and fix hostnames if needed:
```bash
ssh root@192.168.11.10
for vmid in 1504 2503 2504 2505 2506 2507 2508 6201; do
  pct set $vmid --hostname <correct-hostname>
done
```

**Expected Hostnames:**
- 1504: `besu-sentry-ali`
- 2503: `besu-rpc-ali-0x8a`
- 2504: `besu-rpc-ali-0x1`
- 2505: `besu-rpc-luis-0x8a`
- 2506: `besu-rpc-luis-0x1`
- 2507: `besu-rpc-putu-0x8a`
- 2508: `besu-rpc-putu-0x1`
- 6201: `firefly-ali-1`

### 4. ChainID 138 Deployment

**Status:** Waiting for container migrations to complete

**Required Actions (after migrations):**
1. Run deployment script:
   ```bash
   cd /home/intlc/projects/proxmox
   ./scripts/deploy-all-chain138-containers.sh
   ```

2. This will:
   - Configure all Besu nodes
   - Set up JWT authentication
   - Generate JWT tokens
   - Verify configuration

---

## 📋 Priority Order

1. **HIGH:** Complete Proxmox VE post-install script (interactive)
2. **HIGH:** Complete container migrations (manual or backup/restore)
3. **MEDIUM:** Verify and fix container hostnames
4. **MEDIUM:** Run ChainID 138 deployment scripts

---

## 🔧 Quick Reference Commands

### Check Container Status
```bash
ssh root@192.168.11.10 "pct list | grep -E '(1504|2503|2504|2505|2506|2507|2508|6201)'"
```

### Check Container Locations
```bash
ssh root@192.168.11.10 "for vmid in 1504 2503 2504 6201; do for node in ml110 pve; do pvesh get /nodes/\$node/lxc/\$vmid/status/current 2>/dev/null | grep -q 'status' && echo \"\$vmid: on \$node\" && break; done; done"
```

### Verify Hostnames
```bash
ssh root@192.168.11.10 "for vmid in 1504 2503 2504 2505 2506 2507 2508 6201; do echo -n \"\$vmid: \"; pct config \$vmid | grep '^hostname:'; done"
```

---

## 📝 Notes

- Container migrations require storage conversion which Proxmox handles better via web UI
- Post-install script is interactive and must be run in a proper terminal session
- All container configurations are ready once migrations complete
- JWT authentication setup will run automatically with deployment script

---

**Last Updated:** December 26, 2024