Fixes #10243

Add how to load extra variables directly from a file (using @).

made sure passwords are strings

updated to correct to_bytes function
removed old to_bytes/to_unicode and repointed clients to new location
fixed unicode test

Fixed broken link.  Added links to both core and extras git repos.  

Typo in galaxy.rst

Dynamic task includes still need some work, this is a rough first version.
* doesn't work with handler sections of playbooks yet
* when using include + with*, the insertion order is backwards
* fix potential for task lists to be unsynchronized when using the linear
  strategy, as the include conditional could be predicated on an inventory
  variable

to 2015.

ternary filter

Add support for new OpenStack modules

Small change to guid_gce.rst,  'project-name', should be 'project_id'

Update outdated command description in section "Latest Release Via Yum"

Added "--recursive" to git clone command in installation via yum section. Changed rpm build parent directory to current dir.

Conflicts:
	library/files/stat

Resolved: Using theirs

allow fact objects to be instantiated w/o triggering all fact collection

Allow ansible (ad-hoc) to support --extra-vars

This inventory module is based on the shade library like the new os_
modules. It shares the ability to configure itself from os-client-config
configuration files or from the standard OS_ environment variables.

More importantly the guts of the code to get the server vars is now
shared with os_compute_facts. This means that playbooks that provision
compute hosts and then want to run plays on them can refer to server
variables in exactly the same way whether the provsioning play ran first
or whether the play ran in the context of a pre-existing inventory.

Return empty string if unable to read from some files during fact gathering so as not to change the values we return

Added a note about escaping backreferences when using 'regex_replace' filter

Add path for user defined plugin

More integration tests for rax modules

Incoming cloud config for OpenStack is complex due to plugins and
deployer choices. Rather than having the logic spread all over the
OpenStack modules, centralize it in the module_utils code.