[
https://issues.apache.org/jira/browse/YUNIKORN-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479765#comment-17479765
]
Weiwei Yang commented on YUNIKORN-971:
--------------------------------------
hi [~ccondit]
Do you mean in the scheduling chain, when it gets to YK's Filter(), the node
has already been evaluated by the default scheduler and it should be qualified
for the pod? Is the logic in the backend looks like, for each node in the
cluster, scheduler framework check each \{pod, node} pairs by going through all
the Filter() plugins, and stop when all plugins return success?
Thanks for putting the google doc link, I'll comment on that.
> Implement YuniKorn as a Kubernetes Scheduler Plugin
> ---------------------------------------------------
>
> Key: YUNIKORN-971
> URL: https://issues.apache.org/jira/browse/YUNIKORN-971
> Project: Apache YuniKorn
> Issue Type: New Feature
> Components: shim - kubernetes
> Reporter: Craig Condit
> Assignee: Craig Condit
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.0.0
>
> Attachments: YuniKorn as K8S Scheduler Plugin.pdf
>
>
> As of Kubernetes 1.19, there is a new [scheduling
> framework|https://kubernetes.io/docs/concepts/scheduling-eviction/scheduling-framework/]
> available to scheduler implementations. This exposes all the functionality
> of the default Kubernetes scheduler, but allows plugins to be added which
> augment and extend the default scheduler functionality.
> We should explore implementing YuniKorn using this new framework. See
> attached design document for rationale and approach.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
