You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Meng Zhu (JIRA)" <ji...@apache.org> on 2018/12/11 23:14:00 UTC

[jira] [Commented] (MESOS-9314) Consider introducing a ScalarResourceQuantity protobuf message.

    [ https://issues.apache.org/jira/browse/MESOS-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718166#comment-16718166 ] 

Meng Zhu commented on MESOS-9314:
---------------------------------

Design doc https://docs.google.com/document/d/1WbRKmqsos1-IBJ9VjpT4kNIp2Peyvx2k4UphRaFVYFU/edit#

> Consider introducing a ScalarResourceQuantity protobuf message.
> ---------------------------------------------------------------
>
>                 Key: MESOS-9314
>                 URL: https://issues.apache.org/jira/browse/MESOS-9314
>             Project: Mesos
>          Issue Type: Improvement
>          Components: HTTP API
>            Reporter: Benjamin Mahler
>            Assignee: Meng Zhu
>            Priority: Major
>              Labels: multitenancy
>
> As part of introducing quota limits, we're adding a new master::Call for updating quota. This call can take a simplified message that expresses scalar resource quantities:
> {code}
> message ScalarResourceQuantity {
>   required string name;
>   required Value::Scalar quantity;
> }
> {code}
> This greatly simplified the validation code, as well as the UX of the API when it comes to knowing what kind of data to provide.
> Ideally, the new quota paths can use this message in lieu of Resource objects, but we'll have to explore backwards compatibility (e.g. registry data).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)