[ 
https://issues.apache.org/jira/browse/BIGTOP-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486726#comment-13486726
 ] 

Bruno Mahé commented on BIGTOP-730:
-----------------------------------

* Note that there quite a few references to Cloudera (or internal services of 
Cloudera) which should be removed. Also references to CDH should be replaced by 
references to Apache Bigtop.

* In 
bigtop-test-framework/src/main/groovy/org/apache/bigtop/itest/pmanager/PackageInstance.groovy,
 I would rather put the RPM in its own case and error out for the default case.

* Status command of the TarService is still using the service command

* 
bigtop-tests/test-artifacts/package/src/main/resources/tar/config/hbase/hbase-site.xml
 doesn't seem right


Other than that, this patch makes sense.
                
> add tarball driver into Bigtop
> ------------------------------
>
>                 Key: BIGTOP-730
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-730
>             Project: Bigtop
>          Issue Type: New Feature
>          Components: Deployment
>    Affects Versions: 0.5.0
>            Reporter: Johnny Zhang
>            Assignee: Johnny Zhang
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-730.txt
>
>
> We should have a tarball driver for each component, it will be:
> * convenient for people to deploy tarball to run map reduce job in a single VM
> * Whirr is only for EC2, but we want this tarball driver be generic for Linux 
> user.
> * driver should deploy Hadoop tarball by default when deploy other tarball 
> like Hive tarball, or Pig tarball
> * driver should be able to deploy multiple projects. For example, if user 
> choose Hive+Pig, then driver will deploy Hadoop tarball + both Hive,Pig 
> tarball
> * The version of each project tarball will be same as the version of project 
> Bigtop 0.5 shipped
> I already have a prototype, and I am thinking about where to put it and a 
> suitable way to invoke it as a user.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to