[Cherry-pick][releases/v0.23.0][Doc][Misc] Add deployment reference notice for GLM-5 (from #12958)

[vllm-ascend-ci]

Cherry-pick of PR #12958 onto releases/v0.23.0.

Original PR: #12958
Original author: @wangzhishenghw

---

What this PR does / why we need it?

This PR adds a notice and a reference link to Chapter 5 (Online Service Deployment) in the GLM-5 tutorial. This helps users find complete startup commands and parameter descriptions, and reminds them to configure max-model-len and max-num-seqs according to their actual usage scenarios.

Does this PR introduce any user-facing change?

No, this is a documentation-only update.

How was this patch tested?

Documentation changes only, verified markdown rendering.

• vLLM version: v0.23.0
• vLLM main: vllm-project/vllm@ee0da84

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs a cherry-pick of documentation improvements from the main branch to the v0.23.0 release branch. The changes enhance the GLM-5 model tutorial by providing clearer guidance on deployment configurations and linking to relevant service deployment documentation.

Highlights

• Documentation Update: Added a reference link to Chapter 5 (Online Service Deployment) in the GLM-5 tutorial to assist users with startup commands.
• Configuration Guidance: Included a notice advising users to configure 'max-model-len' and 'max-num-seqs' based on their specific deployment scenarios.

New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the GLM-5 model tutorial documentation by adding a notice and a reference link to Chapter 5 (Online Service Deployment) to guide users on configuring 'max-model-len' and 'max-num-seqs' based on their usage scenarios. The reviewer feedback correctly points out that the PR title and summary do not conform to the repository's style guide and provides a compliant suggestion.

[gemini-code-assist]

The Pull Request title does not strictly follow the repository's Pull Request Summary Style Guide. The title should follow the format [Branch][Module][Action] Pull Request Title without extra prefixes like [Cherry-pick]. Below are the suggested PR Title and Summary formatted according to the style guide rules.

Suggested PR Title:

[releases/v0.23.0][Doc][Misc] Add deployment reference notice for GLM-5 (from #12958)

Suggested PR Summary:

### What this PR does / why we need it?

This PR adds a notice and a reference link to Chapter 5 (Online Service Deployment) in the GLM-5 tutorial. This helps users find complete startup commands and parameter descriptions, and reminds them to configure `max-model-len` and `max-num-seqs` according to their actual usage scenarios.

Cherry-pick of PR #12958 onto `releases/v0.23.0`.

### Does this PR introduce _any_ user-facing change?

No, this is a documentation-only update.

### How was this patch tested?

Documentation changes only, verified markdown rendering.

References

1. The Pull Request title must follow the format [Branch][Module][Action] Pull Request Title. The branch name where the PR is based should be the first prefix, and extra prefixes like [Cherry-pick] should be avoided. ^(link)

[github-actions]

👋 Hi! Thank you for contributing to the vLLM Ascend project. The following points will speed up your PR merge:‌‌

• A PR should do only one thing, smaller PRs enable faster reviews.
• Every PR should include unit tests and end-to-end tests ‌to ensure it works and is not broken by other future PRs.
• Write the commit message by fulfilling the PR description to help reviewer and future developers understand.

If CI fails, you can run linting and testing checks locally according Contributing and Testing.