Files

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

2.9 KiB

Raw Blame History

Cohort D Review — Proxmox SSH & dotenv

Date: 2026-01-31
Scope: Cohort D (D1–D5), dotenv, SSH connectivity

SSH Connectivity ✅

Host	IP	SSH	Hostname	Uptime	LXC Count
ml110	192.168.11.10	✅	ml110	40 days 16h	18
r630-01	192.168.11.11	✅	r630-01	7 days 23h	70
r630-02	192.168.11.12	✅	r630-02	7 days 23h	11

All three Proxmox VE hosts are reachable via SSH as root.

dotenv (.env) — Current State

Root `.env` (project root)

Variable	Present	Value / Fallback
NPM_URL	✅	https://192.168.11.167:81
NPM_EMAIL	✅	(set)
NPM_PASSWORD	✅	(set)
NPM_HOST	✅	192.168.11.167
PUBLIC_IP	✅	76.53.10.36
PROXMOX_ML110	❌	—
PROXMOX_R630_01	❌	—
PROXMOX_R630_02	❌	—
PROXMOX_HOST	❌	—
NPMPLUS_HOST	❌	—
NPMPLUS_VMID	❌	—

Script fallbacks (when vars not in .env)

Scripts use these defaults when env vars are unset:

NPMPLUS_HOST: NPM_PROXMOX_HOST → PROXMOX_HOST → 192.168.11.11
NPMPLUS_VMID: NPM_VMID → 10233
PROXMOX_HOST: 192.168.11.11 (in check-udm-pro-config, ensure-npmplus)
PROXMOX_HOST_ML110: 192.168.11.10 (in check-all-proxmox-hosts)
PROXMOX_HOST_R630_01: 192.168.11.11
PROXMOX_HOST_R630_02: 192.168.11.12

So Cohort D scripts still work without explicit vars because of these fallbacks.

Cohort D Task Status

ID	Task	Host	Depends	Status
D1	Verify ml110 containers	ml110	SSH	✅ SSH works; 18 LXC
D2	Verify r630-01 containers	r630-01	SSH	✅ SSH works; 70 LXC
D3	Verify r630-02 containers	r630-02	SSH	✅ SSH works; 11 LXC
D4	Backup NPMplus	r630-01	SSH, NPM_PASSWORD	✅ creds in .env; NPMPLUS_HOST defaults to 192.168.11.11
D5	Export Prometheus targets	r630-01	SSH	✅ SSH works

Updates (2026-01-31)

D4: backup-npmplus.sh ran successfully (API exports, DB backup).
D5: export-prometheus-targets.sh created; targets-proxmox.yml exported.
PROXMOX_*: Added to root .env (PROXMOX_ML110, PROXMOX_R630_01, PROXMOX_R630_02, NPMPLUS_HOST, NPMPLUS_VMID).

Recommendations

~~Optional:~~ Add to root .env for clarity and centralization — DONE

PROXMOX_ML110=192.168.11.10
PROXMOX_R630_01=192.168.11.11
PROXMOX_R630_02=192.168.11.12
NPMPLUS_HOST=192.168.11.11
NPMPLUS_VMID=10233

D4 (Backup NPMplus): Run from project root:
```
./scripts/verify/backup-npmplus.sh
```
Uses .env and will SSH to r630-01 for VMID 10233.
D5 (Prometheus targets): Use smom-dbis-138/monitoring/prometheus/scrape-proxmox.yml; targets can be exported from r630-01 via SSH.

2.9 KiB Raw Blame History Unescape Escape