[
https://issues.apache.org/jira/browse/MESOS-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15276618#comment-15276618
]
Kapil Arya edited comment on MESOS-5173 at 5/26/16 5:59 PM:
------------------------------------------------------------
Added RRs:
https://reviews.apache.org/r/47123 : Added --modules_dir flag
https://reviews.apache.org/r/47905 : Test case added.
https://reviews.apache.org/r/47906 : Documentation updates.
was (Author: karya):
Added RR: https://reviews.apache.org/r/47123/
> Allow master/agent to take multiple modules manifest files
> ----------------------------------------------------------
>
> Key: MESOS-5173
> URL: https://issues.apache.org/jira/browse/MESOS-5173
> Project: Mesos
> Issue Type: Task
> Reporter: Kapil Arya
> Assignee: Kapil Arya
> Priority: Blocker
> Labels: mesosphere
> Fix For: 0.29.0
>
>
> When loading multiple modules into master/agent, one has to merge all module
> metadata (library name, module name, parameters, etc.) into a single json
> file which is then passed on to the --modules flag. This quickly becomes
> cumbersome especially if the modules are coming from different
> vendors/developers.
> An alternate would be to allow multiple invocations of --modules flag that
> can then be passed on to the module manager. That way, each flag corresponds
> to just one module library and modules from that library.
> Another approach is to create a new flag (e.g., --modules-dir) that contains
> a path to a directory that would contain multiple json files. One can think
> of it as an analogous to systemd units. The operator that drops a new file
> into this directory and the file would automatically be picked up by the
> master/agent module manager. Further, the naming scheme can also be inherited
> to prefix the filename with an "NN_" to signify oad order.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)