[
https://issues.apache.org/jira/browse/MESOS-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4058:
---------------------------------------
Description:
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?
was:
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.
As food for thought we may want to introduce a schema or a typed object per
each quota request.
> 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)
