mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niklas Quarfot Nielsen (JIRA)" <>
Subject [jira] [Commented] (MESOS-1384) Add support for loadable MesosModule
Date Tue, 29 Jul 2014 19:58:38 GMT


Niklas Quarfot Nielsen commented on MESOS-1384:

Thanks Bernd - that's one point I didn't touch base on; How do we describe the library paths
to use on start-up?
For example, in the case of isolator modules we want to be able to start with flags like --isolation="cgroups/cpu,module/foobar"
where is located in the default library location. Is that the right way to think
about it? What do we do when users want to define absolute paths to libraries instead? Maybe
--isolation="..., module/path/to/" or module:///path/to/

It is a bit easier to argue about for something like allocator modules, where the --allocator="foobar"
or --allocator="/path/to/"

Would love to get some input here.

> Add support for loadable MesosModule
> ------------------------------------
>                 Key: MESOS-1384
>                 URL:
>             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
> *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.
> (3) After doing (2) for one or two classes in Mesos I think we can formalize the approach
in a "mesos-ified" version of
> *NEXT*

This message was sent by Atlassian JIRA

View raw message