You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Niklas Quarfot Nielsen (JIRA)" <ji...@apache.org> on 2014/05/01 18:34:15 UTC

[jira] [Updated] (MESOS-1224) Add dynamic loadable library abstraction to stout.

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

Niklas Quarfot Nielsen updated MESOS-1224:
------------------------------------------

    Assignee: Timothy St. Clair  (was: Niklas Quarfot Nielsen)

> Add dynamic loadable library abstraction to stout.
> --------------------------------------------------
>
>                 Key: MESOS-1224
>                 URL: https://issues.apache.org/jira/browse/MESOS-1224
>             Project: Mesos
>          Issue Type: Improvement
>          Components: stout
>            Reporter: Niklas Quarfot Nielsen
>            Assignee: Timothy St. Clair
>            Priority: Minor
>              Labels: extensibility
>             Fix For: 0.19.0
>
>
> Adding a first class primitive, abstraction and process for dynamic library writing and loading can make it easier to extend inner workings of Mesos. Making it possible to have dynamic loadable resource allocators, isolators, containerizes, authenticators and much more.
> I think this could be a powerful feature, as we get even more extensible and flexible ways of setting up Mesos - but also for isolating dependencies and complexity in external libraries and to ease experimentation with new features. For example, imagine a loadable allocators which contains a VM (Lua, Python, ...) which makes it possible to try out new allocator algorithms without forcing those dependencies into the project.
> BenH and I chatted about the concrete details and I will follow up with small write-up/proposal.



--
This message was sent by Atlassian JIRA
(v6.2#6252)