[jira] [Updated] (BIGTOP-1449) Add RC Testing support to vagrant recipe

["jay vyas (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BIGTOP-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jay vyas updated BIGTOP-1449:
-----------------------------
    Description: 
We can automatically set up vagrant to install a release candidate on n nodes and  run smoke tests.  Here is how .

1) Adding the bigtop folder as a shared folder in Vagrantfile, so that VMs have access to bigtop  source
{noformat}
   # the bigtop puppet recipes
   bigtop_puppet = "../../puppet"
-
+  bigtop_home =   "../../../"
 {noformat}

2) {{sudo puppet apply --modulepath=./ -e "include bigtop_toolchain::gradle && alias gradle=/usr/local/gradle/bin/gradle"}}

3) Having the bigtop repo in Vagrantfile point at the RC url. 

4) Export HADOOP_CONF_DIR, BIGTOP_HOME,HADOOP_MAPRED_HOME.

5) Ensure that a home dir exists for the user (i.e. {{/user/vagrant}} )
5) Running the tests {{ cd bigtop-tests/smoke-tests/ && gradle compileGroovy test -Dsmoke-tests=mapreduce--info }} 

Might as well do it so that for next release,  we can automate testing of bigtop on n-node clusters.

When doing this task, lets also update {{smoke-tests}} and (1) fix the README (it sais smoke-tests, instead of smoke.tests) (2) parameterize ITest .  Those are both needed for proper automation of RC testing.

Then, next time an RC comes out, to test, we just update number of nodes and run "vagrant up".  
 

  was:
We can automatically set up vagrant to install a release candidate on n nodes and  run smoke tests.  Here is ho .

1) Adding the bigtop folder as a shared folder in Vagrantfile, so that VMs have access to bigtop  source
{noformat}
   # the bigtop puppet recipes
   bigtop_puppet = "../../puppet"
-
+  bigtop_home =   "../../../"
 {noformat}

2) {{sudo puppet apply --modulepath=./ -e "include bigtop_toolchain::gradle && alias gradle=/usr/local/gradle/bin/gradle"}}

3) Having the bigtop repo in Vagrantfile point at the RC url. 

4) Export HADOOP_CONF_DIR, BIGTOP_HOME,HADOOP_MAPRED_HOME.

5) Ensure that a home dir exists for the user (i.e. {{/user/vagrant}} )
5) Running the tests {{ cd bigtop-tests/smoke-tests/ && gradle compileGroovy test -Dsmoke-tests=mapreduce--info }} 

Might as well do it so that for next release,  we can automate testing of bigtop on n-node clusters.

When doing this task, lets also update {{smoke-tests}} and (1) fix the README (it sais smoke-tests, instead of smoke.tests) (2) parameterize ITest .  Those are both needed for proper automation of RC testing.

Then, next time an RC comes out, to test, we just update number of nodes and run "vagrant up".  
 


> Add RC Testing support to vagrant recipe
> ----------------------------------------
>
>                 Key: BIGTOP-1449
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1449
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: vm
>    Affects Versions: 0.9.0
>            Reporter: jay vyas
>
> We can automatically set up vagrant to install a release candidate on n nodes and  run smoke tests.  Here is how .
> 1) Adding the bigtop folder as a shared folder in Vagrantfile, so that VMs have access to bigtop  source
> {noformat}
>    # the bigtop puppet recipes
>    bigtop_puppet = "../../puppet"
> -
> +  bigtop_home =   "../../../"
>  {noformat}
> 2) {{sudo puppet apply --modulepath=./ -e "include bigtop_toolchain::gradle && alias gradle=/usr/local/gradle/bin/gradle"}}
> 3) Having the bigtop repo in Vagrantfile point at the RC url. 
> 4) Export HADOOP_CONF_DIR, BIGTOP_HOME,HADOOP_MAPRED_HOME.
> 5) Ensure that a home dir exists for the user (i.e. {{/user/vagrant}} )
> 5) Running the tests {{ cd bigtop-tests/smoke-tests/ && gradle compileGroovy test -Dsmoke-tests=mapreduce--info }} 
> Might as well do it so that for next release,  we can automate testing of bigtop on n-node clusters.
> When doing this task, lets also update {{smoke-tests}} and (1) fix the README (it sais smoke-tests, instead of smoke.tests) (2) parameterize ITest .  Those are both needed for proper automation of RC testing.
> Then, next time an RC comes out, to test, we just update number of nodes and run "vagrant up".  
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)