diff --git a/docs/dev/assets/dynamo-nvcf-boundary.svg b/docs/dev/assets/dynamo-nvcf-boundary.svg new file mode 100644 index 000000000..d25df639f --- /dev/null +++ b/docs/dev/assets/dynamo-nvcf-boundary.svg @@ -0,0 +1,172 @@ + + + Dynamo NVCF Boundary + Sequence diagram showing the responsibility boundary between NVCF, NVCA, Kubernetes, the Dynamo Operator, Grove and KAI, and the Dynamo runtime. + + + + + + + + + + + + + + Dynamo NVCF Boundary + + + + NVCF Control Plane + Deployment intent + + + NVCA 3.2.5 + Cluster lifecycle + + + Kubernetes API + DynamoGraphDeployment + + + Dynamo Operator 1.2.1 + Graph reconciliation + + + Grove alpha.11 + KAI 0.17 + Placement and scheduling + + + Dynamo Runtime + Frontend + GPU workers + + + + + + + + + + + Create • Update • Terminate + + + Apply desired graph + + + Desired graph event + + + Update graph status + + + Create and reconcile resources + + + Group and schedule GPU pods + + + + Worker readiness + + + Deployment status + + + + + + + + + + + + + + + Inference routing boundary after the deployment is ready + + + Inference Request + + + + + NVCF Multi-Cluster + Routing + + + + + Dynamo Frontend + In-cluster routing + + + + + GPU Workers + + + + + Response + + + + NVCF owns deployment intent and multi-cluster routing. NVCA reports lifecycle status. Dynamo owns graph reconciliation and in-cluster routing. +