reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Weimer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1222) Support a plugin model in REEF
Date Fri, 26 Feb 2016 02:29:18 GMT

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

Markus Weimer commented on REEF-1222:
-------------------------------------

It is a step further than Services. Services (both Driver and Evaluator) provide the needed
API hooks for plugins. However, we don't have a way to materialize them. For instance, we
today require a developer of a REEF application to enumerate all the needed configurations,
assemblies and such as part of their Driver submission. It would be nice to be able to have
a file format and mechanism for all this to be automated. For instance a ZIP archive which
contains all the assemblies as well as the configuration for a Service. That archive is then
automatically picked up by the Driver, if it is found in a certain spot.

> Support a plugin model in REEF
> ------------------------------
>
>                 Key: REEF-1222
>                 URL: https://issues.apache.org/jira/browse/REEF-1222
>             Project: REEF
>          Issue Type: New Feature
>          Components: REEF
>            Reporter: Eran Shamir
>            Priority: Minor
>
> As REEF grows in functionality, it can benefit from having support for discrete extension
units (plugins) - these will be self describing and will be allowed to register in the system
and integrate into the execution pipeline. This will allow different functionalities to be
added to the product without changing the base semantic/offering. A plugin model will also
simplify code management as it will be separated into the core framework and the various plugins.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message