[MESOS-1791] Introduce Master / Offer Resource Reservations aka Quota.

• Type: Epic
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0
• Component/s: allocation, master, replicated log
• Labels: mesosphere
• Epic Name: Quota
• Assignee: Alex R
• Reporter: Tom Arnfeld
• Shepherd: Joris Van Remoortere
• Created: 13/Sep/14 19:15
• Updated: 08/Dec/16 19:33
• Resolved: 31/Oct/16 09:02

Description

Currently Mesos supports the ability to reserve resources (for a given role) on a per-slave basis, as introduced in MESOS-505. This allows you to almost statically partition off a set of resources on a set of machines, to guarantee certain types of frameworks get some resources.

This is very useful, though it is also very useful to be able to control these reservations through the master (instead of per-slave) for when I don't care which nodes I get on, as long as I get X cpu and Y RAM, or Z sets of (X,Y).

I'm not sure what structure this could take, but apparently it has already been discussed. Would this be a CLI flag? Could there be a (authenticated) web interface to control these reservations?

Follow up epic: MESOS-6514.

Issue Links

• blocks: MESOS-6514 Improvements to quota.
• contains: MESOS-3202 Avoid role/framework offer starvation in DRF allocator.
• is blocked by: MESOS-3073 Introduce HTTP endpoints for Quota
• is related to: MESOS-2018 Dynamic Reservation
• relates to: MESOS-3202 Avoid role/framework offer starvation in DRF allocator.
• relates to: MESOS-3068 Registry operations are hardcoded for a single key (Registry object)