Allow specification of the node we wish to connect to.
Fix whitespace, changing tabs to spaces.
LinuxService: avoid enforcing systemd even if init.d script was found
no need to init None to None
ignore unicode errors in stdout
corrected indentation
Inventory script for Spacewalk servers based on the spacewalk-reports package
Merge pull request #2965 from bpennypacker/devel

newrelic_deployment bug fix to support both python 2.4 and 2.6
Do not need to chmod cache file each time

This is particularly important if you've manually ensured you have write
access via group permissions and not by owner.
Merge pull request #2967 from jonEbird/devel

Inventory script for Spacewalk servers based on the spacewalk-reports pa...
Fix pip module documentation (YAML quoting)
Allow virtualenv_command argument of the pip module to be a pathname
add basename and dirname to the core jinja2 filters
Ignore Intellij IML files.
Vagrant external inventory file, to dynamically determine your vagrant vm ip.
OpenStack Modules
Fixes apt_repository always reporting file uri repos as changed
Fix bug with include-level vars and sudo_user.

If a variable was provided for an include, in either of these ways:

    ---
    - hosts: all
      tasks:
      - include: included.yml param=www-data
      - include: included.yml
        vars:
          param: www-data

and then that param was used as the value of sudo_user in the included
tasks:

    ---
    - name: do something as a parameterized sudo_user
      command: whoami
      sudo: yes
      sudo_user: $param

you would receive a "failed to parse: usage: sudo" error back and the
command would not execute.

This seemed to be due to a missing call to template.template somewhere,
because the final value being passed through ssh was still `$param`.
After some digging, the issue seems to instead have been a problem with
providing the wrong context to the template for expansion. Inside the
`Task` logic, it was passing `play.vars` as the context, where
`module_vars` seemed more appropriate. After replacing it, my test case
above ran without issue. There was a comment above suggesting that the
template call might be unnecessary, but removing it made the original
error return, since it is not getting escaped later down the line. I
removed the comment since it was inaccurate.

I tried to actually incorporate my test case above into the test suite
as a regression test, but was unable to figure out how to structure it.
The existing test infrastructure seemed to only be testing for correct
number of counts in things (ok vs. changed, etc.), without regard for
whether the content generated by the command is correct. If there is an
example of a test similar to this one (where I would want to check the
JSON generated to make sure sudo_user had been converted), please let me
know and I will be happy to submit an additional patch.
fix for facter being installed in a different location
OpenStack Identity (keystone) user module

Module for managing users, tenants, and roles within OpenStack.