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

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

thanks for the working configuration, chad!  I updated puppet to run apt-get 
update on install.

I refactored massively so that methods make as much sense as possible, with 
much less cruft.  I also added test cases for nearly all.

note: syntax for module location is puppet.X.module

I tested the following works now, OOB!

* run cluster
bin/whirr launch-cluster --config recipes/puppet-http-ec2.properties
* test cluster
for I in `awk '{print $3}' ~/.whirr/puppettest/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 destroy-cluster --config recipes/puppet-http-ec2.properties

NEXT STEPS:
 - go ahead and re-test, as all is working, now.
 - one last hairy method should be cleaned up: 
CreateSitePpAndApplyRoles.getManifestForClusterSpecAndRole



> 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, 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