[PBH] CLI for Policy Based Hashing#1701
Conversation
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
…tions Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
| inner_v4_hash inner_ip_proto | ||
| inner_l4_dst_port | ||
| inner_l4_src_port | ||
| inner_dst_ipv4 | ||
| inner_src_ipv4 | ||
| inner_v6_hash inner_ip_proto | ||
| inner_l4_dst_port | ||
| inner_l4_src_port | ||
| inner_dst_ipv6 | ||
| inner_src_ipv6 |
There was a problem hiding this comment.
If we won't have too many Hash Field Items / Name can maybe consolidate this into one row / Name
There was a problem hiding this comment.
@kktheballer the question is not clear: can you please share an example for such a use case?
There was a problem hiding this comment.
What I meant was that if we have too many hash field items and we make each item go into each row we may have to scroll down to view all the output.
If we will only have 4-8 hash field items per inner_v4/6_hash we could leave it as is
There was a problem hiding this comment.
@kktheballer so far there will be only up to 7 hash fields. If we introduce more, than we can revisit the current CLI business logic. Are you ok with that?
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
Signed-off-by: Nazarii Hnydyn <nazariig@nvidia.com>
…to parametrized Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
config/plugins/pbh.py
Outdated
| @click.option( | ||
| "--ip-mask", | ||
| help="""Configures IPv4/IPv6 address mask for this hash field, required when the value of --hash-field are - INNER_DST_IPV4 or | ||
| INNER_SRC_IPV4 or INNER_SRC_IPV4 or INNER_SRC_IPV4 """, |
config/plugins/pbh.py
Outdated
| ) | ||
| @click.option( | ||
| "--hash-field", | ||
| help="Configure native hash field for this hash field", |
There was a problem hiding this comment.
@vadymhlushko-mlnx please fix the description according to YANG model
There was a problem hiding this comment.
@nazariig it is already according to the YANG model
There was a problem hiding this comment.
@vadymhlushko-mlnx in YANG we have description "Configures native hash field for this hash field";
config/plugins/pbh.py
Outdated
| @click.option( | ||
| "--hash", | ||
| required=True, | ||
| help="Configures the hash to apply", |
There was a problem hiding this comment.
@vadymhlushko-mlnx please align the description with update subgroup - use YANG model as reference
config/plugins/pbh.py
Outdated
| ) | ||
| @click.option( | ||
| "--ip-mask", | ||
| help="Configures IPv4/IPv6 address mask for this hash field", |
There was a problem hiding this comment.
@vadymhlushko-mlnx please align the description with add subgroup. Use YANG model as a reference
There was a problem hiding this comment.
@nazariig it is already according to the YANG model
There was a problem hiding this comment.
@vadymhlushko-mlnx please rework as per internal review comments
config/plugins/pbh.py
Outdated
| ) | ||
| @click.option( | ||
| "--priority", | ||
| help="Configures priority", |
There was a problem hiding this comment.
@vadymhlushko-mlnx please align the description with YANG model
Signed-off-by: Vadym Hlushko <vadymh@nvidia.com>
84d9b46 to
6a19368
Compare
|
@kktheballer kindly reminder we wish to have the code merges so the test can be verified on top of it. |
|
@kktheballer could you please review and approve? |
|
@liat-grozovik could you please help to merge? |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Ignore inner_hashing test on non-master image. The dependent change in sonic-net/sonic-utilities#1701 is not back port into 202012 branch yet. Hence ```config pbh table``` command is not supported. Signed-off-by: bingwang <bingwang@microsoft.com>
What I did
Created click CLI plugins for PBH feature
How I did it
The CLI plugins were auto-generated (by using the sonic-cli-gen) for
showandconfigCLI groups, then manually those were manually edited to meet PBH the CLI requirements according to the PBH HLDHow to verify it
Added the UT
Which release branch to backport (provide reason below if selected)
Previous command output (if the output of a command-line utility has changed)
New command output (if the output of a command-line utility has changed)