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

[Mellanox]New platform api -- chassis part #3082

Merged
merged 11 commits into from
Jul 4, 2019
Merged

[Mellanox]New platform api -- chassis part #3082

merged 11 commits into from
Jul 4, 2019

Conversation

stephenxs
Copy link
Collaborator

@stephenxs stephenxs commented Jun 25, 2019

- What I did
Implement new platform API, chassis part.

- How I did it
make use of:

  1. common/private tools available on linux to retrieve components' versions.
  2. hw-management to retrieve reboot cause and eeprom information.

- How to verify it
use a test command to drive chassis class in order to check whether it works correctly.

- Description for the changelog
[Mellanox]New platform api -- chassis part

- A picture of a cute animal (not mandatory but encouraged)

@stephenxs stephenxs marked this pull request as ready for review June 25, 2019 10:36
…the reboot causing by user command can be identified"

Since the only hardware-causing reboot should be handled by get_reboot_cause and the logic of handling reboot cause is about to move to the host side, no need to mount this dir to pmon docker.
This reverts commit 3feb968.
2. adjust log output by using sonic_daemon_base.daemon_base.Logger.
3. remove the logic of verifying /host/reboot-cause/ files.
4. fix typo.
Copy link
Contributor

@jleveque jleveque left a comment

Choose a reason for hiding this comment

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

FYI, Please make changes to this PR to adapt to the changes made to sonic_platform_base in the following PR: sonic-net/sonic-platform-common#34

@yxieca
Copy link
Contributor

yxieca commented Jul 10, 2019

Unable to cherry-pick to 201811 branch directly due to merge conflicts. @stephenxs can you create another PR against 201811 branch or suggest dependent PR to cherry-pick?

@stephenxs
Copy link
Collaborator Author

stephenxs commented Jul 11, 2019

Unable to cherry-pick to 201811 branch directly due to merge conflicts. @stephenxs can you create another PR against 201811 branch or suggest dependent PR to cherry-pick?

on 201811, some other modules are required to be updated in order to support reboot-cause.
I'll discuss with our people and find the solution.

yxieca added a commit to yxieca/sonic-buildimage that referenced this pull request Dec 21, 2023
Old format: version_a_b_c
New format: version_<branch>_<nn>

sonic-utilities:
* fba4bf0b 2023-12-21 | [202311][db_migrator] add db migrator version space for 202305/202311 branch (sonic-net#3082) (HEAD -> 202311, github/202311) [Ying Xie]

Signed-off-by: Ying Xie <ying.xie@microsoft.com>
yxieca added a commit that referenced this pull request Dec 22, 2023
…#17600)

Old format: version_a_b_c
New format: version_<branch>_<nn>

sonic-utilities:
* fba4bf0b 2023-12-21 | [202311][db_migrator] add db migrator version space for 202305/202311 branch (#3082) (HEAD -> 202311, github/202311) [Ying Xie]

Signed-off-by: Ying Xie <ying.xie@microsoft.com>
mssonicbld added a commit that referenced this pull request Mar 22, 2024
…lly (#18436)

#### Why I did it
src/sonic-swss
```
* 71e7b37c - (HEAD -> 202311, origin/202311) [202311][muxorch] Fixing cache bug in updateRoute logic and Fixing bug with multiple routes pointing to nhg (#3082) (11 hours ago) [Nikola Dancejic]
```
#### How I did it
#### How to verify it
#### Description for the changelog
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.

5 participants