[
https://issues.apache.org/jira/browse/YUNIKORN-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631402#comment-17631402
]
Qi Zhu commented on YUNIKORN-1389:
----------------------------------
Thank you a lot, [~wilfreds] for reply and details, yeah i agree with you, the
scheduling cycle will not use the node label.
We may need to use node label for:
1. Customers to query, if from UI side, we need to design where to expose the
label info. Besides the UI, if we can expose the labels to the rest api, so
that we can get the info from core side first, such as:
{
"NodeLabel1":{
"node1",
"node3"
},
"NodeLabel2":{
"node2",
"node4"
}
}
And after that, we can discuss which UI need for node label or not.
2. We may need to aggregate one label info for metrics and analysis, such as
the instance type: YUNIKORN-1385
> Pass node labels from shim to core.
> -----------------------------------
>
> Key: YUNIKORN-1389
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1389
> Project: Apache YuniKorn
> Issue Type: Task
> Components: shim - kubernetes
> Reporter: Qi Zhu
> Assignee: Qi Zhu
> Priority: Major
> Labels: pull-request-available
>
> Suggested by YUNIKORN-1362:
> The YuniKorn UI shows the list of all the nodes in the cluster. There is no
> way of filtering the list.
> We have only certain nodes that we want our jobs to be scheduled in the
> cluster and that is dictated by the nodeSelector. I would good to have a way
> to show only those nodes on the UI to give a better idea of the resources
> that we have for the jobs to be scheduled
> The functionality will depend on the details we pull for the nodes into the
> core. Propagating some info for a node from the shim into the core might be
> needed.
> Here we first to pass node labels from shim to core.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
