[
https://issues.apache.org/jira/browse/YUNIKORN-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17815907#comment-17815907
]
Wilfred Spiegelenburg commented on YUNIKORN-2372:
-------------------------------------------------
I think we can piggyback on the queue changes for sure. That is why I added it
to the 1.6.0 release for tracking. I also linked this as related to the
umbrella for the new queue UI. Some of the work can be done already without the
new queue display.
Reading the rest response generate the base page that allows for a list of
users and groups with searching etc can all be done before we even think about
the way we show the queue hierarchy for a user or group that is selected.
{quote}This is obviously something for the future, but do you think we should?
{quote}
I do _not_ think we should track pending resources for a user or group. It is a
lot of overhead and complexity that does not really add functionality. Even the
queue only shows a count of pending resources for all applications in that
queue. The application is the only one that shows the asks.
The queue or the application will be the normal entry point. I doubt that there
will be an investigation starting with "why does this user have pending
resource..." It will normally be "why is my application pending?" or "why has
the queue pending resources and quota left?"
If you have pending resources it will be linked to the queue or application,
quotas are first check. That flow for tracing down why you have a pending
resource is logical. Starting at a user or group does not make sense as you
still need to know the queue for the user. For the group the queue and the
application are needed to confirm that it is tracked for the group.
> Show user/group quota information on the UI
> -------------------------------------------
>
> Key: YUNIKORN-2372
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2372
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: core - scheduler
> Reporter: Peter Bacsko
> Assignee: Dong-Lin Hsieh
> Priority: Major
>
> From a supportability point of view, it's very helpful to show user/group
> quotas on the UI. If a pod is unschedulable due to an insufficient quota,
> then it's immediately obvious why once the user looks at the quotas and sees
> a red bar for a given user/group.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
