generated from coulomb/repo-seed
ops-hub-bootstrap
This commit is contained in:
@@ -152,10 +152,10 @@ Decision:
|
||||
possible, with a migration-backed fallback when a repeatable bootstrap is
|
||||
needed before the public API is hardened.
|
||||
- Treat Pattern A, API Consumer Hub, as the first implementation pattern.
|
||||
- Store VSM classification in the manifest capability description for now,
|
||||
because the current `hubs` table only has `slug`, `name`, `domain`, and
|
||||
`hub_kind`; there are no first-class `hub_family`, `vsm_function`, or
|
||||
`vsm_system` columns yet.
|
||||
- Store VSM classification in first-class hub metadata where the target
|
||||
Inter-Hub schema has `hub_family`, `vsm_function`, and `vsm_system`; keep the
|
||||
same values in the manifest capability description for compatibility with
|
||||
older deployments and API consumers.
|
||||
- Use `hub_kind = domain` for `ops-hub`.
|
||||
- Record missing first-class VSM metadata fields and create endpoints as
|
||||
Inter-Hub hardening work under T10.
|
||||
@@ -690,6 +690,38 @@ This workplan is complete when:
|
||||
9. The bootstrap path is reusable enough that `syn-hub` can be created next
|
||||
without rediscovering the whole process.
|
||||
|
||||
## Implementation Log
|
||||
|
||||
### 2026-05-19 — Live bootstrap access check
|
||||
|
||||
Attempted to execute the prepared bootstrap path.
|
||||
|
||||
Findings:
|
||||
|
||||
- `hub.coulomb.social` resolves to Railiance01 (`92.205.62.239`).
|
||||
- The current workstation kubeconfig has only the `default` context and points
|
||||
at CoulombCore (`92.205.130.254`).
|
||||
- `~/.kube/config-hosteurope` is missing, so the documented Railiance01
|
||||
kubeconfig path is not available locally.
|
||||
- `kubectl` against the current context has no `inter-hub` deployment because
|
||||
it is the CoulombCore cluster.
|
||||
- SSH key auth to `root@92.205.62.239`, `worsch@92.205.62.239`, and
|
||||
`ubuntu@92.205.62.239` was denied.
|
||||
|
||||
Result:
|
||||
|
||||
- Live `ops-hub` bootstrap was not applied from this session.
|
||||
- `wiki/ops-hub-bootstrap.sql` was strengthened to set first-class VSM hub
|
||||
metadata when the target Inter-Hub schema supports it.
|
||||
- `wiki/OpsHubBootstrapRunbook.md` now records the exact SQL fallback command
|
||||
to run from a Railiance01-capable session.
|
||||
|
||||
Next required operator action:
|
||||
|
||||
- Restore/provide Railiance01 Kubernetes access, or run
|
||||
`wiki/ops-hub-bootstrap.sql` from a host that already has access to the
|
||||
`net-kingdom-pg-1` pod in the `databases` namespace.
|
||||
|
||||
## Notes
|
||||
|
||||
`ops-hub` should complement State Hub during the transition:
|
||||
|
||||
Reference in New Issue
Block a user