[
https://issues.apache.org/jira/browse/WHIRR-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095559#comment-13095559
]
David Alves commented on WHIRR-49:
----------------------------------
I chased it down and turns out this is not an EC2 problem.
Let me explain the problem:
cookbooks are provided to chef by downloading directly from the opscodes git
repo.
Whenever chef bootstraps it actually runs a portion of every cookbook is its
cookbooks path.
When I first started this bootstrap failed because of two cookbooks (openldap
and windows) failed and therefore nothing else could proceed.
I solved this problem by removing said cookbooks elegantly (rm -rf) but now it
turns out there is a new cookbook on the repo (iis) and it depends on one of
those that were removed (windows).
I will again solve the problem elegantly (rm -rf) but this may not be the best
approach.
What do you think we can do?
- bind the git clone to a specific version we know works?
- download the entire cookbook set and keep in whirr, upgrading it periodically.
- leave as is and solve the problem whenever it occurs?
> 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, 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
