[SLIDER-773] Add co-processor support for app packages

• Type: New Feature
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Slider 0.60
• Fix Version/s: Slider 0.80
• Component/s: app-package, client
• Sprint: Slider April #1
• Assignee: thomas liu
• Reporter: Sumit Mohanty
• Created: 02/Feb/15 16:51
• Updated: 15/May/15 19:05
• Resolved: 05/May/15 05:21

Description

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.

Issue Links

• relates to: SLIDER-757 Add Additional Resources

Sub-Tasks

• Define new fields in communication between AgentProviderService and SliderAgent to indicate multiple addon packages: Resolved
• Enable AgentProviderService issue INSTALL and CONFIGURE command for addon packages: Resolved
• Enable SliderAgent to receive INSTALL and CONFIGURE commands for both master package and addon package: Resolved
• Read addon package configurations in appConfig.json and metainfo.json into AgentProviderService: Resolved
• Add unit and functional test cases for App packages: Resolved