Adding AWS support to openshift-ansible module

- Update documentation to say that ssh configuration need to point to the private key file
- Removing the -p argument when calling time .... because it is misintrepreted by ruby
- Turning the cluster.sh to agnostic in its help/error message by replacing explicit reference to GCE by a a variable
- Fixing a bug within the playbooks that incorrectly references the minions and master fact group.
- Adding playbooks for AWS, which are almost of copy/paste for those of GCE
- Added environment variable OO_PROVIDER to allow definition of the provider. Defaults is gce
- TODO implement the terminate.yml cookbook

1 files changed, 14 insertions, 2 deletions

diff --git a/README_AWS.md b/README_AWS.md
index 2602f9883..c0f2bce75 100644
--- a/README_AWS.md
+++ b/README_AWS.md
@@ -14,13 +14,25 @@ Create a credentials file
    export AWS_ACCESS_KEY_ID='AKIASTUFF'
    export AWS_SECRET_ACCESS_KEY='STUFF'
 ```
-
 1. source this file
 ```
   source ~/.aws_creds
 ```
+Note: You must source this file in each shell that you want to run cloud.rb
+
+
+(Optional) Setup your $HOME/.ssh/config file
+-------------------------------------------
+In case of a cluster creation, or any other case where you don't know the machine hostname in advance, you can use '.ssh/config' 
+to setup a private key file to allow ansible to connect to the created hosts.
+
+To do so, add the the following entry to your $HOME/.ssh/config file and make it point to the private key file which allows you to login on AWS.
+'''
+Host *.compute-1.amazonaws.com
+  PrivateKey $HOME/.ssh/my_private_key.pem
+'''
 
-1. Note: You must source this file in each shell that you want to run cloud.rb
+Alternatively, you can configure your ssh-agent to hold the credentials to connect to your AWS instances.
 
 
 Install Dependencies