Skip to content
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

[orchagent] NVGRE Tunnel orchestration agent implementation #1953

Merged
merged 35 commits into from
Mar 15, 2022

Conversation

vadymhlushko-mlnx
Copy link
Contributor

@vadymhlushko-mlnx vadymhlushko-mlnx commented Oct 12, 2021

DEPENDS ON:
sonic-swss-common/pull/549

What I did
Implemented the NVGRE Tunnel orchestration agent according to the - SONiC NVGRE Tunnel HLD

Why I did it

How I verified it
Implemented VS test.

Details if related

@vadymhlushko-mlnx vadymhlushko-mlnx changed the title Nvgre tunnel NVGRE Tunnel orchestration agent implementation Oct 12, 2021
@caizhenghui-juniper
Copy link
Contributor

Is there no dstIP? how do we setup encap of traffic through the tunnel?

@liat-grozovik
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@vadymhlushko-mlnx vadymhlushko-mlnx marked this pull request as ready for review October 29, 2021 10:38
@vadymhlushko-mlnx vadymhlushko-mlnx changed the title NVGRE Tunnel orchestration agent implementation [orchagent] NVGRE Tunnel orchestration agent implementation Oct 29, 2021
@vadymhlushko-mlnx
Copy link
Contributor Author

/azpw run

@mssonicbld
Copy link
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@liat-grozovik
Copy link
Collaborator

@@kperumalbfn could you please help to review?
@vadymhlushko-mlnx please handle conflicts as soon as you can.

@kperumalbfn
Copy link
Contributor

@liat-grozovik @mickeyspiegel is reviewing NVGRE tunnel PRs

@vadymhlushko-mlnx
Copy link
Contributor Author

@mickeyspiegel, kind reminder, could you please help to review this PR

orchagent/nvgreorch.cpp Show resolved Hide resolved
orchagent/nvgreorch.h Show resolved Hide resolved
orchagent/nvgreorch.cpp Show resolved Hide resolved
Signed-off-by: Vadym Hlushko <[email protected]>
Signed-off-by: Vadym Hlushko <[email protected]>
Signed-off-by: Vadym Hlushko <[email protected]>
Signed-off-by: Vadym Hlushko <[email protected]>
Signed-off-by: Vadym Hlushko <[email protected]>
@vadymhlushko-mlnx
Copy link
Contributor Author

Is there no dstIP? how do we setup encap of traffic through the tunnel?

Currently, we add implementation only for the decap flow and it is L2 over L3 tunnel, so it should not be referenced by route objects. So at this point, you will be able to configure tunnel object and mapper entries for decap. This covers exactly the same use case as we have for L2 VXLAN, for example, please take a look at this test - test_vxlan_decap.py

@liat-grozovik
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@liat-grozovik
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@liat-grozovik
Copy link
Collaborator

@mickeyspiegel could you please review recent changes following your feedback? if not more comments we will merge this PR

@vadymhlushko-mlnx
Copy link
Contributor Author

/azpw run

@mssonicbld
Copy link
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@liat-grozovik
Copy link
Collaborator

/azp run Azure.sonic-swss

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@vadymhlushko-mlnx
Copy link
Contributor Author

/azpw run

@mssonicbld
Copy link
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@vadymhlushko-mlnx
Copy link
Contributor Author

/azpw run

@mssonicbld
Copy link
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@vadymhlushko-mlnx
Copy link
Contributor Author

vadymhlushko-mlnx commented Mar 8, 2022

@liat-grozovik
LGMT analysis failed not because of this PR.
LGTM analysis failed because it found minor (mostly code style) issues in already existing code in the sonic-swss submodule.

@liat-grozovik liat-grozovik merged commit 0294376 into sonic-net:master Mar 15, 2022
dprital pushed a commit to dprital/sonic-swss that referenced this pull request May 8, 2022
…t#1953)

- What I did
Implemented the NVGRE Tunnel orchestration agent according to the - SONiC NVGRE Tunnel HLD

- Why I did it
Part of the NVGRE feature support.

- How I verified it
Implemented VS test.

Signed-off-by: Vadym Hlushko <[email protected]>
preetham-singh pushed a commit to preetham-singh/sonic-swss that referenced this pull request Aug 6, 2022
…t#1953)

- What I did
Implemented the NVGRE Tunnel orchestration agent according to the - SONiC NVGRE Tunnel HLD

- Why I did it
Part of the NVGRE feature support.

- How I verified it
Implemented VS test.

Signed-off-by: Vadym Hlushko <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants