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

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

We talked about the syntax for module branches being:

{code}
[email protected]/puppetlabs/puppet-ntp.git
puppet.ntp.module.branch=notmaster
{code}

Did that make it in? I looked over the patch and didn't find on a first glance.

> 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