-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PDK PDDF HLD PR request #406
Conversation
|
||
## 1 Requirements Overview | ||
SONiC OS is portable across different network devices with supported ASIC via Switch Abstraction Interface (SAI). These devices primarily differ in the way various device specific hardware components are accessed, and thus require custom device drivers and python plugins. Each platform vendor implements these custom device drivers and plugins. The feature requirement is to support a SONiC platform driver development framework to enable rapid development of custom device drivers and plugins. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently SONiC is in the process to replace platform plugin with a newly designed platform APIs, the target is to switch to new platform API in 201908 release, so should also considering to support platform API for the coming transform. The design doc of new platform API is here: #285 the new platform base class is defined here: https://github.com/Azure/sonic-platform-common/tree/master/sonic_platform_base
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Kebo Liu,
Yes, we are aware of the new platform API in August, 2019 release. We plan to support new platform base class in PDDF.
-Fuzail
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fk410167: Do you have plans to update this document to reflect the new platform API? Vendors are currently in the process of migrating over to the new API. At this point in time, this document should reflect the new API rather than the old plugins.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes we have already started to move the whole framework to use 2.0 platform APIs. We will modify the HLD accordingly.
@fk410167 assuming platform vendor will use its own drivers and not using generic drivers with JSON descriptor files approach, how can vendor use generic plugin/platform API implementation by providing sysfs path or symlink to sysfs and attributes list? |
Hi stepanblyschak,
-Fuzail |
…624) This change is related to Platform Driver Development Framework (PDDF) which is being added to sonic-buildimage repo. More details can be found here, sonic-net/SONiC#406 PDDF supports its own CLI utilities, which use generic PDDF component plugins. I added these PDDF CLI utilities.
…624) This change is related to Platform Driver Development Framework (PDDF) which is being added to sonic-buildimage repo. More details can be found here, sonic-net/SONiC#406 PDDF supports its own CLI utilities, which use generic PDDF component plugins. I added these PDDF CLI utilities.
…#624) This change is related to Platform Driver Development Framework (PDDF) which is being added to sonic-buildimage repo. More details can be found here, sonic-net/SONiC#406 PDDF supports its own CLI utilities, which use generic PDDF component plugins. I added these PDDF CLI utilities.
This document describes the Platform Driver Development Framework (PDDF) which optimises platform driver and SONiC plugin development using a data-driven model.