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.

1 files changed, 18 insertions, 0 deletions

diff --git a/postgresql-tests/gen-data/remote_generate b/postgresql-tests/gen-data/remote_generate
new file mode 100755
index 0000000..eee11f6
--- /dev/null
+++ b/postgresql-tests/gen-data/remote_generate
@@ -0,0 +1,18 @@
+#!/bin/bash -x
+
+where="root@$1"
+
+./dist/dist
+tar tf dist/dist.tar.gz
+
+ssh_opts="-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null"
+ssh="ssh $ssh_opts"
+scp="scp $ssh_opts"
+
+$scp dist/dist.tar.gz "$where:/root"
+
+$ssh "$where" "cd /root ; tar -xf dist.tar.gz ; ./prep && ./generate"
+
+rm -rf remote_results
+mkdir remote_results
+$scp -r "$where:/root/results" ./remote_results