[
https://issues.apache.org/jira/browse/MESOS-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15083491#comment-15083491
]
Alexander Rukletsov edited comment on MESOS-4058 at 1/5/16 11:40 PM:
---------------------------------------------------------------------
https://reviews.apache.org/r/41936/
https://reviews.apache.org/r/41937/
https://reviews.apache.org/r/41947/
https://reviews.apache.org/r/41948/
was (Author: alexr):
https://reviews.apache.org/r/41936/
https://reviews.apache.org/r/41937/
> Do not use `Resource.role` for resources in quota request.
> ----------------------------------------------------------
>
> Key: MESOS-4058
> URL: https://issues.apache.org/jira/browse/MESOS-4058
> Project: Mesos
> Issue Type: Improvement
> Components: master
> Reporter: Alexander Rukletsov
> Assignee: Alexander Rukletsov
> Labels: mesosphere
>
> To be consistent with other operator endpoints and to adhere to the principal
> of least surprise, move role from each {{Resource}} in quota set request to
> the request itself.
> {{Resource.role}} is used for reserved resources. Since quota is not a direct
> reservation request, to avoid confusion we shall not reuse this field for
> communicating the role for which quota should be reserved.
> Food for thought: Shall we try to keep internal storage protobufs as close as
> possible to operator's JSON to provide some sort of a schema or decouple
> those two for the sake of flexibility?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
