Skip to content

gRIBI WCMP Group Resizing and Weight Changes - #5992

Merged
2 commits merged into
mainfrom
unknown repository
Sep 7, 2026
Merged

2 commits merged into
mainfrom
unknown repository

Conversation

@ghost

@ghost ghost commented Sep 5, 2026

Copy link
Copy Markdown

System Test Plan see for more info: b/540867412

  • Objective: Test the switch's ability to handle dynamic changes to Weighted Cost Multi-Path (WCMP) groups programmed via gRIBI. This simulates Orion adjusting tunnel allocations. Specifically validates gRIBI Modify (REPLACE) operations to adjust weights of NextHops within an active NextHopGroup.
    • Interfaces Used: gRIBI, gNMI
    • Expected Outcome Summary:
      • Verify initial traffic distribution across WCMP members matches the weights.
      • Adding, removing, or changing weights of NextHops within the NextHopGroup results in traffic distribution adjusting accordingly.
      • All changes are hitless for unaffected flows.
      • gNMI AFT telemetry via /network-instances/network-instance/afts/next-hop-groups/next-hop-group/state/ reflects the NHG changes.

@ghost
ghost requested review from a team as code owners September 5, 2026 15:59
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! 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 a new system test plan (TE-3.10) designed to verify the switch's capability to dynamically manage WCMP groups using gRIBI. The changes include the necessary documentation and metadata to support this test, which focuses on hitless weight adjustments and group resizing while maintaining traffic integrity for background flows.

Highlights

  • New Test Case Implementation: Added a new test suite, TE-3.10, to validate dynamic Weighted Cost Multi-Path (WCMP) group resizing and weight modifications via gRIBI.
  • Test Coverage: The new test covers weight updates, dynamic addition/removal of NextHops, and negative test cases to ensure robust gRIBI operation handling.
  • Test Registry Update: Registered the new TE-3.10 test case in the global test registry to ensure inclusion in the automated test pipeline.
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 gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new test plan (TE-3.10) for validating gRIBI WCMP group resizing and dynamic weight changes, including the README test plan, metadata, and registry entry. The review feedback correctly points out that the test plan uses the disallowed private IPv4 range 10.0.0.0/16, which violates the repository's network assignment guidelines. It is recommended to update these references to use allowed IP blocks such as 198.18.0.0/16.

Comment thread feature/gribi/otg_tests/dynamic_wcmp_group_resizing_test/README.md
Comment thread feature/gribi/otg_tests/dynamic_wcmp_group_resizing_test/README.md
@ghost ghost added the systemTest Systematic Iron gate test plan label Sep 7, 2026

@AmrNJ AmrNJ left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@ghost
ghost merged commit 5f47e6f into openconfig:main Sep 7, 2026
23 checks passed
@ghost
ghost deleted the dynamic_wcmp_group_resizing branch September 7, 2026 17:26
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

systemTest Systematic Iron gate test plan

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants