[MESOS-4058] Do not use `Resource.role` for resources in quota request.

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.27.0
• Component/s: master
• Labels: mesosphere
• Target Version/s: 0.27.0
• Epic Link: Quota Endpoints
• Sprint: Mesosphere Sprint 26
• Story Points: 1
• Assignee: Alex R
• Reporter: Alex R
• Shepherd: Joris Van Remoortere
• Created: 03/Dec/15 16:39
• Updated: 26/Nov/18 12:21
• Resolved: 26/Nov/18 12:21

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?