d-bis/proxmox
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Reclassify DBIS placeholder Hyperledger CTs
All checks were successful
Deploy to Phoenix / deploy (push) Successful in 6s
Details

Browse Source
This commit is contained in:
defiQUG
2026-03-28 23:21:51 -07:00
parent 7d0462c1c1
commit d6aebf3c43
6 changed files with 163 additions and 145 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/03-deployment/DBIS_HYPERLEDGER_RUNTIME_STATUS.md
View File

@@ -24,12 +24,12 @@ The checks were based on:
|------|----------------|-----------|------------------|--------------------------|-------|
| `6200` | FireFly primary | Running | Healthy minimal local gateway | `5000/tcp` FireFly API, `5432/tcp` Postgres, `5001/tcp` IPFS | `firefly-core` restored on `ghcr.io/hyperledger/firefly:v1.2.0`; `GET /api/v1/status` returned `200`; Postgres `pg_isready` passed; IPFS version probe passed |
| `6201` | FireFly secondary | Stopped | Formally retired until rebuilt | None verified | CT exists in inventory, but the rootfs is effectively empty and no valid FireFly deployment footprint was found. Treat this as retired / standby metadata only until it is intentionally rebuilt as a real secondary node. |
| `6000` | Fabric primary | Running | CT footprint only | No Fabric listener verified | CT is up, but app-native checks found no active Fabric peer/orderer/couchdb processes, no expected listeners such as `7050` / `7051`, and no meaningful Fabric payload under `/opt`, `/etc`, or `/var`. |
| `6001` | Fabric secondary | Running | CT footprint only | No Fabric listener verified | Same current state as `6000`: container present, no proven Fabric application payload or listeners. |
| `6002` | Fabric tertiary | Running | CT footprint only | No Fabric listener verified | Same current state as `6000`: container present, no proven Fabric application payload or listeners. |
| `6400` | Indy primary | Running | CT footprint only | No Indy listener verified | CT is up, but app-native checks found no active Indy-related processes, no expected listeners such as `9701`-`9708`, and no meaningful Indy payload under `/opt`, `/etc`, or `/var`. |
| `6401` | Indy secondary | Running | CT footprint only | No Indy listener verified | Same current state as `6400`: container present, no proven Indy application payload or listeners. |
| `6402` | Indy tertiary | Running | CT footprint only | No Indy listener verified | Same current state as `6400`: container present, no proven Indy application payload or listeners. |
| `6000` | Fabric primary | Stopped | Reserved placeholder | None active | App-native checks found no active Fabric peer/orderer/couchdb processes, no expected listeners such as `7050` / `7051`, and no meaningful Fabric payload under `/opt`, `/etc`, or `/var`. The CT has now been stopped and retained only as a reserved placeholder. |
| `6001` | Fabric secondary | Stopped | Reserved placeholder | None active | Same disposition as `6000`: no proven Fabric application payload or listeners, now stopped and reserved only as placeholder inventory. |
| `6002` | Fabric tertiary | Stopped | Reserved placeholder | None active | Same disposition as `6000`: no proven Fabric application payload or listeners, now stopped and reserved only as placeholder inventory. |
| `6400` | Indy primary | Stopped | Reserved placeholder | None active | App-native checks found no active Indy-related processes, no expected listeners such as `9701`-`9708`, and no meaningful Indy payload under `/opt`, `/etc`, or `/var`. The CT has now been stopped and retained only as a reserved placeholder. |
| `6401` | Indy secondary | Stopped | Reserved placeholder | None active | Same disposition as `6400`: no proven Indy application payload or listeners, now stopped and reserved only as placeholder inventory. |
| `6402` | Indy tertiary | Stopped | Reserved placeholder | None active | Same disposition as `6400`: no proven Indy application payload or listeners, now stopped and reserved only as placeholder inventory. |
## Interpretation
@@ -37,12 +37,12 @@ The checks were based on:
- FireFly primary (`6200`) is restored enough to provide a working local FireFly API backed by Postgres and IPFS.
### Present only as container footprints right now
### Present only as reserved placeholders right now
- Fabric CTs (`6000`-`6002`)
- Indy CTs (`6400`-`6402`)
These should be described as container footprints only, not as active Fabric or Indy application nodes. Current app-native validation found no meaningful service payload, processes, or expected listeners inside those CTs.
These should be described as reserved placeholder inventory only, not as active Fabric or Indy application nodes. Current app-native validation found no meaningful service payload, processes, or expected listeners inside those CTs, and they have now been stopped to match that reality.
### Not currently active
@@ -53,8 +53,8 @@ These should be described as container footprints only, not as active Fabric or
1. Keep `6200` under observation and preserve its working config/image path.
2. Do not force `6201` online unless its intended role and deployment assets are re-established from scratch.
3. For Fabric and Indy, the next step is no longer generic validation. It is either:
- deploy real app payloads and verify them, or
- formally reclassify these CTs as reserved placeholders rather than active DLT workloads.
- deploy real app payloads onto these reserved CTs and verify them, or
- leave them stopped and classified as reserved placeholders rather than active DLT workloads.
4. Any governance or architecture document should distinguish:
- `deployed and app-healthy`
- `container present only`

