You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2014/09/16 05:51:33 UTC
[jira] [Updated] (AMBARI-7321) Slider view: Iron out story on how
app-packages are deployed and instances created
[ https://issues.apache.org/jira/browse/AMBARI-7321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Srimanth Gunturi updated AMBARI-7321:
-------------------------------------
Attachment: AMBARI-7321.patch
Review at https://reviews.apache.org/r/25680/
> Slider view: Iron out story on how app-packages are deployed and instances created
> ----------------------------------------------------------------------------------
>
> Key: AMBARI-7321
> URL: https://issues.apache.org/jira/browse/AMBARI-7321
> Project: Ambari
> Issue Type: Bug
> Components: contrib
> Affects Versions: 1.7.0
> Reporter: Srimanth Gunturi
> Assignee: Srimanth Gunturi
> Fix For: 1.7.0
>
> Attachments: AMBARI-7321.patch
>
>
> Currently we expect an app-package (say hbase-0.98.zip) to be in _/user/yarn_ folder. Also, the appConfig.json file used to create an instance has to have the {{"application.def": "hbase-v098.zip"}}.
> We need to determine how the app-pkgs end up on ambari-server, how they then end up on HDFS, and how the file names are set in appConfig.json
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)