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

Add DEL/CLEAR support for port QoS Map #1566

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

vishnushetty
Copy link
Contributor

What I did
Supported DEL/CLEAR support for PortQoSMap

Why I did it
config qos clear to work

How I verified it
swssloglevel -l INFO -c orchagent

Details if related
Dec 23 01:42:56.135137 sonic NOTICE swss#orchagent: :- handlePortQosMapTable: Removed (all) 64 from port Ethernet8
Dec 23 01:42:56.135164 sonic NOTICE swss#orchagent: :- handlePortQosMapTable: Removed (all) 66 from port Ethernet8
Dec 23 01:42:56.135240 sonic NOTICE swss#orchagent: :- handlePortQosMapTable: Removed (all) 74 from port Ethernet8
Dec 23 01:42:56.135384 sonic NOTICE swss#orchagent: :- handlePortQosMapTable: Removed (all) 71 from port Ethernet8
Dec 23 01:42:56.135553 sonic NOTICE swss#orchagent: :- handlePortQosMapTable: Removed (all) 68 from port Ethernet8
Dec 23 01:42:56.135553 sonic NOTICE swss#orchagent: :- handlePortQosMapTable: Applied QoS maps to ports

@ben-gale
Copy link
Collaborator

@lguohan - pls help with review - thx

EdenGri pushed a commit to EdenGri/sonic-swss that referenced this pull request Feb 28, 2022
…sted (sonic-net#1566)

Enhancement: handle the case that no buffer change in the latest database version
Current, the following two versions are the same:
- The latest version changed by mellanox_buffer_migrator
- The latest version in CONFIG_DB

That won't be true if another part in CONFIG_DB is updated. In that case, the latest version in CONFIG_DB will be greater than the latest version in mellanox_buffer_migrator.
However, this can break the buffer migrator unit test:
- The db_migrator will always migrate the database to the latest version
- The config database version check will fail in case the latest version in the config database doesn't match that defined in the buffer migrator.

This is to support this case.

Signed-off-by: Stephen Sun <stephens@nvidia.com>
EdenGri pushed a commit to EdenGri/sonic-swss that referenced this pull request Feb 28, 2022
…rator test cases as well (sonic-net#1614)

- What I did
Originally, the method advance_version_for_expected_database was introduced (in sonic-net#1566) to handle the case the latest version in CONFIG_DB is greater than the latest version in mellanox_buffer_migrator.
Now there are other database migrators whose test cases can also encounter this situation, like port auto-negotiation (sonic-net#1568) and port-channel for LACP key (sonic-net#1473).
So I would like to make the method public, available for all database migrators.
Related database migrator test cases have been updated accordingly.

- How to verify it
Run the unit test.

Signed-off-by: Stephen Sun <stephens@nvidia.com>
EdenGri pushed a commit to EdenGri/sonic-swss that referenced this pull request Feb 28, 2022
What I did
The port-channel key migrator was introduced in version 2_0_2 so the expected database version of the test case should be 2_0_2.
It was modified to 2_0_3 when the new version was introduced by mistake. This won't fail the test but disable the require its database version to be updated every time a new version is introduced. (Refer sonic-net#1566 and sonic-net#1614 for details)
This is to correct it by changing it back to 2_0_2.

Signed-off-by: Stephen Sun <stephens@nvidia.com>
@prsunny prsunny requested a review from neethajohn as a code owner September 2, 2022 23:17
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.

2 participants