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

Michael Park updated MESOS-3147:
--------------------------------
    Description: 
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].

  was:
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

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].


> 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
>              Labels: mesosphere
>
> 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)

Reply via email to