Skip to content

Add and validate GB300 recipe overlays #1318

Description

@yuanchen8911

Goal

Add concrete service-bound recipe overlays for GB300 so aicr recipe --accelerator gb300 --service <y> --intent <z> resolves a usable recipe end-to-end, with no GB300 coverage today.

GB300 is currently undeclared in pkg/recipe/criteria.go (declared accelerators: a100, b200, gb200, h100, h200, l40, rtx-pro-6000) and has zero overlays under recipes/overlays/. ROADMAP.md frames GB300 as a near-horizon target.

Scope

  1. Declare CriteriaAcceleratorGB300 in pkg/recipe/criteria.go and wire ParseCriteriaAcceleratorType + GetCriteriaAcceleratorTypes.
  2. Add a gb300-any.yaml wildcard stub plus concrete service-bound overlays for the primary deployment shapes (training and inference on the major hyperscalers), modeled on the existing GB200 overlays (gb200-eks-*, gb200-oke-*).
  3. Reference the new overlays in recipes/overlays_validation_floor_test.go (or record an exemption).

Success criteria (per parent epic #1042)

  1. recipes/overlays/ contains at least one concrete service-bound overlay (non-wildcard) for GB300's primary deployment intent.
  2. aicr recipe --accelerator gb300 --service <y> --intent <z> resolves a recipe without manual overlay authoring.
  3. The overlay is covered by recipes/overlays_validation_floor_test.go.

Sub-issue of #1042 (Recipe overlay coverage). Tuning-profile reuse from GB200 should be considered where applicable.

Metadata

Metadata

Assignees

Type

Fields

No fields configured for Task.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions