[
https://issues.apache.org/jira/browse/YUNIKORN-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170587#comment-17170587
]
Weiwei Yang commented on YUNIKORN-332:
--------------------------------------
Hi [~adam.antal]
To be more specific.
When an allocation ask is reserved on a node
* describe the pod, we can see the event: "Pod is reserved on node <node-name>"
* describe the node, we can see the event: "Pod <namespace/pod-name> is
reserved on node <node-name>"
When an allocation ask is unreserved from a node, an ask can be unreserved
because 1) ask is removed; 2) ask can be allocated on this node; 3) ask can be
allocated on some other node.
* describe the pod, we can see the event: "Pod is unreserved from the node
<node-name>"
* describe the node, we can see the event: "Reservation for pod
<namespace>/<pod-name> has been removed"
> 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]
