Suse integration

[Peuserik]

We work mainly with SLES and OpenSUSE OS-Images, so we need to use them as kitchen-docker baseimage for testing purposes.

This PR enables kitchen-docker to work on Suse-Based-Images properly.

Tested with SLES12 and OpenSUSE 13.2

[coderanger]

This doesn't seem to actually be required. Was there a reason you added it?

[Peuserik]

@coderanger thanks for your comment
and sorry for my bad english skills.

sles and opensuse do have a security policy that will deny the built in way to set the password. Its quite few months ago so i can't remember the exact name of the lib that is doing that...

but on Suse machines the line
echo #{username}:#{password} | chpasswd
will result in following error on a normal kitchen test, or kitchen create

   Step 7 : RUN echo kitchen:kitchen | chpasswd
    ---> Running in ef9ed93c2b6e
   BAD PASSWORD: it is based on a dictionary word
   BAD PASSWORD: is too simple

the kitchen create finishes but you can't connect with ssh provisioner afterwards.

The line you commented on creates a way around the password verification with encrypting the password before piping it into chpasswd

I hope ist was understandable. :)

[CarpathianUA]

Hi guys,
I'm one of those people who are patiently waiting for SLES/OpenSuse integration.
Hope it will be realized.
Thanks in advance.

[amontalban]

Another interested user, not sure if this is going to be managed anytime soon but open to help.

Thanks!

[tas50]

I'm going to close this out at this point since we have opensuse and opensuse leap in the case statements as well as testing. Feel free to open a new PR if you think something is still missing.