You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "David Alves (JIRA)" <ji...@apache.org> on 2011/08/27 01:47:29 UTC

[jira] [Issue Comment Edited] (WHIRR-49) Allow Whirr to use Chef for configuration management

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

David Alves edited comment on WHIRR-49 at 8/26/11 11:46 PM:
------------------------------------------------------------

Installs ruby & chef-solo. RPM distros not yet complete. Tested and working on rackspace.
After the chef "service" is boostrapped other servers should be able to do stuff like:

Recipe mysql = new Recipe("mysql); 
addStatement(event,mysql.asStatement());

      was (Author: dr-alves):
    Installs ruby & chef-solo. RPM distros not yet complete. Tested and working on rackspace
  
> 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.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira