[
https://issues.apache.org/jira/browse/MESOS-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986733#comment-13986733
]
Benjamin Hindman commented on MESOS-1224:
-----------------------------------------
I think we should break this into multiple phases.
(1) Let's get the dynamic library loading via a "stout-ified" version of
https://github.com/timothysc/tests/blob/master/plugin_modules/DynamicLibrary.h.
(2) Use (1) to instantiate some classes in Mesos (like an Authenticator and/or
isolator) from a dynamic library. This will give us some more experience with
how we want to name the underlying library symbol, how we want to specify flags
for finding the library, what types of validation we want when loading a
library.
(3) After doing (2) for one or two classes in Mesos I think we can formalize
the approach in a "mesos-ified" version of
https://github.com/timothysc/tests/blob/master/plugin_modules/MesosModule.h.
Perhaps this was already your plan but I think this will accelerate the review
process. Thanks [~tstclair] and [~nnielsen]!
> 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)
