[Mellanox] CMIS-Host-Management JSON's Rearrangement #24
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… and 5600. Created symbolic links to redirect other SKUs to these updated files.
|
What about pmon_daemon_control.json? |
DavidZagury
approved these changes
Aug 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why I did it
There are two JSON files related to the CMIS host management feature: media_settings.json and optics_si_settings.json. Multiple copies of these JSON files exist across different SKUs of the 4700 and 5600, which can cause confusion and make tracking difficult. The goal is to create a unified version of each JSON file and redirect all other JSON files to these unified versions.
Work item tracking
How I did it
I updated media_settings.json and optics_si_settings.json for SKUs 4700 and 5600. Additionally, I created symbolic links to redirect other SKUs to these updated files.
How to verify it
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)