Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Tue, 1 Sep 2015 03:21:46 +0000 (UTC)
From: "Guangya Liu (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12849022.1437774809000.217921.1441077706039@Atlassian.JIRA>
In-Reply-To: <JIRA.12849022.1437774809000@Atlassian.JIRA>
References: <JIRA.12849022.1437774809000@Atlassian.JIRA>
 <JIRA.12849022.1437774809400@arcas>
Subject: [jira] [Updated] (MESOS-3147) Allocator refactor
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Guangya Liu updated MESOS-3147:
-------------------------------
    Shepherd: Alexander Rukletsov

> Allocator refactor
> ------------------
>
>                 Key: MESOS-3147
>                 URL: https://issues.apache.org/jira/browse/MESOS-3147
>             Project: Mesos
>          Issue Type: Task
>          Components: allocation, master
>            Reporter: Michael Park
>            Assignee: Guangya Liu
>              Labels: mesosphere, tech-debt
>
> With new features such as dynamic reservation, persistent volume, quota, optimistic offers, it has been apparent that we need to refactor the allocator to
> 1. solidify the API (e.g. consolidate {{updateSlave}} and {{updateAvailable}})
> 2. possibly move the offer generation to the allocator from the master
> 3. support for allocator modules where the API involves returning {{libprocess::Future}}
> The sequence of implementation challenges for dynamic reservation master endpoints are captured in [this document|https://docs.google.com/document/d/1cwVz4aKiCYP9Y4MOwHYZkyaiuEv7fArCye-vPvB2lAI/edit?usp=sharing].


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