[SLIDER-777] Provide slider dependencies as a self contained versioned tarball

• Type: New Feature
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Slider 0.70
• Fix Version/s: Slider 0.81
• Component/s: build, client
• Sprint: Slider September #1
• Assignee: Gour Saha
• Reporter: Sumit Mohanty
• Created: 05/Feb/15 22:44
• Updated: 31/Jan/17 17:47
• Resolved: 15/Oct/15 13:49

Description

Currently, slider client picks up all the dependencies from the lib folder. This causes an issue for code that embed Slider client where either they need to specify a folder which has the all the required (but no more) jar files or their own lib directory which contains jar files of the embedding application as well.

Slider should explore (similar to Tez or MR) the possibility of packaging all dependencies into a tarball that can be stored in a version aware fashion in HDFS or local FS.

A Slider client can choose to use a specific version when creating the an instance of an application. Now, it is possible for a client of certain version to create an app using another version of the tarball. This requires further investigation in terms of how easy to debug the issues if there is no compatibility between versions of the client and the tarball.

Issue Links

• incorporates: SLIDER-1126 Include slider-agent.tar.gz in the self contained versioned tarball
• is depended upon by: SLIDER-937 Release Slider 0.81.1
• relates to: SLIDER-1192 Slider Agent tarball should be uploaded to HDFS to avoid client side dependency
• requires: AMBARI-13383 Ambari to install/manage Slider tarball to HDFS