-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Event and alarm management #17949
Event and alarm management #17949
Conversation
remove ack, noack from sonic-common-event yang.
@@ -0,0 +1,134 @@ | |||
module sonic-event { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you add a code to call this event from one of the App to showcase the usage?
@@ -0,0 +1,54 @@ | |||
#ifndef __EVENTCONSUME_H__ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like to see the existing event infra and this new changes work together in the unit test.
For example, if there is a BGP event, how does it get saved in the EVENT_DB.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
UT code added with this PR.
"id" : 19, | ||
"separator": "|", | ||
"instance" : "redis" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This a new redis DB instance addition. Have few queries:
- is there a max limit of redis DB instances that can be spawned and maintained on a given SONiC instance?
- If so, was it ensured that its within limits and no impact to the overall system bring-up and working in steady state?
- Is this a global database i.e. only a single instance of it would be spawned on the system in global namespace? or would it be one per ASIC/NPU namespace? Where is that determined/specified in this changeset?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Currently the max limit is set at 100 logical instances. /etc/redis/redis.conf
- This is within the global database. (redis instance.)
/azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/AzurePipelines run Azure.sonic-buildimage |
Commenter does not have sufficient privileges for PR 17949 in repo sonic-net/sonic-buildimage |
/azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
Set eventdb testcases as separate test binary. Skip testcase execution if DB connection failure.
@bmridul @shyam77git @qiluo-msft Please review this PR. |
need more reviews |
@reviewers, can you please help to review this PR? Thanks. |
@leeprecy please help review |
@zhangyanzhao Can we merge this PR? or we need more approval? |
@lguohan @qiluo-msft @adyeung Can you review and merge the pull request? |
@Praveen-Brcm pls help review and merge |
@bhaveshdell , PR validation is too old. It run on May. Now it breaks vs build. LINK
|
This reverts commit 10f0fe8.
@liushilongbuaa How can I commit the fix for the failure? Is the PR reverted? |
@bhaveshdell your PR has been reverted as @liushilongbuaa pointed out. I created a reversion of reversion PR #20064 , I suggest let's watch this PR build and test. Once the issue surfaced again, you can add more changed to 20064 to address the issue. Or you can create another PR, with your original change, plus change addressing the issue. |
This reverts commit 93f3cad.
This reverts commit 93f3cad.
This reverts commit 93f3cad.
* Support for event persistence in redis-db. * Updates * Updates including fix to eventdb in test enviroment. * Add sonic yang to model event and alarm table. remove ack, noack from sonic-common-event yang. * Add event/alarm persistence related testscases * Remove file eventdb_ut.cpp. * Updates to eventdb testsuite. * Revert changes to existing eventd UT. Set eventdb testcases as separate test binary. Skip testcase execution if DB connection failure. * Commit test related config files.
This reverts commit 10f0fe8.
Why I did it
This PR contains code changes for providing extension to the Event Framework as specified in the sonic-net/SONiC#1409
How I did it
Followed design specified in sonic-net/SONiC#1409.
How to verify it
Unit tests added.
A picture of a cute animal (not mandatory but encouraged)