[
https://issues.apache.org/jira/browse/MESOS-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774668#comment-16774668
]
Meng Zhu edited comment on MESOS-9314 at 2/22/19 1:44 AM:
----------------------------------------------------------
The current plan is to just use name and value pairs to express quantity on the
API side:
map<string, Value.Scalar>
See the design doc for [quota
2.0|https://docs.google.com/document/d/13vG5uH4YVwM79ErBPYAZfnqYFOBbUy2Lym0_9iAQ5Uk/edit#]
for more details.
In addition to the API side, we also introduced a `ResourceQuantity` class
internally: https://reviews.apache.org/r/69599
Closing this.
was (Author: mzhu):
The current plan is to just use:
map<string, Value.Scalar>
See the design doc for [quota
2.0|https://docs.google.com/document/d/13vG5uH4YVwM79ErBPYAZfnqYFOBbUy2Lym0_9iAQ5Uk/edit#]
for more details.
In addition to the API side, we also introduced a `ResourceQuantity` class
internally: https://reviews.apache.org/r/69599
Closing this.
> 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)
