[
https://issues.apache.org/jira/browse/YUNIKORN-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175137#comment-17175137
]
Wilfred Spiegelenburg commented on YUNIKORN-332:
------------------------------------------------
This should mirror the internal updates we do in the scheduler when we process
the result. All these cases are handled in the scheduling context to keep the
internal state in sync.
See my comment in the PR.
> 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: Adam Antal
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
