[CI] fix a5 multi resource

[xqchen7]

What this PR does / why we need it?

adapt resource got a5 multi nightly,add openlibing.secret parameter to enable a5 multi nightly run

Does this PR introduce any user-facing change?

eable developer run a5 multi nightly

How was this patch tested?

• vLLM main: vllm-project/vllm@b2f6858

[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 introduces flexibility into the CI pipeline's resource allocation configuration. By parameterizing the NPU resource name in the LWS job template, the system can now support different hardware environments, specifically enabling A5 multi-node nightly testing workflows.

Highlights

• Resource Configuration Flexibility: Updated the LWS configuration template to use a dynamic variable for the NPU resource name instead of a hardcoded value.
• CI Compatibility: Enabled support for A5 multi-node nightly testing by allowing configurable resource naming.

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

Suggested PR Title:

[Test][Misc] Parameterize NPU resource name in LWS template

Suggested PR Summary:

### What this PR does / why we need it?
This PR parameterizes the NPU resource name in the LWS template (`lws.yaml.jinja2`) using the `npu_resource_name` variable, defaulting to `huawei.com/ascend-1980`. This allows for more flexible configuration of NPU resources across different environments.

Feedback: The Jinja2 `default` filter should be updated to use `default(..., true)` to ensure that empty strings correctly fall back to the default values.

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

### How was this patch tested?
No tests were provided in this PR.

[gemini-code-assist]

In Jinja2, the default filter only falls back to the default value if the variable is undefined. If npu_resource_name or npu_per_node are defined but passed as empty strings (e.g., ""), they will evaluate to empty strings, resulting in invalid YAML (e.g., an empty key or missing value under limits:). Passing true as the second argument to default ensures they fall back to their default values for empty strings or other falsy values.

                {{ npu_resource_name | default("huawei.com/ascend-1980", true) }}: {{ npu_per_node | default("16", true) }}

[gemini-code-assist]

In Jinja2, the default filter only falls back to the default value if the variable is undefined. If npu_resource_name or npu_per_node are defined but passed as empty strings (e.g., ""), they will evaluate to empty strings, resulting in invalid YAML (e.g., an empty key or missing value under requests:). Passing true as the second argument to default ensures they fall back to their default values for empty strings or other falsy values.

                {{ npu_resource_name | default("huawei.com/ascend-1980", true) }}: {{ npu_per_node | default("16", true) }}

[gemini-code-assist]

In Jinja2, the default filter only falls back to the default value if the variable is undefined. If npu_resource_name or npu_per_node are defined but passed as empty strings (e.g., ""), they will evaluate to empty strings, resulting in invalid YAML (e.g., an empty key or missing value under limits:). Passing true as the second argument to default ensures they fall back to their default values for empty strings or other falsy values.

                {{ npu_resource_name | default("huawei.com/ascend-1980", true) }}: {{ npu_per_node | default("16", true) }}

[gemini-code-assist]

In Jinja2, the default filter only falls back to the default value if the variable is undefined. If npu_resource_name or npu_per_node are defined but passed as empty strings (e.g., ""), they will evaluate to empty strings, resulting in invalid YAML (e.g., an empty key or missing value under requests:). Passing true as the second argument to default ensures they fall back to their default values for empty strings or other falsy values.

                {{ npu_resource_name | default("huawei.com/ascend-1980", true) }}: {{ npu_per_node | default("16", true) }}

[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.

[lijiahang226]

Please add more description.

[lijiahang226]

LGTM

[zhangxinyuehfad]

/revert
[Bot]: revert completed successfully. New PR created: #16387