[
https://issues.apache.org/jira/browse/MESOS-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146078#comment-14146078
]
Tom Arnfeld commented on MESOS-1791:
------------------------------------
Thanks for the clarification there Adam, hit the nail on the head. I think
you're right that these are two separate things, and we should create separate
JIRA Issues (or subtasks?) for each.
I'm personally more interested in the latter, where all slaves are equal (I
would expect this is a more common use case) and I just need to make sure
Jenkins, for example, has some room to work 24/7.
> Introduce Master / Offer Resource Reservations
> ----------------------------------------------
>
> Key: MESOS-1791
> URL: https://issues.apache.org/jira/browse/MESOS-1791
> Project: Mesos
> Issue Type: Epic
> Reporter: Tom Arnfeld
>
> 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?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
