Skip to content

e2e: remove unused blue VNI from iBGP test#404

Open
andreaskaris wants to merge 1 commit into
openperouter:mainfrom
andreaskaris:cleanup-ibgp
Open

e2e: remove unused blue VNI from iBGP test#404
andreaskaris wants to merge 1 commit into
openperouter:mainfrom
andreaskaris:cleanup-ibgp

Conversation

@andreaskaris
Copy link
Copy Markdown
Contributor

Remove the "blue" L3VNI definition and all its references from the iBGP
E2E test, which only validates connectivity against the red host. This
also removes dead code for IPv6 local CIDR selection, since the test
hardcodes IPv4.

Is this a BUG FIX or a FEATURE ?:

/kind cleanup

What this PR does / why we need it:
Remove the "blue" L3VNI definition and all its references from the iBGP
E2E test, which only validates connectivity against the red host. This
also removes dead code for IPv6 local CIDR selection, since the test
hardcodes IPv4.

Special notes for your reviewer:
N/A

Release note:

Cleanup of iBGP E2E test

@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 performs a cleanup of the iBGP E2E test suite by removing redundant configuration objects and associated logic that were no longer required for validating connectivity. By focusing the test solely on the 'red' host and removing the 'blue' VNI, the codebase is simplified and dead logic for IPv6 handling is eliminated.

Highlights

  • Test Cleanup: Removed the unused 'blue' L3VNI definition and all associated references from the iBGP E2E test suite.
  • Code Simplification: Removed dead code related to IPv6 local CIDR selection, as the test exclusively utilizes IPv4.
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.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

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 simplifies the EVPN routes e2e tests by removing the 'blue' VNI configuration and its associated test logic, focusing the test suite on the 'red' hosts. Additionally, it refactors CIDR handling by removing unused IPv6 logic and reorders imports. Feedback was provided regarding a redundant type cast in the FRR configuration assignment that should be removed to improve code clarity.

Comment thread e2etests/tests/evpn_routes.go Outdated
Remove the "blue" L3VNI definition and all its references from the iBGP
E2E test, which only validates connectivity against the red host. This
also removes dead code for IPv6 local CIDR selection, since the test
hardcodes IPv4.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant