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

Andrei Savu commented on WHIRR-49:
----------------------------------

+1 looks great and integration tests passing on aws-ec2 (without the change 
from WHIRR-410 - it seems like the 32bit AMI is now working as expected). Alex, 
Tom, Jeff any feedback to add before David can commit the patch? 
                
> 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
>            Assignee: David Alves
>         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, 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

        

Reply via email to