[
https://issues.apache.org/jira/browse/YUNIKORN-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515704#comment-17515704
]
Wilfred Spiegelenburg commented on YUNIKORN-332:
------------------------------------------------
Yes this is still relevant. The way it was approached back then does not apply
at this point. A lot has changed, but on the other hand a lot has stayed the
same too. The main point is still to hook this into the scheduling cycle. Keep
the solution as simple as possible.
BTW: I am not sure if we even show the reservations in the app or node outside
of the scheduler. We might need to expose that in the REST objects also
(separate jira?)
> Add events for reserved pods
> ----------------------------
>
> Key: YUNIKORN-332
> URL: https://issues.apache.org/jira/browse/YUNIKORN-332
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: core - scheduler, shim - kubernetes
> Reporter: Adam Antal
> Assignee: Anuraag Nalluri
> Priority: Critical
> Labels: pull-request-available
>
> Pod Event
> - When a pod gets reserved to some node, we need to publish the event to the
> pod and let user know this pod reserved a spot.
> Node Event
> - When a node is reserved by a pod, we need to publish an event to node to
> let user know the node is reserved by some pod.
> - When the pod is unreserved from the node, we also need to publish another
> event
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
