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

Adrian Cole commented on WHIRR-385:
-----------------------------------

I can get the patch to apply, and start via cli.  Socket is open, but curl 
seems to be hanging.  Can someone who knows puppet try and figure out what 
might be wrong with the setup?  Maybe we are missing attribs.

# build with patch
patch -p0 --input /path/to/WHIRR-385.patch
mvn clean install -Dmaven.javadoc.skip=true eclipse:eclipse
mvn package assembly:assembly -Dmaven.javadoc.skip=true

# setup ec2 creds
export AWS_ACCESS_KEY_ID=...
export AWS_SECRET_ACCESS_KEY=...

# run cluster
bin/whirr launch-cluster --config recipes/puppet-nginx-ec2.properties 

# test cluster
for I in `awk '{print $3}' ~/.whirr/nginx/instances`;do nc $I 80 && echo socket 
$I 80 ok|| echo socket $I 80 timeout;curl --connect-timeout 1 --max-time 1 
--silent http://$I >/dev/null 2>&1&& echo http://$I ok|| echo http://$I 
timeout;done

# shutdown cluster
bin/whirr launch-cluster --config recipes/puppet-nginx-ec2.properties 


Note that when the cluster is running, you can ssh into the instance as your 
default user to look around

> Implement support for using nodeless, masterless Puppet to provision and run 
> scripts
> ------------------------------------------------------------------------------------
>
>                 Key: WHIRR-385
>                 URL: https://issues.apache.org/jira/browse/WHIRR-385
>             Project: Whirr
>          Issue Type: New Feature
>          Components: new service
>    Affects Versions: 0.7.0
>            Reporter: Alex Heneveld
>         Attachments: WHIRR-385-results-aws-ec2.txt, 
> WHIRR-385-results-cloudservers-us.txt, WHIRR-385.patch, WHIRR-385.patch, 
> WHIRR-385.patch, WHIRR-385.patch, WHIRR-385.patch, WHIRR-385.patch, 
> WHIRR-385.patch
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> As a user of Whirr, I'd like to be able to use puppet scripts (manifests, 
> modules) from within Whirr to set up machines and clusters, because there are 
> a lot of OS-neutral capabilities and a large number of actively maintained 
> scripts which I could benefit from.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to