Support config_drive and user_data in rax_scaling_group
Ensure that files is the right type, and that we send the formatted personality var
Fix determination if a few configurations change in the launch config
Don't count DELETED servers when adding new servers
Added user, tenant and password to module parameters declaration --
these parameters are already handled by the implementation
Initialize create_changed and replace_changed
Fixed bug #193 where parameter name was set incorrectly
correct requirement of parameter dest

The parameter "dest:" is required, but it is documented as "required: false".
Merge pull request #183 from sb98052/devel

Added user, tenant and password to module parameters declaration
Merge pull request #187 from jorgebastida/devel

ec2_asg: Initialize create_changed and replace_changed
Merge pull request #208 from CptLausebaer/patch-1

correct requirement of parameter dest
Merge pull request #194 from rglew/devel

Fixed bug #193 where parameter name was set incorrectly
Merge pull request #116 from sivel/rax-skip-deleted

rax module: Don't count DELETED servers when adding new servers
Merge pull request #115 from sivel/autoscale-more-args

rax_scaling_group module improvements
Fix for systemd service scripts with newlines

Fixes #127
LinuxService: check properly if systemd is running

Use a pure Python reimplementation of the [sd_booted(3)][1] function
from [systemd v210][2].

[1]: http://www.freedesktop.org/software/systemd/man/sd_booted.html
[2]: http://cgit.freedesktop.org/systemd/systemd-stable/tree/src/libsystemd/sd-daemon/sd-daemon.c?id=v210#n465
Transform comment into docstring
LinuxService: use the same logic as systemd for appending .service to an unit

There's no need for complex rules to determine if `.service` should be
appended to a unit's name, just do like systemd does.  For more details
see commit [696c245a23d55e4249651573eb9c61b68e61580c][1] and
[`unit_name_mangle`][2] from systemd.

[1]: http://cgit.freedesktop.org/systemd/systemd/commit/?id=696c245a23d55e4249651573eb9c61b68e61580c
[2]: http://cgit.freedesktop.org/systemd/systemd/tree/src/shared/unit-name.c?id=696c245a23d55e4249651573eb9c61b68e61580c#n501
LinuxService: check properly if systemd manages the unit

There's no need to list and look at all the unit files, just check the
[load state][1] of the current unit by running `systemctl -p LoadUnit show`.

This also covers cases like when an unit is masked (which means that
systemd can't start or enable it).

[1]: http://cgit.freedesktop.org/systemd/systemd-stable/tree/src/shared/unit-name.c?h=v208-stable#n52
LinuxService.get_service_tools: check for systemd first

Check for systemd first then for legacy init systems. This simplifies
the code.