d-bis/proxmox
4
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
master
proxmox/docs/03-deployment/MISSING_CONTAINERS_LIST.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

6.7 KiB
Raw Permalink Blame History

Missing LXC Containers - Complete List

Last Updated: 2026-02-08
Document Version: 1.2
Status: Active Documentation

VMIDs 2506, 2507, 2508 — destroyed 2026-02-08. These containers were removed and are no longer in the inventory. Besu RPC range is now 2500–2505 only. No other VMIDs are currently missing.

SSH review (2026-02-05): All three Proxmox hosts were checked via SSH (pct list). See MISSING_VMS_SSH_REVIEW_20260205.md for the full inventory comparison.

Date: December 26, 2024
Status: Inventory of containers; 2506–2508 destroyed 2026-02-08; updated after SSH review to match current hosts.

Summary

Missing: 0 VMIDs. 2506, 2507, 2508 were destroyed 2026-02-08 (see header). Besu RPC nodes in use: 2500–2505.

Category Missing Total Expected Status
Besu Nodes 0 16 16/16 deployed (2506–2508 removed)
Hyperledger Services 0 5 5/5 deployed
Explorer 0 1 1/1 deployed
TOTAL 0 22 22/22 deployed

🔴 Missing Containers by Category (post–SSH review)

Note: 1504, 2503, 2504, 2505 exist on hosts (as besu-sentry-ali, besu-rpc-hybx-1/2/3). Ali/Luis/Putu RPC nodes also exist on ml110 at VMIDs 2303–2308. 2506, 2507, 2508 were destroyed 2026-02-08 — no longer in inventory.

1. Besu Nodes (ChainID 138) — no missing VMIDs

Missing Sentry Node → Deployed (SSH review 2026-02-05)

VMID Hostname Role Actual (host) Notes
1504 besu-sentry-5 Sentry ml110: besu-sentry-ali ✅ Exists (name differs)

Missing RPC Nodes (2506, 2507, 2508) → Destroyed 2026-02-08

2503, 2504, 2505 exist on r630-01 as besu-rpc-hybx-1/2/3. VMIDs 2506, 2507, 2508 were removed and destroyed on all Proxmox hosts (2026-02-08). Script: scripts/destroy-vmids-2506-2508.sh. IPs 192.168.11.202, .203, .204 are freed. Besu RPC range is 2500–2505 only.

2. Hyperledger Services — all deployed (SSH review 2026-02-05)

Firefly

VMID Hostname Role Actual (host) Notes
6200 firefly-1 Firefly Core r630-02: firefly-1 ✅ Deployed
6201 firefly-2 Firefly Node r630-02: firefly-ali-1 ✅ Deployed (stopped) — start if needed

Specifications (per container):

  • Memory: 4GB
  • CPU: 2 cores
  • Disk: 50GB
  • Access: Ali (Full)

Notes:

  • 6201 is specifically mentioned in ChainID 138 documentation
  • 6200 is the core Firefly service

Cacti

VMID Hostname Role Actual (host) Notes
5200 cacti-1 Cacti r630-01: cacti-1 ✅ Deployed

Specifications:

  • Memory: 4GB
  • CPU: 2 cores
  • Disk: 50GB

Fabric

VMID Hostname Role Actual (host) Notes
6000 fabric-1 Fabric r630-01: fabric-1 ✅ Deployed

Specifications:

  • Memory: 8GB
  • CPU: 4 cores
  • Disk: 100GB

Indy

VMID Hostname Role Actual (host) Notes
6400 indy-1 Indy r630-01: indy-1 ✅ Deployed

Specifications:

  • Memory: 8GB
  • CPU: 4 cores
  • Disk: 100GB

3. Explorer — deployed (SSH review 2026-02-05)

Blockscout

VMID Hostname Role Actual (host) Notes
5000 blockscout-1 Blockscout r630-02: blockscout-1 ✅ Deployed

Specifications:

  • Memory: 8GB+
  • CPU: 4 cores+
  • Disk: 200GB+
  • Requires: PostgreSQL database

📊 Deployment Priority

To create

None. 2506, 2507, 2508 were destroyed 2026-02-08; no replacement planned.

Optional

  • 6201 — Start firefly-ali-1 on r630-02 if needed (container exists but stopped).

✅ Currently Deployed Containers (SSH review 2026-02-05)

Besu Network (16/19)

VMID Hostname (doc) Actual name/host Status
1000–1004 validators — ✅ Deployed
1500–1503 sentries — ✅ Deployed
1504 besu-sentry-5 besu-sentry-ali (ml110) ✅ Deployed
2500–2502 besu-rpc-1/2/3 — ✅ Deployed
2503 besu-rpc-4 besu-rpc-hybx-1 (r630-01) ✅ Deployed
2504 besu-rpc-4 besu-rpc-hybx-2 (r630-01) ✅ Deployed
2505 besu-rpc-luis besu-rpc-hybx-3 (r630-01) ✅ Deployed
2506 besu-rpc-luis — 🗑️ Destroyed 2026-02-08
2507 besu-rpc-putu — 🗑️ Destroyed 2026-02-08
2508 besu-rpc-putu — 🗑️ Destroyed 2026-02-08

Services & Hyperledger & Explorer

VMID Hostname Actual (host) Status
3500 oracle-publisher-1 — ✅ Deployed
3501 ccip-monitor-1 — ✅ Deployed
5000 blockscout-1 blockscout-1 (r630-02) ✅ Deployed
5200 cacti-1 cacti-1 (r630-01) ✅ Deployed
6000 fabric-1 fabric-1 (r630-01) ✅ Deployed
6200 firefly-1 firefly-1 (r630-02) ✅ Deployed
6201 firefly-2 firefly-ali-1 (r630-02) ✅ Deployed (stopped)
6400 indy-1 indy-1 (r630-01) ✅ Deployed

🚀 Deployment Scripts Available

For Besu Nodes

  • Main deployment: smom-dbis-138-proxmox/scripts/deployment/deploy-besu-nodes.sh
  • Configuration: scripts/configure-besu-chain138-nodes.sh
  • Quick setup: scripts/setup-new-chain138-containers.sh

For Hyperledger Services

  • Deployment: smom-dbis-138-proxmox/scripts/deployment/deploy-hyperledger-services.sh

For Explorer

  • Deployment: Check Blockscout deployment scripts

📝 Deployment Checklist (only missing items after SSH review)

Besu RPC — 2506, 2507, 2508 destroyed 2026-02-08

No create action. RPC range is 2500–2505 only.

Optional

  • 6201 - Start existing container firefly-ali-1 on r630-02 if needed

🔗 Related Documentation

📊 Summary Statistics

Missing: 0 VMIDs. 2506–2508 destroyed 2026-02-08.
Deployed: 22/22.
Important: RPC containers 2503–2505 require JWT authentication via nginx reverse proxy where used.

Last Updated: 2026-02-08 (2506–2508 destroyed); SSH review 2026-02-05; original list December 26, 2024

Reference in New Issue View Git Blame Copy Permalink