WIP to test ubuntu support - #19

For reference: https://github.com/neillturner/kitchen-ansible/blob/master/provisioner_options.md

ERROR! the role 'gsa.https-proxy' was not found in /tmp/kitchen/roles:/tmp/kitchen/roles:/tmp/kitchen
       
       The error appears to have been in '/tmp/kitchen/test.yml': line 8, column 7, but may
       be elsewhere in the file depending on the exact syntax problem.
       
       The offending line appears to be:
       
         roles:
           - gsa.https-proxy
             ^ here

Yeeeeah, this is annoying problem. Ansible is looking for a role by that name in its "roles path", but since the repository is cloned (by default) into a folder named ansible-https-proxy, the playbook thinks the role is missing. Two options are:

• Change the role reference in the playbook to ansible-https-proxy
• Change the role's directory name to be gsa.https-proxy

While the Test Kitchen setup seems nice for testing across different operating systems, I worry that it

• Adds another dependency (Ruby), making setup (especially locally) harder
• Requires a bunch of boilerplate
• Is more opaque than executing Docker directly, which could make troubleshooting harder

I have been doing (simple) integration/acceptance/smoke testing as tasks within roles, and have been really happy with that approach. This keeps all the testing in Ansible, and runs those tests in the context of applying the role, which

• Execute any time you execute the role, whether in testing or production
• Can short-circuit the role right after the corresponding change is applied, if the corresponding test fails

Not saying we shouldn't use Test Kitchen...just that there are tradeoffs.