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

[201911][acl-loader] Use 'ipaddress' module in lieu of 'ipaddr' #1484

Closed
wants to merge 1 commit into from
Closed

[201911][acl-loader] Use 'ipaddress' module in lieu of 'ipaddr' #1484

wants to merge 1 commit into from

Conversation

jleveque
Copy link
Contributor

@jleveque jleveque commented Mar 5, 2021

What I did

Use 'ipaddress' module in lieu of 'ipaddr' in acl-loader.

This aligns acl-loader with all other sonic-utilities code in 201911 and aligns it with upstream modifications.

How I did it

Use 'ipaddress' module in lieu of 'ipaddr' in acl-loader.

How to verify it

Test acl-loader on 201911 branch.

@vaibhavhd
Copy link
Contributor

Should a corresponding change be made for 201811 branch too? That's where I have seen these tests to fail.

@jleveque
Copy link
Contributor Author

jleveque commented Mar 6, 2021

Change is unnecessary in 201911 and cannot be ported exactly as is upstream due to differences between Python 2 and 3. Rather than add typecasting here, I will close this PR. We will continue to use 'ipaddr' in acl-loader in 201911.

@jleveque jleveque closed this Mar 6, 2021
@jleveque jleveque deleted the acl_loader_ipaddress_201911 branch March 6, 2021 00:11
sflow pushed a commit to sflow/sonic-utilities that referenced this pull request Feb 3, 2024
* added CLI: config sflow drop-monitor-limit 1-999 (0 to disable)
* added line to show sflow output to indicate current setting
* added test to ensure that out-of-range value is denied

The effect is to add the redis field drop_monitor_limit to the
sflow configuration table in redis, as described in
pull-request sonic-net#1484 on the sonic-net/SONiC repo.

Note: hsflowd version 2.0.52 will apply this setting.
Older versions will ignore it.

Signed-off-by: Neil McKee  neil.mckee@inmon.com
sflow added a commit to sflow/sonic-utilities that referenced this pull request Feb 5, 2024
* added CLI: config sflow drop-monitor-limit 1-999 (0 to disable)
* added line to show sflow output to indicate current setting
* added test to ensure that out-of-range value is denied

The effect is to add the redis field drop_monitor_limit to the
sflow configuration table in redis, as described in
pull-request sonic-net#1484 on the sonic-net/SONiC repo.

Note: hsflowd version 2.0.52 will apply this setting.
Older versions will ignore it.

Signed-off-by: Neil McKee  neil.mckee@inmon.com
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