Add a yang model for the new "Logger" table in the CONFIG DB#12067
Merged
liat-grozovik merged 10 commits intosonic-net:masterfrom Oct 31, 2022
Merged
Add a yang model for the new "Logger" table in the CONFIG DB#12067liat-grozovik merged 10 commits intosonic-net:masterfrom
liat-grozovik merged 10 commits intosonic-net:masterfrom
Conversation
dgsudharsan
approved these changes
Sep 29, 2022
praveen-li
reviewed
Sep 29, 2022
Contributor
Author
|
The tests that failed are: |
Contributor
Author
|
/azpw run |
Collaborator
|
/AzurePipelines run |
|
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list. |
Contributor
Author
|
/azpw run Azure.sonic-buildimage |
Collaborator
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
Could you refine your PR title? |
praveen-li
reviewed
Oct 6, 2022
ganglyu
approved these changes
Oct 6, 2022
EdenGri
changed the title
qiluo-msft
approved these changes
Oct 9, 2022
EdenGri
force-pushed
the
persistent_loglevel
branch
from
b0d9337 to
4dad806
Compare
Contributor
Author
|
The test that failed is: |
Contributor
Author
|
/azpw run Azure.sonic-buildimage |
Collaborator
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
failed in the test: configlet/test_add_rack.py::test_add_rack |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
/azp run Azure.sonic-buildimage |
|
Commenter does not have sufficient privileges for PR 12067 in repo sonic-net/sonic-buildimage |
Contributor
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…er table, update the sample_config_db.json to include logger table
EdenGri
force-pushed
the
persistent_loglevel
branch
from
4dad806 to
74ae9fa
Compare
Contributor
Author
|
/azp run Azure.sonic-buildimage |
|
Commenter does not have sufficient privileges for PR 12067 in repo sonic-net/sonic-buildimage |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This was referenced Oct 28, 2022
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
7 tasks
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
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.
Signed-off-by: EdenGri [email protected]
This PR should be merged together with the following PRs as there is dependency between them:
Why I did it
Add the ability to the user to save the loglevel and make it persistent to reboot.
How I did it
Move the logger tables from the LOGLEVEL DB to the CONFIG DB. Add new yang model to verify the new config schema.
How to verify it
Which release branch to backport (provide reason below if selected)
Description for the changelog
Ensure to add label/tag for the feature raised. example - PR#2174 where, Generic Config and Update feature has been labelled as GCU.
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)