Add model registration and qualification handoff#419
Closed
Thump604 wants to merge 1 commit intofeat/model-acquisition-workflowfrom
Closed
Add model registration and qualification handoff#419Thump604 wants to merge 1 commit intofeat/model-acquisition-workflowfrom
Thump604 wants to merge 1 commit intofeat/model-acquisition-workflowfrom
Conversation
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.
Stacked on #417. This keeps the first model artifact workflow PR reviewable, then adds the next handoff layer without mutating any local Ops registry.
Scope:
vllm-mlx model register <artifact>to write a portablevllm_mlx_registration_manifest.jsonproduction_ready=falsevllm-mlx model qualify <model-id>to create or run abench-servequalification handoff command and optional request manifestLocal validation:
CLI smokes:
Dependency note:
model qualify --workloadis intended to compose with #406's workload contract support. Without that bench-serve support, the dry-run manifest is still useful, but running the generated command with--workloaddepends on #406 or equivalent landing.