refactor(configs): migrate compute configs to ComputeConfig schema#742
Merged
Conversation
Aydin-ab
commented
Jun 3, 2026
Aydin-ab
added a commit
that referenced
this pull request
Jun 3, 2026
Per review on #742: from the user perspective there is only one ComputeConfig schema. Signed-off-by: Aydin Abiar <aydin@anyscale.com>
Aydin-ab
force-pushed
the
migrate-template-compute-configs
branch
from
7abed91 to
eda5ebe
Compare
Aydin-ab
added a commit
that referenced
this pull request
Jun 5, 2026
configs/ now uses the new user-facing ComputeConfig schema (#742): rewrite the schema reference, flip the legacy warning in conventions, and simplify the create-template compute-config step (workspace config is now copied as-is, pruned of defaults). Signed-off-by: Aydin Abiar <aydin@anyscale.com>
Aydin-ab
added a commit
that referenced
this pull request
Jun 5, 2026
Per review on #742: from the user perspective there is only one ComputeConfig schema. Signed-off-by: Aydin Abiar <aydin@anyscale.com>
elliot-barn
approved these changes
Jun 5, 2026
| @@ -1,11 +1,9 @@ | |||
| head_node_type: | |||
Contributor
There was a problem hiding this comment.
This isn't used in the template right?
Contributor
Author
There was a problem hiding this comment.
indeed, that's an orphan compute config folder. We can cleanup/declutter orphans later, i'm just removing any trace of the legacy schema in this PR
Migrate every compute config under configs/ from the legacy CreateComputeTemplateConfig schema to the new user-facing ComputeConfig schema (head_node/worker_nodes/min_nodes/max_nodes/market_type/enable_cross_zone_scaling), pruning defaults (min 0, ON_DEMAND, auto_select false, unschedulable-by-default head resources). Flip ci/validate_build_yaml.py to validate the new schema: strict top-level keys reject legacy configs, and auto_select_worker_config cannot be combined with worker_nodes (mirrors the SDK constraint). Published bundles are unaffected: rayapp build converts new->legacy at publish time (ray-project/rayci#492), so the console clone path keeps receiving legacy configs. Signed-off-by: Aydin Abiar <aydin@anyscale.com>
There is only one ComputeConfig schema from the user perspective; rename New* models and reword comments/errors accordingly. Per review. Signed-off-by: Aydin Abiar <aydin@anyscale.com>
Aydin-ab
force-pushed
the
migrate-template-compute-configs
branch
from
eda5ebe to
8867057
Compare
Aydin-ab
added a commit
that referenced
this pull request
Jun 8, 2026
configs/ now uses the new user-facing ComputeConfig schema (#742): rewrite the schema reference, flip the legacy warning in conventions, and simplify the create-template compute-config step (workspace config is now copied as-is, pruned of defaults). Signed-off-by: Aydin Abiar <aydin@anyscale.com>
Aydin-ab
added a commit
that referenced
this pull request
Jun 8, 2026
Per review on #742: from the user perspective there is only one ComputeConfig schema. Signed-off-by: Aydin Abiar <aydin@anyscale.com>
elliot-barn
approved these changes
Jun 8, 2026
Aydin-ab
added a commit
that referenced
this pull request
Jun 8, 2026
Documents the user-facing `ComputeConfig` schema as the `configs/` convention: rewrites `schemas/compute-config-schema.yaml`, updates the warning in `references/conventions.md`, and simplifies the create-template compute-config step (workspace config is copied as-is, pruned of defaults — no more schema translation). Lands after #742. --------- Signed-off-by: Aydin Abiar <aydin@anyscale.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
2 participants
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.
Migrates all 111 compute configs under
configs/from the legacy schema to the user-facingComputeConfigschema; flipsci/validate_build_yaml.pyto validate it.Published bundles are unchanged —
rayapp buildconverts to the legacy bundle format at publish time (ray-project/rayci#492, shipped in rayci v0.45.0, now pinned on main). Validated: converter audit 111/111; staging publishes tmpl-publish #367–#369; release-binary smoke #371 (v0.45.0 → staging, clone path verified).