Skip to content

docs: cross-link federation docs with edge instance-provisioning architecture#157

Open
scotwells wants to merge 1 commit into
mainfrom
docs/cross-link-instance-provisioning
Open

docs: cross-link federation docs with edge instance-provisioning architecture#157
scotwells wants to merge 1 commit into
mainfrom
docs/cross-link-instance-provisioning

Conversation

@scotwells

Copy link
Copy Markdown
Contributor

What this gives readers

Someone reading the compute architecture docs today can follow a Workload all the way to "the POP cell creates Instances" — and then the trail goes cold. The edge half of the story (how a created Instance becomes a booted unikernel: host assignment, networking, Kraftlet) lives in the unikraft-provider repo, with no pointer from here. This PR adds cross-links at the exact spots where the federation docs hand off to the edge, so readers can continue into Instance Provisioning via Kraftlet without knowing in advance which repo holds it.

Changes

  • docs/enhancements/federated-deployment-scheduling.md — two prose links: one after the Creation Path sequence diagram (where the POP cell steps are summarized), one at the end of the WorkloadDeploymentReconciler section (where Instance materialization is described).
  • docs/compute/development/rfcs/workloads/README.md — one link at the end of the Control Loops section, after the Workload Scheduler diagram, covering what happens once a WorkloadDeployment is assigned a location.

No generated API references (docs/api/) were touched.

Merge ordering

The linked doc lands with datum-cloud/unikraft-provider#9 — merge this PR after that one, since the links 404 until it merges.

🤖 Generated with Claude Code

…itecture

Point readers from the federation/control-plane docs to the unikraft-provider
doc covering how edge locations turn Instances into running unikernels.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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