-
Notifications
You must be signed in to change notification settings - Fork 539
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
Add support for fabric monitor daemon (swss part). #2920
Add support for fabric monitor daemon (swss part). #2920
Conversation
/azpw run Azure.sonic-swss |
/AzurePipelines run Azure.sonic-swss |
Azure Pipelines successfully started running 1 pipeline(s). |
this depends on sonic-net/sonic-swss-common#808 . we need submodule update . |
@arlakshm , please review |
Please add unit-tests |
sonic-net/sonic-sairedis#1301 is the preparation for adding tests for this PR |
For running the test, we need to merge |
Add fabric ports related calls for vs tests. This is the preparation for adding vs test for fabric daemon ( sonic-net/sonic-swss#2920 )
4a08249
to
7b73c97
Compare
Signed-off-by: Jie Feng <jfeng@arista.com>
the vs test failures needs |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
sonic-net/sonic-sairedis#1301 merged in on Sun, Oct 8 |
… vs environment (#16791) Add fabric port data for vs test, and start fabricmgrd in vs environment. This PR depends on sonic-net/sonic-sairedis#1301 sonic-net/sonic-swss#2920 needs this one merge first.
/Azp run Azure.sonic-swss |
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @jfeng-arista sonic-net/sonic-buildimage#16791 is merged now. Can you help update the branch. |
@jfeng-arista , I am adding the fabric monitoring device files for nokia platform and i am trying to understand the lanes field in the fabric_port_config.ini file. Does this need to match to the SAI_PORT_ATTR_HW_LANE_LIST returned by SAI for the fabric port?. name lanes isolateStatusFabric0 0 False Thanks, |
test_drop_counters.py:762: self = <test_drop_counters.TestDropCounters object at 0x7f3a31c208e0>
E AssertionError: assert 'SAI_PORT_STAT_IN_CONFIGURED_DROP_REASONS_1_DROPPED_PKTS' in 'SAI_PORT_STAT_OUT_CONFIGURED_DROP_REASONS_1_DROPPED_PKTS,SAI_PORT_STAT_IN_CONFIGURED_DROP_REASONS_0_DROPPED_PKTS' test_drop_counters.py:109: AssertionError this is the new test failure, not seems related to this change, will try trigger the test pipeline again |
test_drop_counters.py:762: self = <test_drop_counters.TestDropCounters object at 0x7fd196394a00>
E AssertionError: assert 'SAI_PORT_STAT_IN_CONFIGURED_DROP_REASONS_1_DROPPED_PKTS' in 'SAI_PORT_STAT_OUT_CONFIGURED_DROP_REASONS_1_DROPPED_PKTS,SAI_PORT_STAT_IN_CONFIGURED_DROP_REASONS_0_DROPPED_PKTS' test_drop_counters.py:109: AssertionError |
/azpw run Azure.sonic-swss |
/AzurePipelines run Azure.sonic-swss |
Azure Pipelines successfully started running 1 pipeline(s). |
Now all tests passed |
@prsunny, please help merge this PR |
@jfeng-arista , @arlakshm , could you please confirm all dependent PRs are merged and this is ready for merge? |
Yes. thank you |
Add support for fabric monitor daemon ( swss related changes )
Added fabricmgr that reacts the change in config_db and writes to appl_db, as orchagent can only reacts to the appl_db changes in current infrastructure.
So, when users configure the fabric link monitoring polling period or threshold to a none default values, the cli changes the value in config_db. This fabricmgr will react to the change in config_db and copy the value to appl_db. The fabric orchagent can react to the appl_db change and adjust the algorithm accordingly.
need to merge sonic-net/sonic-sairedis#1301 and sonic-net/sonic-buildimage#16791 first for test.
What I did
Why I did it
How I verified it
Details if related