CPO common cpoutil commands

[KroosMicas]

add CPO common cpoutil commands

[mssonicbld]

/azp run

[azure-pipelines]

No pipelines are associated with this pull request.

[mssonicbld]

/azp run

[azure-pipelines]

No pipelines are associated with this pull request.

[zili11720]

Hi @KroosMicas,

I have 2 questions regarding the cpoutil show commands:

1. I don’t see how vendor-specific fields can be integrated into the output.
   In sfputil, DOM formatting is driven by known maps, so unmapped fields are not printed. If cpoutil follows that pattern, vendors will need a defined way to contribute labels/units for platform-specific fields.

I suggest supporting vendor-specific format maps that are merged into cpoutil show output, with the maps owned by the platform rather than hardcoded in the common CLI. This reuses the idea from #2317 adapted for cpoutil.
Can the HLD clarify how vendor specific fields should be integrated?

2. Today for pluggables we have two types of show commands:

• sfputil — direct hardware access (sonic-utilities/sfputil/main.py)
• show interfaces transceiver … - reads STATE_DB only (sonic-utilities/scripts/sfpshow)
  Examples:
  show interfaces transceiver eeprom EthernetX -d
  show interfaces transceiver status EthernetX
  This HLD covers a CPO analogue of sfputil (cpoutil). I don’t see a STATE_DB-backed 'show interfaces …' path for CPO in scope.

Do we plan to extend / add show interfaces … commands for CPO that rely on STATE_DB only (like sfpshow)?
If yes, the first question applies here as well for DOM/STATUS maps.

Thanks

[eddyk-nvidia]

what about the reset of some specific laser on a certain ELS ? Some vendors can support it

[eddyk-nvidia]

please refer to the Nvidia HLD on cpoutil for FW management - #2489