# RPC VMID Migration - Current Status

**Last Updated:** 2026-01-31  
**Document Version:** 1.0  
**Status:** Active Documentation

---

**Date:** 2025-01-20  
**Status:** 🔄 **IN PROGRESS**

---

## Migration Progress

The migration script is currently running. Cloning containers can take 30-60 minutes per container depending on size and storage speed.

### Current Status

**Migration Started:** 2025-01-20 08:00  
**Process:** Running in background

### Completed Migrations

- ⏳ **2504 → 2304** (besu-rpc-ali-0x1) - **IN PROGRESS**
  - Status: Clone operation running
  - New VMID 2304 exists but in "create" state
  - Old VMID 2504 stopped for cloning

### Pending Migrations

The following migrations are queued and will proceed after current clone completes:

1. ⏳ 2500 → 2101 (besu-rpc-core-1)
2. ⏳ 2501 → 2201 (besu-rpc-public-1)
3. ⏳ 2502 → 2301 (besu-rpc-private-1)
4. ⏳ 2400 → 2401 (besu-rpc-thirdweb-0x8a-1)
5. ⏳ 2401 → 2402 (besu-rpc-thirdweb-0x8a-2)
6. ⏳ 2402 → 2403 (besu-rpc-thirdweb-0x8a-3)
7. ⏳ 2503 → 2303 (besu-rpc-ali-0x8a)
8. ⏳ 2505 → 2305 (besu-rpc-luis-0x8a)
9. ⏳ 2506 → 2306 (besu-rpc-luis-0x1)
10. ⏳ 2507 → 2307 (besu-rpc-putu-0x8a)
11. ⏳ 2508 → 2308 (besu-rpc-putu-0x1)

---

## Monitoring Migration

### Check Clone Progress

```bash
# Check if clone processes are running
ssh root@192.168.11.10 "ps aux | grep 'pct clone' | grep -v grep"

# Check status of new VMIDs
ssh root@192.168.11.10 "pct list | grep -E '^(2101|2201|2301|2303|2304|2305|2306|2307|2308|2401|2402|2403)'"

# Check status of old VMIDs
ssh root@192.168.11.10 "pct list | grep -E '^(2500|2501|2502|2503|2504|2505|2506|2507|2508|2400|2401|2402)'"
```

### Check Migration Log

```bash
tail -f /tmp/rpc-migration.log
```

---

## Expected Timeline

- **Per Container Clone:** 5-15 minutes (depending on size)
- **Total Migration Time:** 1-3 hours for all 12 containers
- **Network Configuration:** ~1 minute per container
- **Total Estimated Time:** 2-4 hours

---

## What's Happening

1. **Clone Operation:** Creating full copies of containers with new VMIDs
2. **Storage Allocation:** Allocating disk space for new containers
3. **Network Configuration:** Updating IP addresses after clone completes
4. **Hostname Update:** Setting new hostnames

---

## Important Notes

- ✅ Old containers remain intact (for safety)
- ✅ Old containers are stopped during cloning
- ✅ Migration can be safely interrupted (old containers preserved)
- ⚠️ Do not delete old containers until new ones are verified
- ⚠️ Migration script will skip already-cloned VMIDs if re-run

---

## Next Steps After Migration Completes

1. Verify all new VMIDs exist and are configured
2. Start new containers
3. Deploy Besu node files to new containers
4. Restart Besu services
5. Verify connectivity
6. Update NPMplus proxy rules (if needed)
7. Decommission old containers (after verification)

---

## Troubleshooting

### If Migration Appears Stuck

1. Check if clone process is actually running:
   ```bash
   ssh root@192.168.11.10 "ps aux | grep 'pct clone'"
   ```

2. Check storage space:
   ```bash
   ssh root@192.168.11.10 "vgs && lvs"
   ```

3. Check container status:
   ```bash
   ssh root@192.168.11.10 "pct list | grep create"
   ```

### If Migration Fails

1. Check error logs
2. Verify storage availability
3. Check network connectivity
4. Re-run migration script (it will skip completed migrations)

---

**Last Updated:** 2025-01-20 08:05  
**Next Check:** Monitor clone progress