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

[Teamshow]: get platform info before parsing minigraph #30

Merged
merged 3 commits into from
Apr 11, 2017

Conversation

sihuihan88
Copy link
Contributor

No description provided.

Sihui Han added 2 commits April 7, 2017 23:53
Signed-off-by: Sihui Han <sihan@microsoft.com>
Signed-off-by: Sihui Han <sihan@microsoft.com>
@stcheng
Copy link
Contributor

stcheng commented Apr 8, 2017

hold this pull request before sonic-net/sonic-buildimage#489 is approved

@sihuihan88
Copy link
Contributor Author

Since we plan to add port channel status from database in teamshow, I think it also makes senses that we get the portchannel list from database directly at the same time. This helps us get rid of parsing the minigraph logic and keep the logic simple.
I would prefer to obtain portchannel list and status from database directly rather than parsing minigraph.

@stcheng
Copy link
Contributor

stcheng commented Apr 10, 2017

the reason is that it is possible that the port channels are probably not up or initialized due to some unknown reasons/bugs. that is why we prefer to load all the information from minigraph so that to make sure that the desired state could be shown.

@sihuihan88
Copy link
Contributor Author

Just curious, where the database gets the port channel info? It also shows some port channel are down. I was thinking database will check minigraph or somewhere first to get the port channel list and then determine the status of each.

@stcheng
Copy link
Contributor

stcheng commented Apr 10, 2017

the database get the port channel information when the teamsyncd gets the notification about the initialization of team instances in docker-teamd, and then the swss gets the message from teamsyncd. thus there will be several steps before the database finally gets the information.

in this case, either way makes logical sense, it just depends on the requirements of this utility by users. if users want to know the status of the port channels defined in the minigraph, then we need to read the minigraph. if the user only cares about the current status of the team instances on the box, then we will only need to read the database.

thus it is the users of this utility that decide which approach to choose.

@sihuihan88
Copy link
Contributor Author

Got it. I understand it much better now. Thanks!

@stcheng stcheng merged commit bd6cf5d into sonic-net:master Apr 11, 2017
@sihuihan88 sihuihan88 deleted the teamshow branch April 11, 2017 22:51
praveen-li pushed a commit to praveen-li/sonic-utilities that referenced this pull request Jun 30, 2020
…onfig. (sonic-net#30)

Not changing variable name to avoid more changes in code.

Signed-off-by: Praveen Chaudhary pchaudhary@linkedin.com
vdahiya12 pushed a commit to vdahiya12/sonic-utilities that referenced this pull request Jul 23, 2021
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.

2 participants