[
https://issues.apache.org/jira/browse/YUNIKORN-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552662#comment-17552662
]
Manikandan R commented on YUNIKORN-1235:
----------------------------------------
SI changes are incompatible as we have changed {{Priority}} field type of
{{Allocation}} & {{AllocationAsk}} message from {{Priority}} to int32 using
same field number. But, Still it is ok to go ahead as we do not allow shim
version X to talk to core version Y.
Priority is now defined as an integer (32 bits) with natural ordering. i.e. the
higher the number the higher the priority.
> pass priority on pods from shim into the core
> ---------------------------------------------
>
> Key: YUNIKORN-1235
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1235
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: core - scheduler, scheduler-interface, shim - kubernetes
> Reporter: Manikandan R
> Assignee: Manikandan R
> Priority: Major
> Labels: pull-request-available
>
> First step to support priority based pod handling: make sure we get the pod
> priority from the shim into the core. The current communication runs via the
> allocation ask.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
