[jira] [Commented] (MESOS-2213) Custom allocators should implement Allocator instead of AllocatorProcess

["Alexander Rukletsov (JIRA)" <ji...@apache.org>]

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

Alexander Rukletsov commented on MESOS-2213:
--------------------------------------------

Commit: 82ad111cc7c2a03abefda56a3134254e2a345bd2 [82ad111]
Author: Alexander Rukletsov <al...@mesosphere.io>
Date: 10 Feb 2015 20:12:54 GMT+1
Committer: Niklas Q. Nielsen <ni...@mesosphere.io>

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