feat: update gpt-oss 120b model recipe #3143 #3454

[biswapanda]

Overview:

Cherry pick

• feat: update gpt-oss 120b model recipe #3143
• feat: use generic image and use single node for oss-gpt-120b recipe #3454

closes: DEP-410

Details:

Where should the reviewer start?

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• closes GitHub issue: #xxx

Summary by CodeRabbit

• New Features

  • Added CLI controls for request synthesis (min/max input/output lengths).
  • Container run script now supports --network modes and -p port mappings.
  • Introduced GPT-OSS-120B deployment recipe and artifacts.

• Bug Fixes

  • More robust streaming completion handling and finish_reason standardization.

• Improvements

  • Increased default KV Router snapshot threshold for better scalability.
  • Upgraded default images across backends to 0.5.1; Helm charts bumped.
  • Enhanced NATS stream readiness and purge behavior.
  • Refined Docker build flows (RDMA reinstall, TRT-LLM setup) and benchmarks packaging.

• Documentation

  • Extensive updates: image/tag references, runtime guides, ECS/Fargate steps, networking guidance, and example renames.

[coderabbitai]

Caution

Review failed

Failed to post review comments

Pre-merge checks

❌ Failed checks (3 warnings)

Check name	Status	Explanation	Resolution
Title Check	⚠️ Warning	The title only references updating the GPT-OSS 120B recipe but the changeset spans extensive container image bumps to v0.5.1, new CLI flags, Dockerfile overhaul, documentation updates, and configuration tweaks across many components; it fails to summarize the primary scope of the patch accurately and is misleadingly narrow.	Please revise the title to reflect the full scope of the changes, for example “chore: bump container images to v0.5.1 across components and cherry-pick GPT-OSS 120B recipe updates,” or split this broad changeset into focused PRs.
Description Check	⚠️ Warning	The description includes the template headings but leaves the Details and Where should the reviewer start sections empty and uses a placeholder issue number, so it provides no substantive summary of the actual changes or guidance on key files to review.	Complete the Details section with an overview of the modifications made (e.g., image tag updates, CLI enhancements, Dockerfile changes, recipe additions), list the primary files or directories reviewers should examine, and update the Related Issues section with the correct issue references.
Docstring Coverage	⚠️ Warning	Docstring coverage is 30.43% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.