[ https://issues.apache.org/jira/browse/MESOS-9599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892347#comment-16892347 ]
Meng Zhu commented on MESOS-9599: --------------------------------- {noformat} commit ed06bc6b539eea115375640703eb0934328daca6 Author: Meng Zhu m...@mesosphere.io Date: Tue May 21 16:07:41 2019 +0200 Added `repeated QuotaConfig` to `QuotaStatus`. Also marked the `infos` field as deprecated. `QuotaStatus` is returned by `GET_QUOTA` and `GET /quota`. As we introduce quota limits, a new mesage `QuotaConfig` is introduced to describe the quota configuration. For backwards compatibility, we will fill in both fields until `QuotaInfo` is removed (in Mesos 2.0). Review: https://reviews.apache.org/r/70690 {noformat} > Update `GET_QUOTA` to return both guarantees and limits. > --------------------------------------------------------- > > Key: MESOS-9599 > URL: https://issues.apache.org/jira/browse/MESOS-9599 > Project: Mesos > Issue Type: Task > Reporter: Meng Zhu > Priority: Major > Labels: resource-management > > We should mark the existing `QuotaInfo` message as deprecated in favor of the > new `QuotaConfig`: > {noformat} > message GetQuota { > required quota.QuotaStatus status = 1; > } > message QuotaStatus { > repeated QuotaInfo infos [deprecated = true]; > repeated QuotaConfig configs; > } > message QuotaConfig { > required string role; > map<string, Value.Scalar> guarantees; > map<string, Value.Scalar> limits; > } > {noformat} > We will continue to fill in the QuotaInfo though for backward compatibility. > See the design doc: [New > API|https://docs.google.com/document/d/13vG5uH4YVwM79ErBPYAZfnqYFOBbUy2Lym0_9iAQ5Uk/edit#heading=h.z2vfcyzabymz] -- This message was sent by Atlassian JIRA (v7.6.14#76016)