Update run_instance.rb

We're using an aws-like service that does not support security groups. With this change a the DescribeSecurityGroups is only called if there are security groups.
Use a new class instead of a deprecated one
Update README.md

The documentation here is correct:
 http://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html


If you specify aws.subnet_id and specify a list of security group names names for security_groups, then you will get the following error message:

==> default: Launching an instance with the following settings...
==> default:  -- Security Groups: ["A","B"]
...
==> default:  -- Assigning a public IP address in a VPC: false
There was an error talking to AWS. The error message is shown
below:

InvalidParameterCombination => The parameter groupName cannot be used with the parameter subnet


If you specify aws.subnet_id and specify a list of security group IDs names for security_groups, then this plugin works:

==> default: Launching an instance with the following settings...
==> default:  -- Security Groups: ["sg-1234","sg-4567"]
...
==> default:  -- Assigning a public IP address in a VPC: false
==> default: Waiting for instance to become "ready"...
==> default: Waiting for SSH to become available...
==> default: Machine is booted and ready for use!

See people talking about this here:
http://stackoverflow.com/questions/22365470/launching-instance-vpc-security-groups-may-not-be-used-for-a-non-vpc-launch
Update README to clarify rsync exclusion option
m1.small has been deprecated in us-east-1 - although the t-class instance types are cheaper they only support hvm - m3.medium is the smallest instance type to support both paravirtualization and hvm AMIs
Merge pull request #280 from ankushnarula/hotfix/fix-default-instance-type

m1.small has been deprecated in us-east-1
Updated README to use Ruby syntax for excluding multiple files and directories from rsync.
Merge pull request #277 from mypetyak/master

Update README to clarify rsync exclusion option
Added support for static ip for non-VPC instance.  Still a WIP with some need to clean up.
Added ability to assign an existing Elastic IP address to an instance, both EC2 and VPC.
Code cleanup
Updated change log
remove :endpoint option from elb config

When specifically setting an ec2 endpoint fog prints a warning when initializing the
`Fog::AWS::ELB` driver:

    [fog][WARNING] Unrecognized arguments: endpoint
Added retry delay when creating instances.

Without a retry delay - if you configure a lot of servers at the same time you will run into AWS API limits and it will throw an exception that will stop instance creation.

This adds in a minor delay when checking the status of an instance which seems to fix the issue when deploying ~ 20 - 40 machines.
Merge pull request #289 from btomasini/master

Allocate existing Elastic IP address using existing config api
fixed typo
Merge pull request #312 from Mytho/patch-1

fixed typo
Use the session token if it's available
Add support for the session token
Fix documentation