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

Bernd Mathiske edited comment on MESOS-1384 at 9/18/14 7:57 PM:
----------------------------------------------------------------

[~tstclair] Thanks for the vote of confidence! We can a code improvement pass 
now and also remove non-essentials to get to a minimal viable first patch. 

However, we still have to solve the question what the command line interface 
should look like. Go for JSON right away? On the command line? Or maybe this: 
keep the simple format (<lib path>:<module name>,...) we have right now and 
also add a second flag that points at a JSON file? 





was (Author: bernd-mesos):
[~tstclair] Thanks for the vote of confidence! We will can a code improvement 
pass now and also remove non-essentials to get to a minimal viable first patch. 

However, we still have to solve the question what the command line interface 
should look like. Go for JSON right away? On the command line? Or maybe this: 
keep the simple format (<lib path>:<module name>,...) we have right now and 
also add a second flag that points at a JSON file? 




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

Reply via email to