big reorg: prepare for generalization

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.

4 files changed, 0 insertions, 60 deletions

diff --git a/config/.gitignore b/config/.gitignore
deleted file mode 100644
index 57c4fcb..0000000
--- a/config/.gitignore
+++ /dev/null
@@ -1,2 +0,0 @@
-*.sh
-hosts
diff --git a/config/config.sh.template b/config/config.sh.template
deleted file mode 100644
index 94cbe22..0000000
--- a/config/config.sh.template
+++ /dev/null
@@ -1,36 +0,0 @@
-# OpenStack ID
-# ------------
-#
-# By default, based on DTF_OPENSTACK_ID content the corresponding OpenStack
-# configuration is used.  You may have multiple OpenStack instances configured -
-# this option selects one.  Based on the OpenStack ID (say 'EXAMPLE'), those
-# configuration-like files are used:
-#
-# * private/os/'EXAMPLE'.yml
-#       File having OpenStack credentials in ansible variable file (YAML file
-#       with "key: value" lines).  See the ./private/os/EXAMPLE.yml for
-#       variables you should set up.  Keep this file secret.
-#
-# * config/os/'EXAMPLE'.sh
-#       This file must contain configuration for specific OpenStack instance.
-#       Usually information about available images, flavors, networking, etc.
-#       The template file config/os/EXAMPLE.sh may be used when configuring your
-#       testing environment.
-
-export DTF_OPENSTACK_ID=dropbear
-
-# Result Database
-# ---------------
-# Directory where the testsuite should keep its (persistent) results.  Make sure
-# that this directory is backed up.
-
-export DTF_DATABASE=/var/lib/dtf_results
-
-# Presenter place
-# ---------------
-# For now, only static results are available.  DTF_PRESENTER_PLACE must contain
-# rsync-compatible destination (it may be place accessible via ssh+rsync).  It
-# is expected that some httpd server is able to read the directory with results
-# and publish them as static directory structure over http://.
-
-export DTF_PRESENTER_PLACE=user@example.org:/var/www/html/my_project/dtf
diff --git a/config/hosts.template b/config/hosts.template
deleted file mode 100644
index 6850700..0000000
--- a/config/hosts.template
+++ /dev/null
@@ -1,2 +0,0 @@
-[host]
-10.64.27.30
diff --git a/config/os/EXAMPLE.sh b/config/os/EXAMPLE.sh
deleted file mode 100644
index b5ba270..0000000
--- a/config/os/EXAMPLE.sh
+++ /dev/null
@@ -1,20 +0,0 @@
-## THIS IS EXAMPLE OPENSTACK DTF CONFIGURATION ##
-
-# variable declarations, should be C&Ped
-declare -A os_flavor_ids os_image_ids
-export os_flavor_ids=[]
-export os_image_ids=[]
-
-# connection info about particular OpenStack instance
-
-# which ssh keys should be uploaded to created VMs
-export os_keypair="keypair-id"
-# group of firewall rules to be set on VMs
-export os_security_group=test_group
-# the name of network connection as is presented by ansible
-export os_network_dev=network_name
-
-# per-distribution dictionary with images/flavors
-os_flavor_ids["fedora20"]="2"
-os_image_ids["fedora20"]="0461eef2-5921-4c01-95a6-6edf96d41b89"
-