[
https://issues.apache.org/jira/browse/WHIRR-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108039#comment-13108039
]
Andrei Savu commented on WHIRR-385:
-----------------------------------
+1 by looking at the code (I haven't tried running the tests). I think it's
safe to commit if the tests are passing both on cloudservers and ec2 and we can
fix any remaining issues in follow-up JIRAs. I'm excited about this change!
> 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, 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
