mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Drake (JIRA)" <>
Subject [jira] [Commented] (MESOS-1791) Introduce Master / Offer Resource Reservations
Date Fri, 27 Feb 2015 03:51:04 GMT


Chris Drake commented on MESOS-1791:

Could this feature be used by the master(s) to keep track of a central resource such as software

Let's say you only have ten licenses to run a batch execution of some commercial CAD software
that uses FlexLM to limit the number of instances you can run at once. That resource doesn't
belong to any slave, but we need the system to keep track of it nevertheless. Also need the
ability to modify that value w/o shutting down the server if licenses expire or you buy new

> Introduce Master / Offer Resource Reservations
> ----------------------------------------------
>                 Key: MESOS-1791
>                 URL:
>             Project: Mesos
>          Issue Type: Epic
>            Reporter: Tom Arnfeld
>              Labels: mesosphere
> 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

This message was sent by Atlassian JIRA

View raw message