Bootstrap grouped home reef repo
This commit is contained in:
parent
74ad256c04
commit
3f48975191
17 changed files with 621 additions and 1 deletions
22
substrate/topology.yaml
Normal file
22
substrate/topology.yaml
Normal file
|
|
@ -0,0 +1,22 @@
|
|||
reef_id: reef-railiance
|
||||
membership_policy: Add Railiance home servers here when they share one durable home-substrate boundary.
|
||||
members:
|
||||
- member_id: Railiance01
|
||||
role: first-current-member
|
||||
provider: HostEurope
|
||||
ip: 92.205.62.239
|
||||
ssh_user: tegwick
|
||||
evidence:
|
||||
- repo: railiance-infra
|
||||
path: inventory/servers.yaml
|
||||
- repo: railiance-infra
|
||||
path: docs/adr/ADR-004-forgejo-in-cluster-actions-runner.md
|
||||
access_surfaces:
|
||||
- type: ssh
|
||||
member: Railiance01
|
||||
user: tegwick
|
||||
- type: kubernetes-runtime
|
||||
rail: rail-kubernetes
|
||||
unresolved_questions:
|
||||
- Which future Railiance servers should join this grouped home reef first?
|
||||
- At what point would member divergence justify splitting this reef?
|
||||
Loading…
Add table
Add a link
Reference in a new issue