[ https://issues.apache.org/jira/browse/YARN-8851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16665382#comment-16665382 ]
Chandni Singh commented on YARN-8851: ------------------------------------- Thanks [~tangzhankun] {quote} "DeviceRegisterRequest getDeviceResourceInfo" and "DeviceRegisterRequest getRegisterRequestInfo()". Maybe the later one is more acurate since the "DeviceRegisterRequest" may contains more info besides resource name & version we currently want? {quote} {{getRegisterRequestInfo()}} is good. {quote} We have another interface "DevicePluginScheduler" to do this. {quote} {code} Set<Device> allocateDevices(Set<Device> availableDevices, Integer count); {code} I saw the above API. This one seems that if the implementation of custom scheduler is provided, this implementation will allocate devices which is fine. However, the DevicePluginAPI can have a method {code} onDevicesAllocated(Set<Device> allocatedDevices) {code} Let's say the user does NOT want to provide a custom DevicePluginScheduler and use the default one. This will be call back after the devices get allocated. It also seems to complete the current DevicePluginAPI which has a {{onDevicesReleased(devices)}} method. > [Umbrella] A new pluggable device plugin framework to ease vendor plugin > development > ------------------------------------------------------------------------------------ > > Key: YARN-8851 > URL: https://issues.apache.org/jira/browse/YARN-8851 > Project: Hadoop YARN > Issue Type: New Feature > Components: yarn > Reporter: Zhankun Tang > Assignee: Zhankun Tang > Priority: Major > Attachments: YARN-8851-WIP2-trunk.001.patch, > YARN-8851-WIP3-trunk.001.patch, YARN-8851-WIP4-trunk.001.patch, > YARN-8851-WIP5-trunk.001.patch, YARN-8851-WIP6-trunk.001.patch, > YARN-8851-WIP7-trunk.001.patch, [YARN-8851] > YARN_New_Device_Plugin_Framework_Design_Proposal-3.pdf, [YARN-8851] > YARN_New_Device_Plugin_Framework_Design_Proposal.pdf > > > At present, we support GPU/FPGA device in YARN through a native, coupling > way. But it's difficult for a vendor to implement such a device plugin > because the developer needs much knowledge of YARN internals. And this brings > burden to the community to maintain both YARN core and vendor-specific code. > Here we propose a new device plugin framework to ease vendor device plugin > development and provide a more flexible way to integrate with YARN NM. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org