[
https://issues.apache.org/jira/browse/SLIDER-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14483765#comment-14483765
]
thomas liu edited comment on SLIDER-834 at 4/7/15 10:50 PM:
------------------------------------------------------------
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,
which is composed of:
metainfo.json/xml
package folder
package/script folder, in which they provide python scripts similar to those in
the master package to instruct Slider how to install/configure the addon
package.
They should be zipped the same way as the master package.
So now the user have:
appConfig.json
resources.json
master package zip file
addon package zip file
Now when the users submit the application, they still use 'slider create'
command, with additional parameters: --addon <package name> <package zip file
location in local FS>.
For example: if they want to submit an HBASE application with Phoenix and
Ranger, they need to call:
slider create hbase01 --template /Users/yarn/app/hbase/appConfig-default.json
--resources /Users/yarn/app/hbase/resources-default.json --addon PHOENIX
/Users/yarn/app/phoenix/Archive.zip --addon RANGER
/Users/yarn/app/ranger/Archive.zip
And that's all what they need
Given today SliderAM doesn't issue CONFIGURE commands to SliderAgent, users can
choose to perform CONFIGURE tasks inside INSTALL. Or they can still define
CONFIGURE command in their python scripts of the add on package and call it
from INSTALL command in the python scripts
was (Author: thomas_liu):
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,
which is composed of:
metainfo.json/xml
package folder
package/script folder, in which they provide python scripts similar to those in
the master package to instruct Slider how to install/configure the addon
package.
They should be zipped the same way as the master package.
So now the user have:
appConfig.json
resources.json
master package zip file
addon package zip file
Now when the users submit the application, they still use 'slider create'
command, with additional parameters: --addon <package name> <package zip file
location in local FS>.
For example: if they want to submit an HBASE application with Phoenix and
Ranger, they need to call:
slider create hbase01 --template /Users/yarn/app/hbase/appConfig-default.json
--resources /Users/yarn/app/hbase/resources-default.json --addon PHOENIX
/Users/yarn/app/phoenix/Archive.zip --addon RANGER
/Users/yarn/app/ranger/Archive.zip
And that's all what they need
> Read addon package configurations in appConfig.json and metainfo.json into
> AgentProviderService
> -----------------------------------------------------------------------------------------------
>
> Key: SLIDER-834
> URL: https://issues.apache.org/jira/browse/SLIDER-834
> Project: Slider
> Issue Type: Sub-task
> Components: app-package, client
> Reporter: thomas liu
> Fix For: Slider 0.80
>
>
> Example metainfo.xml/json schema:
> <metainfo>
> <schemaVersion>2.0</schemaVersion>
> <applicationPackage>
> <name>PHOENIX</name>
> <comment>
> Apache Phoenix is
> </comment>
> <version>2.0</version>
> <type>ADDON-PACKAGE</type>
> <minHadoopVersion>1.0</minHadoopVersion>
>
> <components>
> <component>
> <name>HBASE_REST</name> ----- this add on package should
> be applied to hbase_rest component
> <commandScript>
> <script>scripts/addon_hbase_rest.py</script> ----- location of
> the script to be used by Slider in zip file/package
> <scriptType>PYTHON</scriptType>
> <timeout>600</timeout>
> </commandScript>
> </component>
> <component>
> <name>HBASE_MASTER</name> ----- this add on package should be
> applied to hbase_master component
> <commandScript>
> <script>scripts/addon_hbase_master.py</script> -----location of the
> script to be used by Slider in zip file/package
> <scriptType>PYTHON</scriptType>
> </commandScript>
> </component>
> </components>
> </applicationPackage>
> </metainfo>
> Another example:
> <metainfo>
> <schemaVersion>2.0</schemaVersion>
> <applicationPackage>
> <name>RANGER</name>
> <comment>
> Apache RANGER is
> </comment>
> <version>2.0</version>
> <type>ADDON-PACKAGE</type>
> <minHadoopVersion>1.0</minHadoopVersion>
>
> <components>
> <component>
> <name>ALL</name> ----- this add on package should be applied to all
> components
> <commandScript>
> <script>scripts/all.py</script>
> <scriptType>PYTHON</scriptType>
> <timeout>600</timeout>
> </commandScript>
> </component>
> </components>
> </applicationPackage>
> </metainfo>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
