The play was just checking for the presence of the keyword in the
YAML datastructure, and not the value of the field, so doing something
like variable substitution was always causing the play to be accelerated

* also minor tweak to the # of retries in the connection attempt

Fixes #4012

Fixes #3943

Fixes #3556

Conflicts:
	lib/ansible/playbook/__init__.py
	lib/ansible/playbook/play.py

fix JSON extra vars quotation.

Loading the default variables in _build_role_dependencies() lead to
a side-effect where those variables were over-riding inventory variables.

* Default variables are now fed directly into roles, just like the
  other variables, so that roles see their unique values rather
  than those set at the global level.

* Role dependency duplicates are now determined by checking the params used
  when specifying them as dependencies rather than just on the name of the
  role. For example, the following would be included twice without having
  to specify "allow_duplicates: true":

  dependencies:
  - { role: foo, x: 1 }
  - { role: foo, x: 2 }

Adding regions_exclude parameter to be able to do subtractive region exc...

adding regions_exclude parameter to be able to do subtractive region exclusion. Defaults to us-gov-west-1 so as to not cause errors for people who don't have govcloud credentials but get it in their regions list

This reverts commit 1d13ec2d.

* ssh port not being picked up, always uses default of 22
* forgot to 'import time' in the fireball2 connection plugin

Fix issue 3908. There was some ilegal operations over the sets

quantum_network: fix some doc mistakes

- tenant_name was missing.
- comments were on wrong tasks.
- error message had a reference to glance.

Fixes #3111

Caveats:
* requiretty must be disabled in the sudoers config
* asking for a password doesn't work yet, so any sudoers users must
  be configured with NOPASSWD
* if not starting the daemon as root, the user running the daemon
  must have sudoers entries to allow them to run the command as the
  target sudo_user

Still needs:
* chunked file transfer/receive
* should probably move all send/recv operations to separate
  functions to reduce code duplication
* initial connection setup over ssh? or do we handle that in runner?

This is based somewhat loosely on how Keyczar does things. Their
implementation does things in a much more generic way to allow for more
variance in how the cipher is created, but since we're only using one
key type most of our values are hard-coded. They also add a header to
their messages, which I am not doing (don't see the need for it
currently).