[jira] [Commented] (YUNIKORN-490) generate the SchedulerAPI and callback interface from the SI

["Manikandan R (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YUNIKORN-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17284761#comment-17284761 ] 

Manikandan R commented on YUNIKORN-490:
---------------------------------------

[~wilfreds] I can see RPC based syntax constructs in https://github.com/apache/incubator-yunikorn-scheduler-interface/blob/master/scheduler-interface-spec.md, but API based interfaces are in use and recommended approach too as mentioned in the doc.

Now, from cleaner separation perspective, we are trying to avoid the dependency on "core" for build process, but am not sure how to define the API interfaces in Protobuf message format. Can you help me to take it forward? Thanks.

> generate the SchedulerAPI and callback interface from the SI
> ------------------------------------------------------------
>
>                 Key: YUNIKORN-490
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-490
>             Project: Apache YuniKorn
>          Issue Type: Sub-task
>          Components: scheduler-interface
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Manikandan R
>            Priority: Major
>
> The SchedulerAPI and callback are closely linked to the SI. The interface is however not defined in the scheduler interface but in the core.
> Currently the core and shim both use that one interface defined in the core to build. This means that a shim must pull in the core to be able to build. It would be preferable to define the interface with the messages in the SI for implementation by both the core and the shims.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org