You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by Wilfred Spiegelenburg <wi...@apache.org> on 2022/08/05 03:17:23 UTC
[DISCUSSION] usage tracking for users
As a first step for implementing quotas around users and groups we
have looked at tracking usage inside YuniKorn for a user and group.
The design document referenced [1] sets out a design for tracking this
usage.
The usage tracking is based on the existing user propagation from the
k8shim into the core. We do not intend that to change as part of the
tracking implementation. We did realise that the current user details
are limited but that does not impact the design. The user object is
stable and flexible enough to support all use cases. The way the user
is retrieved and set in the object might change but that is not
relevant for the usage tracking.
We have also on purpose disconnected the usage tracking from
enforcement of a quota on that usage. We are working on a design for
the enforcement that sits on top of this tracking design. More to
follow on that one soon.
Feedback and comment welcome,
Wilfred
[1] https://docs.google.com/document/d/19FYOL1Uw7tSf74qyuVN40Fv-GdWd2KrBcHJpUQLTBZ4/edit?usp=sharing
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org
Re: [DISCUSSION] usage tracking for users
Posted by Manikandan R <ma...@gmail.com>.
Hi Everyone,
We started doing the implementation and wanted to check with the community
to know any feedback/comments on the design. Please feel free to share your
thoughts if you have any.
Thanks,
Mani
On Fri, Aug 5, 2022 at 8:47 AM Wilfred Spiegelenburg <wi...@apache.org>
wrote:
> As a first step for implementing quotas around users and groups we
> have looked at tracking usage inside YuniKorn for a user and group.
> The design document referenced [1] sets out a design for tracking this
> usage.
>
> The usage tracking is based on the existing user propagation from the
> k8shim into the core. We do not intend that to change as part of the
> tracking implementation. We did realise that the current user details
> are limited but that does not impact the design. The user object is
> stable and flexible enough to support all use cases. The way the user
> is retrieved and set in the object might change but that is not
> relevant for the usage tracking.
>
> We have also on purpose disconnected the usage tracking from
> enforcement of a quota on that usage. We are working on a design for
> the enforcement that sits on top of this tracking design. More to
> follow on that one soon.
>
> Feedback and comment welcome,
> Wilfred
>
> [1]
> https://docs.google.com/document/d/19FYOL1Uw7tSf74qyuVN40Fv-GdWd2KrBcHJpUQLTBZ4/edit?usp=sharing
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
> For additional commands, e-mail: dev-help@yunikorn.apache.org
>
>