> 2. Do not run Whirr as root. Create a non root account to run > whirr**** > > You can run Whirr as root if you want but you have to specify a > different value for whirr.cluster-user **** > > See http://whirr.apache.org/docs/0.6.0/configuration-guide.html **** > > **** > > We tried it, but this did not work for us. Also, from the documentation it > is not clear what valid values for the whirr.cluster-user are. Can you just > put any string ‘sample’, or must it be an existing user somewhere... > Running whirr as non root avoids the whole issue. >
whirr.cluster-user should be a valid linux user name that doesn't exist on the remote machine. > **** > > 3. Make sure that the machine running whirr can be reached from > the created cloud nodes.**** > > This is not a requirement. **** > > ** ** > > I am not a whirr novice, so maybe you are right. But for us, trying to > setup a cluster from behind a firewall (machine can go out, but not > vice-versa) failed consistently. Are you really sure about this? Could it > be that the hadoop recipe has additional requirements? Fact is that it > started working for us when we moved to a machine that could be reached > from the created nodes. > I always run Apache Whirr tests behind a NAT or / and firewall. Maybe your firewall does some sort of filtering or connection throttling. > ** > > In 0.7.0 (coming soon) we have improved the configuration page by > documenting some jclouds specific options relevant to this issue. Expect > more improvements in 0.8.0 thanks to changes in the upcoming jclouds 1.2.2 > release.**** > > ** ** > > That is a good thing!**** > > > We would appreciate your feedback on upcoming releases. Thanks, -- Andrei
