Update fabric test plan

[jfeng-arista]

Description of PR

Summary: Update fabric test plan
Fixes # (issue)

Type of change

• Bug fix
• Testbed and Framework(new/improvement)
• Test case(new/improvement)

Back port request

• 201911
• 202012

Approach

What is the motivation for this PR?

How did you do it?

How did you verify/test it?

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

[ghost]

All CLA requirements met.

[kenneth-arista]

@arlakshm for awareness

[kenneth-arista]

/Azp run Azure.sonic-mgmt

[azure-pipelines]

Commenter does not have sufficient privileges for PR 5678 in repo Azure/sonic-mgmt

[jfeng-arista]

/Azp run Azure.sonic-mgmt

[azure-pipelines]

Commenter does not have sufficient privileges for PR 5678 in repo Azure/sonic-mgmt

[rlhui]

Please specify if this check is expected to be done on all line cards and sup as well.

[jfeng-arista]

The check is done for both linecards and fabric cards on sup. I also updated document with this information

[rlhui]

As this is to model the fabric links with software/defined in yaml file, is this applicable for packet based chassis too?

[arlakshm]

Please check if this information can be added in the seperate yaml file for each testbed.

[jfeng-arista]

The the fabric link map information is generated dynamically when run the test based on which slot the card is inserted in the system , which type of cards ( sku ), and all these information is in the testbed.yaml file now, and we can get the information while generating the testbed.yaml file and the same time update the fabric topology into it. If they are in separate files, then we will need to get the information from processing the testbed.yaml and then generate the fabric topology into a different files, this can be done , but it will taking longer time also need to parse the same information several times . So we want to double check here if we still want to have the fabric topology information in a separate yaml file ? thank you !

[jfeng-arista]

Discussed with Arvind, the information will be added in separate yaml files for each type of cards.

[jfeng-arista]

/easycla

[arlakshm]

Hi @jfeng-arista, please fix the conflicts

[mssonicbld]

The pre-commit check detected issues in the files touched by this pull request.
The pre-commit check is a mandatory check, please fix detected issues.

Detailed pre-commit check results:
trim trailing whitespace.................................................Failed
- hook id: trailing-whitespace
- exit code: 1
- files were modified by this hook

Fixing docs/testplan/Chassis-fabric-test-plan.md

fix end of files.........................................................Passed
check yaml...........................................(no files to check)Skipped
check for added large files..............................................Passed
check python ast.....................................(no files to check)Skipped
flake8...............................................(no files to check)Skipped
check conditional mark sort..........................(no files to check)Skipped

To run the pre-commit checks locally, you can follow below steps:

1. Ensure that default python is python3. In sonic-mgmt docker container, default python is python2. You can run
   the check by activating the python3 virtual environment in sonic-mgmt docker container or outside of sonic-mgmt
   docker container.
2. Ensure that the pre-commit package is installed:

sudo pip install pre-commit

3. Go to repository root folder
4. Install the pre-commit hooks:

pre-commit install

5. Use pre-commit to check staged file:

pre-commit

6. Alternatively, you can check committed files using:

pre-commit run --from-ref <commit_id> --to-ref <commit_id>

[jfeng-arista]

/easycla