Try to split into three separate components -> controller, tester,
and 'tasks' (postgresql-tasks in our case).  The controller
component is the main part which is able to run the task remotely.
Tester is more-like library for 'tasks' component (should be
reusable on the raw git level).

* controller: Almost separated component.
* postgresql-tasks: Likewise.
* tester: Likewise.

* get_machine: Rework, new options, using parse_credsfile script
to parse configuration etc.
* parse_credsfile: New config-parsing script.

* ansible/dummy-wrapper.yml: Helper playbook to directly invoke
"included" playbooks.
* ansible/fedora.yml: The "main" playbook (new file).
* ansible/include/beakerlib.yml: New file, install beakerlib
remotely.
* ansible/include/prepare-testenv.yml: Install the test
dependencies remotely.
* ansible/run_include: Helper script to run included playbooks.
* dist: Do not distribute ansible playbooks in tarball.
* get_machine: Helper script to obtain openstack machine, not
used currently.
* lib_pgsql.sh: Assert for PG_VERSION, not for datadir (as it by
default exists after postgresql-server installation.
* run_remote: Helper script invoking the main ansible playbook.
* ansible_helpers/wait-for-ssh: Helper script as 'wait_for' is
broken?
* README: Document.
* .gitignore: Ignore private files.