Add vip_v4 and vip_v6 to DPU DASH_HA_SCOPE_TABLE#96
Merged
r12f merged 1 commit intosonic-net:masterfrom Aug 5, 2025
Merged
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
r12f
approved these changes
Aug 5, 2025
|
Cherry-pick PR to msft-202506: Azure/sonic-dash-ha.msft#15 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
why
There is a mismatch between DASH_HA_SCOPE_TABLE in DPU sonic-db and SAI HA_SCOPE definition. vip_v4 and vip_v6 exist in the latter but not in DASH_HA_SCOPE_TABLE. DashHaOrch has to implement complicated logic to get vip_v4 and vip_v6 from DASH_HA_SET_TABLE. To simplify DashHaOrch design, vip_v4 and vip_v6 are added to DASH_HA_SCOPE_TABLE. Accordingly, hamgrd needs to adapt to it.
what this PR does