16
docs/03-deployment/DBIS_PHASES_1_TO_3_PRODUCTION_GATE.md
View File

@@ -22,8 +22,8 @@
### What is not yet proven production-ready
- FireFly secondary failover footprint (`6201`) is not deployed; it is currently retired / standby until rebuilt
- Fabric peer / orderer workload health inside `6000-6002`
- Indy validator / node listener health inside `6400-6402`
- Fabric peer / orderer workload health inside `6000-6002`; those CTs are now intentionally stopped as reserved placeholders
- Indy validator / node listener health inside `6400-6402`; those CTs are now intentionally stopped as reserved placeholders
- Sovereignized Phase 2 platform baseline:
- Ceph-backed storage
- final VLAN segmentation
@@ -71,8 +71,8 @@
| Automated liveness wrapper exists | Complete | [scripts/verify/run-dbis-phase3-e2e-simulation.sh](../../scripts/verify/run-dbis-phase3-e2e-simulation.sh) |
| Besu liveness passes | Complete | direct script output and [scripts/verify/check-chain138-rpc-health.sh](../../scripts/verify/check-chain138-rpc-health.sh) |
| FireFly HTTP liveness passes | Complete | `6200` returns `HTTP 200` on `/api/v1/status` |
| Fabric app-native business flow validation passes | Blocked | CTs are present, but current checks found no active Fabric payload, processes, or listeners |
| Indy app-native business flow validation passes | Blocked | CTs are present, but current checks found no active Indy payload, processes, or listeners |
| Fabric app-native business flow validation passes | Blocked | Current checks found no active Fabric payload, processes, or listeners; CTs are now intentionally stopped as reserved placeholders |
| Indy app-native business flow validation passes | Blocked | Current checks found no active Indy payload, processes, or listeners; CTs are now intentionally stopped as reserved placeholders |
| Cross-chain / Cacti business flow validation passes | Blocked | not currently proven as deployed live DBIS path |
| Full business E2E has been demonstrated | Blocked | current wrapper is intentionally liveness-only |
@@ -85,8 +85,8 @@
The following items still prevent a full “DBIS Chain 138 production complete” declaration:
1. `6201` is not a verified active secondary FireFly node and is currently treated as retired / standby until rebuilt.
2. Fabric `6000-6002` are not yet proven as active peer/orderer workloads; current evidence shows CT footprints only.
3. Indy `6400-6402` are not yet proven as active validator workloads; current evidence shows CT footprints only.
2. Fabric `6000-6002` are not active peer/orderer workloads; current evidence showed placeholder CTs only, and they have now been stopped and retained as reserve inventory.
3. Indy `6400-6402` are not active validator workloads; current evidence showed placeholder CTs only, and they have now been stopped and retained as reserve inventory.
4. Phase 2 sovereignization is still roadmap work, not completed platform state.
5. The current Phase 3 wrapper is liveness validation, not end-to-end business certification.
@@ -107,8 +107,8 @@ It is **not** yet accurate to declare:
## Next production-closing actions
1. Decide whether `6201` is to be rebuilt as a real secondary FireFly node or left retired as a reserve inventory slot.
2. Either deploy real Fabric workloads inside `6000-6002` and validate them, or reclassify those CTs as placeholders.
3. Either deploy real Indy workloads inside `6400-6402` and validate them, or reclassify those CTs as placeholders.
2. Either deploy real Fabric workloads inside `6000-6002` and validate them, or leave those CTs stopped as reserved placeholders.
3. Either deploy real Indy workloads inside `6400-6402` and validate them, or leave those CTs stopped as reserved placeholders.
4. Execute the first real Phase 2 platform milestone:
- fleet expansion, or
- Ceph pilot, or