[ 
https://issues.apache.org/jira/browse/WHIRR-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Alves updated WHIRR-49:
-----------------------------

    Attachment: WHIRR-49.patch

ITests are passing on rackspace, any volunteers for ec2?

Changed the spacing.

Uncommented commented out itests by running the recipe scripts directly against 
the ComputeService available from ComputeCache, instead of against 
ClusterController, this way I was able to run recipes as initscripts.

Note: In order for itests to pass I've had to introduce a small (5sec) sleep 
between installing recipes and testing for their installation.

I'm not sure why this is happening. Jclouds script timeout should not be an 
issue here (tests takes  less than the default 10 min timeout). So either 
jclouds is returning before the script is complete or there is some visibility 
issue with chef and/or with script execution visibility in general.

In practice as chef is used to provision stuff for other services this is not 
an issue (i've been provisioning sun's java and postgres through chef without 
problems).
                
> 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, 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