Added support to get random asic in a testcase using 'enum_rand_one_asic_index' #3017
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of PR
Summary:
Fixes # (issue)
Type of change
Approach
What is the motivation for this PR?
If a script has 'enum_rand_one_per_hwsku_frontend_hostname' and 'enum_asic_index' , enum_asic_index always returns asics from first dut. but It should be returning asics from the dut chosen by 'enum_rand_one_per_hwsku_frontend_hostname'.
If a script needs to run test cases only on one asic, we need a way to get random asic index.
How did you do it?
Added enum_rand_one_asic_index to get random asic index.
How did you verify/test it?
Ran on muti-asic dut.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation