Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Thu, 8 Dec 2016 19:33:58 +0000 (UTC)
From: "Adam B (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12741275.1410635757000.476126.1481225638537@Atlassian.JIRA>
In-Reply-To: <JIRA.12741275.1410635757000@Atlassian.JIRA>
References: <JIRA.12741275.1410635757000@Atlassian.JIRA> <JIRA.12741275.1410635757668@arcas>
Subject: [jira] [Updated] (MESOS-1791) Introduce Master / Offer Resource
 Reservations aka Quota.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 08 Dec 2016 19:34:00 -0000


     [ https://issues.apache.org/jira/browse/MESOS-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam B updated MESOS-1791:
--------------------------
    Fix Version/s:     (was: 1.2.0)
                   1.0.0

> Introduce Master / Offer Resource Reservations aka Quota.
> ---------------------------------------------------------
>
>                 Key: MESOS-1791
>                 URL: https://issues.apache.org/jira/browse/MESOS-1791
>             Project: Mesos
>          Issue Type: Epic
>          Components: allocation, master, replicated log
>            Reporter: Tom Arnfeld
>            Assignee: Alexander Rukletsov
>              Labels: mesosphere
>             Fix For: 1.0.0
>
>
> 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.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)