[MESOS-8968] Wire `UPDATE_QUOTA` call.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.9.0
• Labels: Quota allocator multitenancy
• Epic Link: Quota Limits
• Sprint: Resource Mgmt: RI-16 Sp 50, Resource Mgmt: RI-16 51
• Story Points: 5
• Assignee: Meng Zhu
• Reporter: Meng Zhu
• Created: 30/May/18 23:17
• Updated: 23/Jul/19 22:08
• Resolved: 23/Jul/19 22:08

Description

Wire the existing master, auth, registar, and allocator pieces together to complete the `UPDATE_QUOTA` call.

This would enable the master capability `QUOTA_V2`.

This also fixes the "ignoring zero resource quota" bug in the old quota implementation, namely:

Currently, Mesos discards resource object with zero scalar value when parsing resources. This means quota set to zero would be ignored and not enforced. For example, role with quota set to "cpu:10;mem:10;gpu:0" intends to get no GPU. Due to the above issue, the allocator can only see the quota as "cpu:10;mem:10", and no quota GPU means no guarantee and NO limit. Thus GPUs may still be allocated to this role.

With the completion of `UPDATE_QUOTA` which takes a map of name, scalar values, zero value will no longer be dropped.

Issue Links

• relates to: MESOS-8945 Master check failure due to CHECK_SOME(providerId).