Add pd-disaggregation release support#1
Open
fwyc0573 wants to merge 3 commits into
Open
Conversation
Constraint: PR preparation is local-only for worktrees/Frontier and scoped to frontier/ plus tests/unit core transfer paths; no push, release, or PR publication. Rejected: Blindly applying the full pre-release-v0.2 patch queue | mixed commits contain examples, old pd-only names, and unrelated release hardening outside this commit boundary. Confidence: high Scope-risk: moderate Directive: Keep follow-up example scripts and final naming cleanup in separate commits so review can isolate core simulator behavior from docs/examples wording. Tested: PYTHONPATH=/local/ycfeng/frontier/worktrees/Frontier conda run -n frontier python -m pytest tests/unit/test_pd_transfer_entities.py tests/unit/test_pd_transfer_predictors.py tests/unit/test_pd_transfer_types_and_configs.py tests/unit/test_kv_transfer_completion_contract.py tests/unit/test_prefix_cache_cluster_validation.py tests/unit/test_request_generator_decode_bound_count.py -q -> 25 passed in 1.23s; changed_python_files=40 py_compile PASS; git diff --check PASS; staged_unexpected_files=0. Not-tested: Full final preparation gate is reserved for the completed three-commit branch.
Constraint: Commit is limited to examples/architecture/pdd, examples indexes, transfer config boundary checks, and PDD smoke/cross-validation tests for the local worktrees/Frontier PR branch. Rejected: Applying the full examples patch | target main already contains co-location offline/online layout, and broad co-location rewrites are outside the pd-disaggregation PR boundary. Confidence: high Scope-risk: moderate Directive: Keep generated outputs, analysis/performance harnesses, root docs, and profiling docs out of this PR unless a future scope expansion explicitly includes them. Tested: PYTHONPATH=/local/ycfeng/frontier/worktrees/Frontier conda run -n frontier python -m pytest tests/unit/test_examples_pdd_scripts.py tests/unit/test_pdd_scripts_cross_validate.py tests/e2e/test_pd_disaggregation_example_script_smoke.py tests/e2e/test_pdd_example_scripts_smoke.py -q -> 22 passed in 16.70s; changed_python_files=8 py_compile PASS; pdd_shell_scripts=12 bash -n PASS; git diff --check PASS; staged_unexpected_files=0. Not-tested: Full final preparation gate is reserved for the completed three-commit branch.
Constraint: Commit is limited to final naming cleanup and the naming guard for tracked frontier/examples/tests content on the local worktrees/Frontier PR branch. Rejected: Broad rename of historical analysis, generated outputs, profiling docs, or performance artifacts | those paths are outside patch_queue_audit.md allowlist for this PR. Confidence: high Scope-risk: narrow Directive: Keep retired pd-only spellings out of source-facing frontier/examples/tests paths; use string splitting in guard tests when a negative assertion must mention a retired token. Tested: PYTHONPATH=/local/ycfeng/frontier/worktrees/Frontier conda run -n frontier python -m pytest tests/unit/test_pd_disaggregation_naming_guard.py -q -> 1 passed in 0.10s; PYTHONPATH=/local/ycfeng/frontier/worktrees/Frontier conda run -n frontier python -m pytest tests/unit/test_examples_pdd_scripts.py -q -> 8 passed in 0.08s; changed_python_files=4 py_compile PASS; git diff --check PASS; staged_unexpected_files=0; case-insensitive old-name rg returned 0 hits. Not-tested: Full final preparation gate is reserved for the completed three-commit branch.
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
1 participant
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
This PR adds the public pd-disaggregation path prepared for the v0.2 release surface.
examples/architecture/pdd/, plus smoke tests and script cross-checks.pd-onlytopd-disaggregation, with a naming guard to keep the old term out offrontier/,examples/, andtests/.Scope
frontier/examples/tests/Validation
Environment:
conda run -n frontier, Python 3.10.20.python -m frontier.main --sys_arch pd-disaggregationexits with code 1, prints the--no-enable_parallel_clustersguidance, and does not print a Python traceback.git diff --check: pass.frontier/,examples/, andtests/: 358 tracked files scanned, 0 path hits, 0 content hits.main..HEAD: 61 changed files, 0 files outside the allowed PR scope.Release surface
The public pd-disaggregation path is limited to sequential cluster execution in this PR. Runs that omit
--no-enable_parallel_clustersfail fast with a clean CLI error because parallel cluster processing for pd-disaggregation is outside this release surface.Dependencies
No dependency, submodule, or release tag changes are included.