Add instance provisioning lifecycle sequence diagrams#9
Draft
scotwells wants to merge 20 commits into
Draft
Conversation
Add sequence diagrams showing end-to-end instance provisioning and deletion flows via Kraftlet with Galactic CNI for VPC networking. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
06091f8 to
7cb9289
Compare
Updates both provisioning and deletion sequence diagrams to explicitly show Multus CNI as the meta-CNI orchestrator and a new IPAM CNI plugin that calls the Datum Cloud IPAM service for IP allocation/release. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…grams Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…sioning Introduces a HOST (Linux Network Stack) participant in the Unikraft Host box. The Galactic CNI now explicitly drives VRF/TAP creation through HOST, and the Unikraft Runtime binds the TAP device to the instance via HOST, making the two-stage provisioning (CNI provisions, runtime binds) visible. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
676bcad to
2ace5e6
Compare
Add a top-down Architecture Overview ahead of the detailed sequence diagrams: the platform path from a user Workload through Karmada federation out to edge-location Instances, then the per-location component view that turns each Instance into a running unikernel. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Convert the two overview component diagrams (Workload-to-edge federation and the per-location Instance flow) from flowcharts to sequence diagrams for consistency with the detailed diagrams in this document. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add a resource relationship flowchart and notes showing how the compute objects relate: Workload owns WorkloadDeployments (per placement/city code), which own Instance replicas, and how Instances reference Networks, ConfigMaps/Secrets, and Locations. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Adds a PlantUML C4 container diagram showing the deployed pieces of the compute system across its four planes (project control plane, Karmada federation, edge POP-cell cluster, Unikraft host), styled with the shared Datum theme from datum-cloud/enhancements. Relationship labels name the resource mediating each operator hand-off, and the reading guide calls out the declarative-to-imperative frontier at Kraftlet. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Collapses operator-internal controllers (Workload controller, WorkloadDeployment federator/controller) into their deployable unit — the Compute Operator, which runs in both the project control plane and each edge location. Adds a reading-guide note mapping sequence-diagram lifelines (controllers) to C4 level 3 components within these containers. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Rewrites the container descriptions, relationship labels, and reading guide for a consumer/architect audience: drops operator jargon (reconcile, NAD, Multus, VRF/veth, SRv6) in favor of plain descriptions of what each piece does and hands off. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Renders the API servers, Galactic networking pieces, and Unikraft host runtime (Kraftlet, unikernel) in the muted external style, leaving only the compute system's own services (Compute Operator, Unikraft Provider, Platform Services) as internal containers. Updates the reading guide to explain the color split. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Simplifies the edge location to the Edge API Server, Compute Operator, and Platform Services; the elided services are noted in the reading guide and traced in full by the sequence diagrams. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Keeps the top-down flow but lays the federation hand-off out to the side: the project control plane packs its two containers side by side and the edge location sits to the right of Karmada, taking the diagram from a 1305x1854 strip to a near-square 1549x1643. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Switch the container diagram to a left-to-right layout so the provisioning spine reads in flow order, and regenerate the PNG to match the source. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The container diagram speaks for itself; readers don't need rendering instructions in the architecture doc. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Point readers of the instance-provisioning doc at the compute repo's Federated Deployment Scheduling enhancement and the foundational Workload RFC, and link the README to the architecture doc. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds sequence diagrams showing how instance provisioning and deletion work end-to-end, from Instance creation through VPC network connectivity via the Galactic CNI plugin.
🤖 Generated with Claude Code