platform/orca-platform
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(iac): scaffold orca-platform layout (M1.1) #3

Merged
sharang merged 3 commits from feat/m1.1-iac-layout into main 2026-05-18 20:28:41 +00:00
Conversation 0 Commits 3 Files Changed 53
+1023 -35
3 Commits
Author SHA1 Message Date
sharang 3d7b67060e fix(iac): drop vms/ — Orca does not provision VMs
ci / shared (pull_request) Successful in 3s
Details
ci / validate (pull_request) Successful in 2s
Details 
Re-read the Orca spec: 'orca nodes' lists already-joined hosts and
'orca join' attaches an existing node to a cluster, but Orca does not
provision the VMs themselves. VM provisioning (SysEleven OpenStack
via Terraform) is a separate concern and will land in a dedicated repo
under the M1.2 milestone, not in orca-platform.

Removes vms/{vm-edge,vm-control,vm-data,stage}.toml + vms/README.md.
Updates README directory tree and milestone fill-in table to reflect
that M1.2's VM specs live elsewhere. validate.sh stops checking vms/.

Refs: M1.1
 2026-05-18 22:13:32 +02:00
sharang 1a728428cf chore(domain): yourplatform.com → breakpilot.com
ci / shared (pull_request) Successful in 5s
Details
ci / validate (pull_request) Successful in 2s
Details 
Apply the platform-domain decision (2026-05-18) to every manifest,
overlay, DNS template, README, and script in this repo.

Refs: M1.1
 2026-05-18 22:07:41 +02:00
sharang 6cd1a1546c feat(iac): scaffold orca-platform layout (M1.1)
ci / shared (pull_request) Successful in 4s
Details
ci / validate (pull_request) Successful in 3s
Details 
Lands the per-VM × per-service manifest tree, per-env overlays, VM specs
for SysEleven provisioning, DNS zone placeholder, plan/apply/validate
scripts, and a Makefile.

Structure (per INFRASTRUCTURE.md §2 + IMPLEMENTATION_PLAN.md M1.1):
- manifests/{vm-edge,vm-control,vm-data,stage}/<service>.toml — 35 stubs
- overlays/{dev,stage,prod}/overlay.toml — env-selection rules
- vms/{vm-edge,vm-control,vm-data,stage}.toml — OpenStack flavor/IP/firewall
- dns/yourplatform.com.zone.template — PowerDNS zone (body lands in M0.3)
- cluster.toml.tmpl — cluster-level config rendered per env
- scripts/validate.sh — TOML parse + structural sanity
- scripts/plan.sh — merge manifests + overlay → .orca-out/<env>/
- scripts/apply.sh — push to Orca controller (no-op until M1.2)
- Makefile — validate / plan / apply / diff / clean

Each manifest header names the milestone that finalises its real values;
images today are 'placeholder' for services that need their own repo to
exist first. make validate stays green; apply gates on ORCA_API_URL.

CI workflow swapped from the broken 'orca validate' to 'make validate',
which calls a Python TOML parser plus structural checks (placement.node
matches vm dir, resources.memory present, no mis-nested keys).

Refs: M1.1
 2026-05-18 22:02:11 +02:00