mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niklas Quarfot Nielsen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-2213) Custom allocators should implement Allocator instead of AllocatorProcess
Date Fri, 06 Feb 2015 16:32:34 GMT

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

Niklas Quarfot Nielsen updated MESOS-2213:
------------------------------------------
    Sprint: Mesosphere Q1 Sprint 3 - 2/20

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

Mime
View raw message