whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrei Savu (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WHIRR-434) Tool for patch testing on aws-ec2
Date Wed, 07 Dec 2011 16:30:40 GMT

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

Andrei Savu commented on WHIRR-434:
-----------------------------------

+1 for build-tools/remote-test + a readme with instructions
                
> Tool for patch testing on aws-ec2
> ---------------------------------
>
>                 Key: WHIRR-434
>                 URL: https://issues.apache.org/jira/browse/WHIRR-434
>             Project: Whirr
>          Issue Type: Improvement
>            Reporter: Andrei Savu
>         Attachments: patch-whirr.sh, setup-whirr.sh, test-whirr-service.sh
>
>
> Some time ago Adrian created a tool for testing on aws-ec2. I'm creating this issue because
I think we should have that in version control. 
> This is the original message on the email list:
> Sometimes it is tough to reproduce test success or failure since one's
> workspace might be tainted.  The following is a process I used to test
> a patch running against zookeeper on aws-ec2.  It first creates a
> fresh node to perform tests on, then runs the integration test against
> zookoeeper.
> Here's the steps:
>  * preparation
>    checkout and mvn install
> https://github.com/jclouds/jclouds-examples/tree/master/compute-basics
>  * setup a new node with whirr and maven:
>    create a m1.small node on aws-ec2 with the following command:
>         java -DminRam=1024 -jar
> target/compute-basics-jar-with-dependencies.jar aws-ec2 ACCESS SECRET
> whirrtest
>    setup whirr from a clean svn checkout
>         java -jar target/compute-basics-jar-with-dependencies.jar
> aws-ec2 ACCESS SECRET whirrtest run /path/to/setup-whirr.sh
>  * iterate a patch, testing against a live service
>    if you are testing a patch, apply it with the patch-script after
> you changed it to use the correct url for the patch you wish to test
>         java -jar target/compute-basics-jar-with-dependencies.jar
> aws-ec2 ACCESS SECRET whirrtest run /path/to/patch-whirr.sh
>    modify test-whirr-service with the config params you want and the
> cloud you are testing against and then run it, repeating as necessary
>         java -jar target/compute-basics-jar-with-dependencies.jar
> aws-ec2 ACCESS SECRET whirrtest run /path/to/test-whirr-service.sh
>  * cleanup your node!
>     java -jar target/compute-basics-jar-with-dependencies.jar aws-ec2
> ACCESS SECRET whirrtest destroy
> I hope this helps!
> -Adrian
> ex.
> Adrian-Coles-iMac:compute-basics adriancole$  java  -jar
> target/compute-basics-jar-with-dependencies.jar aws-ec2 ACCESS SECRET
> whirrtest run /Users/adriancole/Desktop/test-whirr-service.sh
> >> initialized provider  [id=aws-ec2, endpoint=https://ec2.us-east-1.amazonaws.com,
apiVersion=2010-06-15, identity=067PW7Z9P0FNH7JDPE82, iso3166Codes=[US-VA, US-CA, IE, SG,
JP-13]]
> >> running [/Users/adriancole/Desktop/test-whirr-service.sh] on group whirrtest
as adriancole
> -  >> blocking on socket [address=174.129.88.111, port=22] for 600000 seconds
> -  << socket [address=174.129.88.111, port=22] opened
> -  >> running [./_test-whirr-service init] as adriancole@174.129.88.111
> -  << init(0)
> -  >> running [./_test-whirr-service start] as adriancole@174.129.88.111
> -  << start(0)
> -  << complete(true)
> -  << stdout from _test-whirr-service as adriancole@174.129.88.111
> [INFO] Installing
> /home/users/adriancole/whirr/services/zookeeper/pom.xml to
> /home/users/adriancole/.m2/repository/org/apache/whirr/whirr-zookeeper/0.7.0-SNAPSHOT/whirr-zookeeper-0.7.0-SNAPSHOT.pom
> [INFO] Installing
> /home/users/adriancole/whirr/services/zookeeper/target/whirr-zookeeper-0.7.0-SNAPSHOT-tests.jar
> to /home/users/adriancole/.m2/repository/org/apache/whirr/whirr-zookeeper/0.7.0-SNAPSHOT/whirr-zookeeper-0.7.0-SNAPSHOT-tests.jar
> [INFO] Installing
> /home/users/adriancole/whirr/services/zookeeper/target/whirr-zookeeper-0.7.0-SNAPSHOT-sources.jar
> to /home/users/adriancole/.m2/repository/org/apache/whirr/whirr-zookeeper/0.7.0-SNAPSHOT/whirr-zookeeper-0.7.0-SNAPSHOT-sources.jar
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 6:12.858s
> [INFO] Finished at: Thu Aug 18 17:22:05 UTC 2011
> [INFO] Final Memory: 28M/247M
> [INFO] ------------------------------------------------------------------------
> -  << stderr from _test-whirr-service as adriancole@174.129.88.111
> << node us-east-1/i-cf0a2fae: [10.116.77.215, 174.129.88.111]
> <<     [output=, error=, exitCode=0]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message