Skip to content

[action] [PR:4615] [EVPN-MH] Integrate EVPN-MH with existing modules and add tests#239

Merged
mssonicbld merged 1 commit into
Azure:202606from
mssonicbld:cherry/msft-202606/4615
Jun 18, 2026
Merged

[action] [PR:4615] [EVPN-MH] Integrate EVPN-MH with existing modules and add tests#239
mssonicbld merged 1 commit into
Azure:202606from
mssonicbld:cherry/msft-202606/4615

Conversation

@mssonicbld

Copy link
Copy Markdown
Collaborator

Why I did it

This is part 2/2 of splitting the original EVPN-MH PR (#4262) into reviewable pieces.
Part 1 (#4608) landed the standalone EVPN-MH code (new orchs and headers added without touching existing files).
This PR integrates EVPN-MH with the existing modules (NeighOrch, FdbOrch, VxlanOrch, RouteOrch, MuxOrch, p4orch, fpmsyncd, etc.) and adds the mock/VS tests that exercise both the standalone and integration paths.

The test-infra prerequisites required to land these tests were merged separately as #4599.

How I did it

  • Commit 1 — Integrate EVPN-MH with existing modules: wires the standalone EVPN-MH orchs (added in #4608) into the existing data plane (FDB / neighbor / next-hop / VXLAN / mux / p4orch / fpmsyncd).
  • Commit 2 — Add EVPN-MH tests and stabilization updates: adds new mock_tests (neighorch, vxlanorch, p4orch fake/mock helpers) and VS tests (test_sag.py, EVPN FDB/L3 VXLAN updates) and a few small stabilization tweaks needed for the new tests.

How to verify it

  • make the swss debs and run mock_tests; test_sag.py and the new EVPN-MH cases under tests/mock_tests/{neighorch,vxlanorch}_ut.cpp should pass.
  • Full VS suite locally and in CI.

Which release branch to backport (provide reason below if selected)

  • 202012
  • 202205
  • 202211
  • 202305
  • 202311
  • 202405
  • 202411
  • 202505
  • 202511

Description for the changelog

[EVPN-MH] Integrate EVPN-MH with existing modules and add unit/VS tests.

Link to config_db schema for YANG module changes

N/A (YANG changes are tracked separately in sonic-buildimage PR #27543.)

Signed-off-by: Sonic Build Admin sonicbld@microsoft.com

A picture of a cute animal (not mandatory but encouraged)

#### Why I did it

This is part 2/2 of splitting the original EVPN-MH PR (#4262) into reviewable pieces.
Part 1 ([#4608](sonic-net/sonic-swss#4608)) landed the standalone EVPN-MH code (new orchs and headers added without touching existing files).
This PR integrates EVPN-MH with the existing modules (NeighOrch, FdbOrch, VxlanOrch, RouteOrch, MuxOrch, p4orch, fpmsyncd, etc.) and adds the mock/VS tests that exercise both the standalone and integration paths.

The test-infra prerequisites required to land these tests were merged separately as #4599.

#### How I did it

- Commit 1 — *Integrate EVPN-MH with existing modules*: wires the standalone EVPN-MH orchs (added in #4608) into the existing data plane (FDB / neighbor / next-hop / VXLAN / mux / p4orch / fpmsyncd).
- Commit 2 — *Add EVPN-MH tests and stabilization updates*: adds new mock_tests (neighorch, vxlanorch, p4orch fake/mock helpers) and VS tests (`test_sag.py`, EVPN FDB/L3 VXLAN updates) and a few small stabilization tweaks needed for the new tests.

#### How to verify it

- `make` the swss debs and run mock_tests; `test_sag.py` and the new EVPN-MH cases under `tests/mock_tests/{neighorch,vxlanorch}_ut.cpp` should pass.
- Full VS suite locally and in CI.

#### Which release branch to backport (provide reason below if selected)

- [ ] 202012
- [ ] 202205
- [ ] 202211
- [ ] 202305
- [ ] 202311
- [ ] 202405
- [ ] 202411
- [ ] 202505
- [ ] 202511

#### Description for the changelog

[EVPN-MH] Integrate EVPN-MH with existing modules and add unit/VS tests.

#### Link to config_db schema for YANG module changes

N/A (YANG changes are tracked separately in sonic-buildimage PR #27543.)

Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com>

#### A picture of a cute animal (not mandatory but encouraged)
@mssonicbld

Copy link
Copy Markdown
Collaborator Author

Original PR: sonic-net/sonic-swss#4615

@mssonicbld

Copy link
Copy Markdown
Collaborator Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

Comment thread run-gtest-suite.py
target_nofile = hard_nofile
if target_nofile > soft_nofile:
resource.setrlimit(resource.RLIMIT_NOFILE, (target_nofile, hard_nofile))
except (OSError, ValueError):
@mssonicbld mssonicbld merged commit b70596c into Azure:202606 Jun 18, 2026
6 checks passed
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.

2 participants