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

[WR]: Add reconciliation logic for teamsyncd #725

Merged
merged 20 commits into from
Dec 23, 2018

Conversation

pavel-shirshov
Copy link
Contributor

What I did
Added reconciliation logic for teamsyncd.

Why I did it
To avoid sending wrong updates to swss from teamsyncd.

How I verified it
Install changes to teamd docker. Restart dut in cold mode, then restart dut in wr mode.

Details if related

teamsyncd/teamsyncd.cpp Outdated Show resolved Hide resolved
teamsyncd/teamsyncd.cpp Outdated Show resolved Hide resolved
@lguohan lguohan requested review from qiluo-msft and stcheng December 7, 2018 09:08
teamsyncd/teamsyncd.cpp Outdated Show resolved Hide resolved
teamsyncd/teamsync.cpp Outdated Show resolved Hide resolved
teamsyncd/teamsyncd.cpp Outdated Show resolved Hide resolved
teamsyncd/teamsyncd.cpp Outdated Show resolved Hide resolved
Copy link
Contributor

@qiluo-msft qiluo-msft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comments

Copy link
Contributor

@jipanyang jipanyang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pavel-shirshov
Copy link
Contributor Author

The schema was added

Copy link
Contributor

@jipanyang jipanyang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change itself looks good to me, but please make sure the VS test cases pass.

@@ -11,19 +11,23 @@
#include "netmsg.h"
#include <team.h>

// seconds
const uint32_t DEFAULT_WR_PENDING_TIMEOUT = 70;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would like to understand the logic behind this default value of 70 seconds here.

With lacp slow mode, 30 second interval * 3 times = 90 seconds, all the teamd related processing has to be within that range from teamd shutdown to the lacp connection reestablished.
During warm reboot, are you expecting it will take about 20 seconds from teamd shutdown to teamd restarted, then from teamd started to lacp connected, it will take x*10 seconds?

@qiluo-msft qiluo-msft merged commit 025268a into sonic-net:master Dec 23, 2018
EdenGri pushed a commit to EdenGri/sonic-swss that referenced this pull request Feb 28, 2022
oleksandrivantsiv pushed a commit to oleksandrivantsiv/sonic-swss that referenced this pull request Mar 1, 2023
Changes include SAI support for voq neighbor. VOQ neighbor requires an
additional attribute to set the encap index. For local neighbors the
encap index iis assigned by SAI, if not imposed. For remote neighbors,
the encap index is required to be supplised by the upper layer. The
changes validate these conditions for remote neighbors.
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.

3 participants