Bootstrap grouped home reef repo
This commit is contained in:
parent
74ad256c04
commit
3f48975191
17 changed files with 621 additions and 1 deletions
33
docs/source-backed-substrate-facts.md
Normal file
33
docs/source-backed-substrate-facts.md
Normal file
|
|
@ -0,0 +1,33 @@
|
|||
# Source-Backed Substrate Facts
|
||||
|
||||
## Purpose
|
||||
|
||||
Record the first source-backed facts imported into `reef-railiance` for the
|
||||
grouped home reef bootstrap.
|
||||
|
||||
## Imported Facts
|
||||
|
||||
From `railiance-infra/inventory/servers.yaml`:
|
||||
|
||||
- current first member: `Railiance01`
|
||||
- member IP: `92.205.62.239`
|
||||
- member SSH user: `tegwick`
|
||||
|
||||
From `railiance-infra/docs/reef-first-wave-source-map.md`:
|
||||
|
||||
- this repo represents the grouped Railiance home reef rather than a singleton
|
||||
host repo
|
||||
- `rail-kubernetes` is the first primary rail stance
|
||||
- additional Railiance home servers should join this reef when they share the
|
||||
same lifecycle and workload-placement boundary
|
||||
|
||||
From `railiance-infra/docs/adr/ADR-004-forgejo-in-cluster-actions-runner.md`:
|
||||
|
||||
- Forgejo production and the in-cluster Actions runner already use
|
||||
`railiance01` as a Kubernetes-first operational substrate
|
||||
|
||||
## Explicit Gaps
|
||||
|
||||
- only one source-backed member is declared today
|
||||
- there is still no dedicated `host_vars/Railiance01.yml`
|
||||
- future grouped members and split criteria remain explicit follow-up work
|
||||
Loading…
Add table
Add a link
Reference in a new issue