-
Notifications
You must be signed in to change notification settings - Fork 532
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VNET/VXLAN changes #643
VNET/VXLAN changes #643
Conversation
retest this please |
retest this please |
@prsunny , can you rebase your pr and do a test again? I fixed a few things on the vstest. |
retest this please |
is the vs test in this PR or a new PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
refactor test cases to make it more readable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as comments
I see two functions with the same name, but with different signatures. If you need both functions I'd suggest to change names, otherwise you'd better to remove unused one.
vs
|
…ure to adopt to new changes
@pavel-shirshov , addressed the comment by combining the two APIs. Initially thought to leave the existing function unmodified. There are new changes to the PR based on VNET Table flow redesign. The new flow is updated in the HLD document. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you updated Application DB schema with VXLAN_TUNNEL_MAP in swss-schema.md?
…t#643) * [syncd] ARM32 bit fixes, for 64bit printf format specifier. Signed-off-by: Rajkumar Pennadam Ramamoorthy <rpennadamram@marvell.com> * [syncd] ARM32 bit fixes, for 64bit printf format specifier. Signed-off-by: Rajkumar Pennadam Ramamoorthy <rpennadamram@marvell.com>
What I did
Modified Vxlanorch to support VNet peering feature.
Introduced the following:
Why I did it
Support VNet peering using Vxlan (VNI <-> VRF)
How I verified it
Verified by VS test and checking the ASIC DB for intended SAI tables
Details if related
Design Document:
https://github.com/prsunny/SONiC/blob/gh-pages/doc/vxlan/Vxlan_hld.md
Related PR
#632
Pending: