id_vagrant may need to be chmod 0400 in order to allow use as an ssh identity file

[jbsmith]

Please consider setting id_vagrant to mode 0400 in order to facilitate its use as an ssh identity file.

This will prevent failures that resemble the following:

evstack | FAILED => Authentication or permission failure. In some cases, you may have been able to authenticate and did not have permissions on the remote directory. Consider changing the remote temp path in ansible.cfg to a path rooted in "/tmp". Failed command was: mkdir -p $HOME/.ansible/tmp/ansible-1376859817.42-159871785923233 && chmod a+rx $HOME/.ansible/tmp/ansible-1376859817.42-159871785923233 && echo $HOME/.ansible/tmp/ansible-1376859817.42-159871785923233, exited with result 255

[lorin]

Unfortunately, I don't think git preserves these permissions, so I can't set them in the repository. I've added to the readme for now.

Alternately, I could use ~/.vagrant.d/insecure_private_key as the path to the key in the ansible hosts file. I'd have to verify that ansible will resolve the path properly.

[jbsmith]

Looked at that as well, seems you are right. Thanks for the feedback.