Updated and improved the documentation (examples)

Service module changed to terminate early if only enabled specified

Adding npm module

Provide functionality to work with Rackspace's public cloud

Expanded the documentation slightly.

Improved backrefs example in lineinfile.

Preliminary ability to use Jinja2 {{ }} to replace ${foo.bar} in playbooks.  Can't use both at the same time per line.

Typo in cloudformation module documentation.

postgresql_user: fix docstrings

Change documentation of "state" param to refer to user (role) state instead of
database state.

Change 2 function docstrings to reflect the code

Use aptitude safe-upgrade for apt upgrade=yes

Use aptitude safe-upgrade instead of apt-get upgrade to implement
apt: upgrade=yes. Using aptitude ensures that missing dependencies
will also be installed.

Fixes #2540

Vagrant module - fixed version_added

Suppressed output and updated documentation

Double quoted version_added in documentation

Examples must use "name" parameter instead of "guest" for virt module, b...

Chnge description as list inside string

Files can be inserted during server creation (like a fully formed
authorized_keys file). This code allows that to happen.

Docs were updated for formatting, location, and to add the new entry for
files.

The rax inventory plugin provides a way to discovery inventory in the
Rackspace Public Cloud by way of pyrax, the official SDK. Grouping will
be done if a group:name is found in the instance metadata. When a single
host is queried all the instance details are returned with a rax_
prefix.

Because inventory plugins cannot take extra arguments, ENV variables
must be set to point to the pyrax compatible credentials file and the
region to query against.

This library provides functionality for the Rackspace Public Cloud by
way of the official pyrax SDK (https://github.com/rackspace/pyrax). At
this time only the cloudservers service is functional. Instances can be
created or deleted. Idempotency is provided on matching instances with
the same name, flavor, image, and metadata values within a given
region.

pyrax usage does require a credentials file written out to hold username
and API key.  See pyrax documentation for details
(https://github.com/rackspace/pyrax/blob/master/docs/pyrax_doc.md)