[jira] [Commented] (MESOS-3147) Allocator refactor

["Michael Park (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724713#comment-14724713 ] 

Michael Park commented on MESOS-3147:
-------------------------------------

[~gyliu] This is actually quite a hefty ticket. I'm not sure who will be able to help you shepherd this currently. Perhaps you could work with [~alexr] on this?

> 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)