-
Notifications
You must be signed in to change notification settings - Fork 659
docs: add a doc for framework lib versions #3572
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
/ok to test 51d3cb6 |
51d3cb6 to
a76a621
Compare
WalkthroughAdded FRAMEWORK_VERSIONS.md documenting core dependencies, versions, base images, framework configurations, dependency management artifacts, notes on variability, and container documentation references for NVIDIA Dynamo. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
Pre-merge checks❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
/ok to test a76a621 |
WalkthroughAdds a new documentation file, FRAMEWORK_VERSIONS.md, detailing core frameworks and versions, base CUDA images, framework-specific configurations (vLLM, TensorRT-LLM, SGLang), dependency management locations (build scripts, wheels, requirements), notes on version usage, and container documentation references. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
Pre-merge checks❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
FRAMEWORK_VERSIONS.md(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Build and Test - dynamo
|
Any way we can generate this automatically? vs. having to manually update? I think that would make our lives easier and could be part of the release process. I think @dagil-nvidia worked on something tangentially related. |
|
I also think some of this should be covered in a release / support matrix that is floating around somewhere. |
|
See - Line 7 in d4ff6f0
|
Created automated generator for framework versions documentation: Generator Script (.github/scripts/dependency-extraction/generate_framework_versions.py): - Dynamically generates FRAMEWORK_VERSIONS.md from dependency CSV - Shows both latest (main) and last release versions side-by-side - Auto-detects most recent release snapshot for comparison - Highlights version differences between main and release - Extracts critical dependencies, base images, and framework configs - Organizes by component (vLLM, TensorRT-LLM, SGLang) Key Features: - Auto-generated from dependency_versions_latest.csv (262 total deps) - Displays 55 critical dependencies with versions - Shows 21 base/runtime images with tags - Compares latest vs release when available - Includes statistics (total deps, critical count, NVIDIA products) - Links to dependency reports and container documentation Workflow Integration: - Runs nightly after dependency extraction - Generates FRAMEWORK_VERSIONS.md in repo root - Included in automated PR when dependency changes detected - Provides easy reference for framework versions This addresses PR #3572 request for framework versions doc, but implements it dynamically instead of manually maintained. Benefits over manual approach: - Always up-to-date (runs nightly) - Automatically detects version changes - Shows version differences (latest vs release) - Sourced from single source of truth (dependency CSV) - No risk of manual updates being stale Files Generated: - FRAMEWORK_VERSIONS.md (438 lines, auto-generated) - Example also saved to ~/Desktop/FRAMEWORK_VERSIONS.md Related: #DYN-1235, PR #3572 Signed-off-by: Dan Gil <[email protected]>
|
To match other docs, would recommend the doc be named framework_versions.md. |
Implements comprehensive dependency tracking across all Dynamo components with full modularization, unit tests, and automated documentation generation. Core System: - Automated extraction from 10 source types - Nightly workflow with smart PR creation - Release snapshot system - Version discrepancy detection - Automated failure monitoring Modular Architecture (1,900+ lines extracted): - constants.py: Centralized hardcoded values - utils/: formatting, comparison, URL generation - extractors/: Base class + Python extractor (pattern for future) - tests/: 145+ unit tests (@pytest.mark.weekly) Documentation: - framework_versions.md: Auto-generated framework versions (101 lines) - .github/reports/README.md: CSV structure and workflows - .github/scripts/dependency-extraction/README.md: Architecture (290 lines) Workflows: - Unified dependency-extraction.yml (nightly + release modes) - Composite action for reusable setup - Auto-creates GitHub issues on failure Files (22 total): - 18 new files (scripts, config, docs, tests, modules) - 1 modified (.gitignore) - 1 generated (dependency_versions_latest.csv) - 1 auto-generated (framework_versions.md) Testing: - 145+ unit tests with proper pytest markers - Tests run weekly (non-blocking) - Coverage for formatting and Python extractor Addresses: - DYN-1235: Automated dependency tracking - PR #3572: Framework versions doc (but auto-generated) - Review feedback from @nv-anants (all 6 comments) Supersedes: PR #3547 (had merge conflicts and unrelated files) Signed-off-by: Dan Gil <[email protected]>
Overview:
add a doc for framework lib versions
Details:
Where should the reviewer start?
Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)
Summary by CodeRabbit