Skip to content

feat(gateway): add phase 4 kouja storage routing - #36

Open
msdmazvoid wants to merge 5 commits into
feat/kouja-storage-backend-phase3from
feat/kouja-storage-backend-phase4
Open

msdmazvoid wants to merge 5 commits into
feat/kouja-storage-backend-phase3from
feat/kouja-storage-backend-phase4

Conversation

@msdmazvoid

Copy link
Copy Markdown
Contributor

Summary

Phase 4 of the kouja storage backend, stacked on feat/kouja-storage-backend-phase3.

This wires the kouja driver into backend config, disk lifecycle, VM start planning, autostart, and deletion processing.

What changed

  • Accept and map nested config.kouja storage backends and driver selection.
  • Add kouja disk create/finalize/queue-delete paths, with 202 Accepted for remote deletes.
  • Add gateway health for kouja and LVM backends plus deletion backlog fields.
  • Route VM starts through vmstart.Planner and qemu.StartWithPlan in the gateway and API autostart.
  • Start the deletion reclaimer in serve and record protocol/locator/deletion fields in disk responses.
  • Add gateway integration coverage for kouja disk creation, VM start planning, and queued deletion.

Verification

  • go test ./... -count=1
  • make proto-check
  • make proto-compile
  • gofmt clean

Chain

Base PR: #35 (feat/kouja-storage-backend-phase3). Merge order: #32 → #33 → #34 → #35 → this PR.

Review-artifact scratch files are intentionally excluded.

Wire the kouja driver into disk create/delete, backend config mapping and selection, VM start planning, autostart, deletion reclamation, and backend health. Disk deletes now return 202 for queued remote cleanup.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant