Running the basic clouds.rb example, looks like a dependency failure over on the deployed host:
...
38 gems installed
174.129.167.165 stderr => ERROR: Error installing thin-1.2.2.gem:
thin requires rack (>= 1.0.0, runtime)
connecting to ssh with options = {:auth_methods=>"publickey", :paranoid=>false, :user=>"root", :keys=>["/Users/cnoshpitz/ws/poolparty/keypairs/clauden-001.pk"], :timeout=>180}
174.129.167.165 stderr => cp: cannot create regular file `/etc/chef/dna.json': No such file or directory
Your cloud has started. Your ip is 174.129.167.165
Sadly, while the cloud was started my customizations were not deployed. Yet there wasn't any meaningful error message. I think this sort of has more to do with poor dependency management by the gem mechanism, but pool party ought to be a bit more diligent.
Running the basic clouds.rb example, looks like a dependency failure over on the deployed host: ... 38 gems installed 174.129.167.165 stderr => ERROR: Error installing thin-1.2.2.gem: thin requires rack (>= 1.0.0, runtime) connecting to ssh with options = {:auth_methods=>"publickey", :paranoid=>false, :user=>"root", :keys=>["/Users/cnoshpitz/ws/poolparty/keypairs/clauden-001.pk"], :timeout=>180} 174.129.167.165 stderr => cp: cannot create regular file `/etc/chef/dna.json': No such file or directory Your cloud has started. Your ip is 174.129.167.165
Sadly, while the cloud was started my customizations were not deployed. Yet there wasn't any meaningful error message. I think this sort of has more to do with poor dependency management by the gem mechanism, but pool party ought to be a bit more diligent.