[
https://issues.apache.org/jira/browse/WHIRR-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133706#comment-13133706
]
David Alves commented on WHIRR-49:
----------------------------------
The commented out tests refer to testing using recipes outside of handlers,
which can come in handy (I use them).
The thing is that recipe scripts should run as initscript by jclouds, and this
requires an additional method on ClusterController, which Adrian implemented
and that I have but should probably go on another jira.
When/If this method is available we can uncomment the test, I just didn't want
to loose the code.
I'll change the formatter setup for whirr, to comply, thank you.
Moving common scripts to services/common seems like a nice idea, but we could
probably do it form another jira, right?
> Allow Whirr to use Chef for configuration management
> ----------------------------------------------------
>
> Key: WHIRR-49
> URL: https://issues.apache.org/jira/browse/WHIRR-49
> Project: Whirr
> Issue Type: New Feature
> Components: core
> Reporter: Jeff Hammerbacher
> Attachments: WHIRR-49-cc.patch, WHIRR-49-pom.patch, WHIRR-49.patch,
> WHIRR-49.patch, WHIRR-49.patch, WHIRR-49.patch, WHIRR-49.patch,
> WHIRR-49.patch, WHIRR-49.patch, WHIRR-49.patch, WHIRR-49.patch, WHIRR-49.patch
>
>
> As discussed in
> https://cwiki.apache.org/confluence/display/WHIRR/WhirrDesign, Whirr should
> be agnostic to the tool used to bring the images up to a state where they're
> ready to run the service.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
