[
https://issues.apache.org/jira/browse/MESOS-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139097#comment-14139097
]
Timothy St. Clair commented on MESOS-1384:
------------------------------------------
Having a pluggable architecture would enable folks to do the following:
1. Test PoC ideas in a clean way without impacting mainline.
2. Enable Service providers to write custom interfaces that may only apply to
their workflow. *This is the big one*
3. Prevents mesos from accreating too much into it's core without having well
thought out boundaries on interfaces and adaptability over time. By forcing
the step, it helps to define clear boundaries.
...
> Add support for loadable MesosModule
> ------------------------------------
>
> Key: MESOS-1384
> URL: https://issues.apache.org/jira/browse/MESOS-1384
> Project: Mesos
> Issue Type: Improvement
> Affects Versions: 0.19.0
> Reporter: Timothy St. Clair
> Assignee: Niklas Quarfot Nielsen
>
> 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.
> -
> *DONE*
> (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.
> *TARGET*
> (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.
> *NEXT*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
