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

Chad Metcalf commented on WHIRR-385:
------------------------------------

How about a brain dead httpd and ntp example?

{code}
whirr.cluster-name=puppettest

puppet.httpd.module-dir=git://github.com/metcalfc/puppet-httpd.git
puppet.ntp.module-dir=git://github.com/puppetlabs/puppetlabs-ntp.git
puppet.ntp.servers=[ '0.pool.ntp.org' ]
puppet.ntp.autoupdate=true

whirr.instance-templates=1 puppet:httpd+puppet:ntp
whirr.firewall.rules=80

whirr.provider=${sys:whirr.test.provider}
whirr.identity=${sys:whirr.test.identity}
whirr.credential=${sys:whirr.test.credential}
whirr.hardware-min-ram=1024  
{code}

Curl localhost:80 should work and testing ntp could be as easy as grepping 
{{/etc/ntp.conf}} for "pool.ntp.org".

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