[
https://issues.apache.org/jira/browse/SLIDER-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388852#comment-14388852
]
thomas liu edited comment on SLIDER-773 at 4/7/15 6:48 PM:
-----------------------------------------------------------
How to package and submit add on packages:
When users would like to submit an application composed of master package and
add on packages, they need to provide the master package(the existing
application package) without modification as it is, and also the add on
packages. The addon packages can be created the same way as master package. For
submission, they still use 'slider create' command, with additional parameters:
--addon <package name> <package zip file location in local FS>. The detail of
packaging, especially the schema of appConfig.json, metainfo.json are defined
in https://issues.apache.org/jira/browse/SLIDER-834
Current design:
We are not modifying the basic architecture of Slider, either how SliderAgent
communicate with SliderAM. We modify the state machine in AgentProviderService
to issue INSTALL commands for add on packages. Details here:
https://issues.apache.org/jira/browse/SLIDER-820
was (Author: thomas_liu):
How to package and submit add on packages:
Users need to create Slider application package for addon packages in a way
similar to master package. The detail of packaging, especially the schema of
appConfig.json, metainfo.json are defined in
https://issues.apache.org/jira/browse/SLIDER-834
Current design:
We are not modifying the basic architecture of Slider, either how SliderAgent
communicate with SliderAM. We modify the state machine in AgentProviderService
to issue INSTALL commands for add on packages. Details here:
https://issues.apache.org/jira/browse/SLIDER-820
> Add co-processor support for app packages
> -----------------------------------------
>
> Key: SLIDER-773
> URL: https://issues.apache.org/jira/browse/SLIDER-773
> Project: Slider
> Issue Type: Bug
> Components: app-package, client
> Affects Versions: Slider 0.60
> Reporter: Sumit Mohanty
> Assignee: thomas liu
> Priority: Critical
> Fix For: Slider 0.80
>
> Attachments: Co-processorSupport.pdf, coprocessor-apri-4th.patch
>
>
> It is typical for applications to allow plugins/co-processors that are
> essentially a set of additional jar files in the classpath and optionally a
> set of config files or config changes.
> Current, slider app packages can handle additional config changes/entries
> very well. Additional configs files can be added as well but it is not easy
> if the config files include parameters that need to be resolved by the agent.
> This requires app package changes. Dropping additional jar files into the
> class path is not easy and requires app package changes.
> It is not efficient to modify the app package to support such plugins. App
> packaging and create command should be modified such that the user can
> dynamically specify additional jars, config files, configs etc.
> Specific scenarios are modifying HBase to add support for Phoenix or Ranger.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
