mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Hindman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-1224) Add dynamic loadable library abstraction to stout.
Date Tue, 29 Apr 2014 21:07:17 GMT

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

Benjamin Hindman commented on MESOS-1224:
-----------------------------------------

We could name the symbols that we want to lookup and pass that to the stout function which
does the load. Then in Mesos we could fix that to a well known name (and/or wrapper).

Also, 'load' is almost more like 'instantiate', since that's what we expect to have happen,
i.e., a 'new' on some type T that gets returned to us.

> 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: Niklas Quarfot Nielsen
>            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)

Mime
View raw message