[
https://issues.apache.org/jira/browse/MESOS-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344721#comment-14344721
]
Adam B commented on MESOS-1791:
-------------------------------
Excellent question [~cjdrake]. We've previously discussed "cluster-wide
resources" as a separate feature that could also include NAS/SAN
bandwidth/quota or a pool of available IPs; generally speaking, a resource (or
set of resources) that is not tied to a slave, but can be consumed by tasks
(and released when they complete).
These cluster-wide resources do not require any master/offer reservation
features, although they should be able to be reserved by a framework just the
same as any other resource type.
In order to add these cluster-wide resources, we could have some non-slave
"resource provider" register with the Mesos master and advertise its
cluster-wide resources, and then the master could offer these cluster-wide
resources in any offer, regardless of slave.
> 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
> 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 reservations?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
