[
https://issues.apache.org/jira/browse/MESOS-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285411#comment-14285411
]
Alexander Rukletsov commented on MESOS-2213:
--------------------------------------------
https://reviews.apache.org/r/29890/
https://reviews.apache.org/r/29925/
https://reviews.apache.org/r/29927/
https://reviews.apache.org/r/29929/
https://reviews.apache.org/r/29931/
https://reviews.apache.org/r/30082/
https://reviews.apache.org/r/29932/
> Custom allocators should implement Allocator instead of AllocatorProcess
> ------------------------------------------------------------------------
>
> Key: MESOS-2213
> URL: https://issues.apache.org/jira/browse/MESOS-2213
> Project: Mesos
> Issue Type: Task
> Components: allocation
> Reporter: Alexander Rukletsov
> Assignee: Alexander Rukletsov
> Labels: mesosphere
>
> Currently new allocation policies can be added by implementing
> {{AllocatorProcess}} interface, while {{Allocator}} class is a thin wrapper
> around it. This architecture may be not very favourable, because it imposes
> restriction on how allocators should be implemented. Additionally, the
> current design is not consistent with other pluggable—or potentially
> pluggable—Mesos components, e.g. {{Isolator}}, {{Authenticator}}.
> As we are moving to modularizing the allocator, this ticket aims to change
> the way we implement allocation policies and instantiate allocators.
> Allocator tests and {{MockAllocatorProcess}} will be affected as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
