…unning around the chef world can sort out
* 'master' of github.com:infochimps-labs/ironfan: Removing completed TODO items related to Cluster Chef -> Ironfan rename Removing completed TODO item From conversation with Flip: the remainder of #81 should be a TODO item, not an issue Make ironfan work with string (in addition to array) for cluster_path, to conform to chef semantics (fixes #130)
…tion AMI that mostly works. Have initial work to allow placement group specification, but unfortunately Fog is not passign things through correctly, will have to dive in and figure that out. sigh.
…' method, that deals with the four different ways you need to try to get fog to give you a hostname. Moved ssh commands to it, including a fallback to a fifth option that only makes sense int he ssh context
… and forcefully remove the obsolete chef package if it's present
…, to conform to chef semantics (fixes #130)
…ady been authorized' error, just do a log.debug message. Other errors still get a ui.warn. Also made knife cluster stop and knife cluster kill more descriptive about their eschewal of 'permanent=true' servers
…ty groups, fixes #86
… other commands will run something
…ash <<EOF, or else env vars are interpolated before the script can run. I'm unable to tell if this ever worked or if something in chef's handling of bootstrap scripts changed.
…e cluster shell banner Conflicts: lib/chef/knife/cluster_launch.rb