Add support for Accton wedge100bf_32qs platform

[alvinkaiwei]

Why I did it

This pull request is based on wedge100bf_32x.

The components on the mainboard are the same as wedge100bf_32x, except for tofino 32Q and COMe models, so it refers to wedge100bf_32x to create new model: wedge100bf_32qs.

Signed-off-by: alvin_feng alvin_feng@accton.com

How I did it

It refers to wedge100bf_32x to create new model: wedge100bf_32qs.

How to verify it

Verify on the 32qs device.
show interface status
sfputil show eeprom
sfputil show presence
show platform syseeprom
psuutil status

Which release branch to backport (provide reason below if selected)

• 201811
• 201911
• 202006
• [x ] 202012
• 202106

[lgtm-com]

This pull request introduces 6 alerts when merging f1deed2 into 1c86196 - view on LGTM.com

new alerts:

• 6 for Except block handles 'BaseException'

[qiluo-msft]

Could you PR against master branch first and request cherry-pick to release branch like 202012? As PR submitter, I believe you could modify the base branch in this PR directly.

[qiluo-msft]

As comment

[alvinkaiwei]

Could you PR against master branch first and request cherry-pick to release branch like 202012? As PR submitter, I believe you could modify the base branch in this PR directly.

Yes, I can modify the base branch in this PR.
But I'm not sure how to do "request cherry-pick to release branch 202012" after the modification?

Thanks

[alvinkaiwei]

Hi qiluo-msft

I want to confirm with you again what you said.
Do you mean the following?

1. We push the commit to SONiC-master first.
2. When the user wants to use this modification, user must pull the SONiC-202012 codebase and use git cherry-pick to pick our modification commit from SONiC-master.

Because of the modification we want to push, it can only be used on the SONiC-202012 branch and it needs to match SAI version 1.7.1.
So, can we directly push the modification to SONiC-202012 branch?

Thanks.

[akokhan]

@alvinkaiwei , looks like no SAI/SDK specific changes in this PR. So, it should be Ok just to update #9257 description as per original SONiC PR template and mark it to be cherry-picked into 202012.

Also, this PR makes a copy of the original BFN platform plugins. This may introduce maintenance difficulty. So, I believe we should avoid this until it's really needed. Instead, symlink can be created.

[alvinkaiwei]

@akokhan, we will close this PR and just to update #9257 description as per original SONiC PR template and mark it to be cherry-picked into 202012.