From 0f6bbe303f054480d19d95a9820f7b777feb2ed5 Mon Sep 17 00:00:00 2001
From: Andreas Jaeger <aj@suse.com>
Date: Fri, 3 Feb 2017 07:33:49 +0100
Subject: [PATCH] Prepare for using standard python tests

Add simple script to setup mysql and postgresql databases, this script
can be run by users during testing and will be run by CI systems for
specific setup before running unit tests. This is exactly what is
currently done by OpenStack CI in project-config.

This allows to change in project-config the python-db jobs to
python-jobs since python-jobs will call this script initially.

See also
http://lists.openstack.org/pipermail/openstack-dev/2016-November/107784.html

Update devref for this.

Needed-By: I628f825d9200f7951eae46b7be78b111b1a8141c
Change-Id: If549e6f108ec6184a432d5050da4386efe794a4e
(cherry picked from commit 1c91c0f03308feb6635eb8de10833d0f83648f8d)
---
 doc/source/devref/testing.rst |  7 +++++
 tools/test-setup.sh           | 57 +++++++++++++++++++++++++++++++++++
 2 files changed, 64 insertions(+)
 create mode 100755 tools/test-setup.sh

diff --git a/doc/source/devref/testing.rst b/doc/source/devref/testing.rst
index 957eb3d8612..71509bd82ad 100644
--- a/doc/source/devref/testing.rst
+++ b/doc/source/devref/testing.rst
@@ -83,6 +83,13 @@ execution. To ensure the Cinder tests are picked up when running tempest, run::
 More information about tempest can be found in the `Tempest Documentation
 <http://docs.openstack.org/developer/tempest/overview.html>`_.
 
+Database Setup
+~~~~~~~~~~~~~~~
+
+Some unit and functional tests will use a local database. You can use
+``tools/test-setup.sh`` to set up your local system the same way as
+it's setup in the CI environment.
+
 Running a subset of tests using tox
 -----------------------------------
 One common activity is to just run a single test, you can do this with tox
diff --git a/tools/test-setup.sh b/tools/test-setup.sh
new file mode 100755
index 00000000000..07a078547b2
--- /dev/null
+++ b/tools/test-setup.sh
@@ -0,0 +1,57 @@
+#!/bin/bash -xe
+
+# This script will be run by OpenStack CI before unit tests are run,
+# it sets up the test system as needed.
+# Developers should setup their test systems in a similar way.
+
+# This setup needs to be run as a user that can run sudo.
+
+# The root password for the MySQL database; pass it in via
+# MYSQL_ROOT_PW.
+DB_ROOT_PW=${MYSQL_ROOT_PW:-insecure_slave}
+
+# This user and its password are used by the tests, if you change it,
+# your tests might fail.
+DB_USER=openstack_citest
+DB_PW=openstack_citest
+
+sudo -H mysqladmin -u root password $DB_ROOT_PW
+
+# It's best practice to remove anonymous users from the database.  If
+# a anonymous user exists, then it matches first for connections and
+# other connections from that host will not work.
+sudo -H mysql -u root -p$DB_ROOT_PW -h localhost -e "
+    DELETE FROM mysql.user WHERE User='';
+    FLUSH PRIVILEGES;
+    GRANT ALL PRIVILEGES ON *.*
+        TO '$DB_USER'@'%' identified by '$DB_PW' WITH GRANT OPTION;"
+
+# Now create our database.
+mysql -u $DB_USER -p$DB_PW -h 127.0.0.1 -e "
+    SET default_storage_engine=MYISAM;
+    DROP DATABASE IF EXISTS openstack_citest;
+    CREATE DATABASE openstack_citest CHARACTER SET utf8;"
+
+# Same for PostgreSQL
+# The root password for the PostgreSQL database; pass it in via
+# POSTGRES_ROOT_PW.
+DB_ROOT_PW=${POSTGRES_ROOT_PW:-insecure_slave}
+
+# Setup user
+root_roles=$(sudo -H -u postgres psql -t -c "
+   SELECT 'HERE' from pg_roles where rolname='$DB_USER'")
+if [[ ${root_roles} == *HERE ]];then
+    sudo -H -u postgres psql -c "ALTER ROLE $DB_USER WITH SUPERUSER LOGIN PASSWORD '$DB_PW'"
+else
+    sudo -H -u postgres psql -c "CREATE ROLE $DB_USER WITH SUPERUSER LOGIN PASSWORD '$DB_PW'"
+fi
+
+# Store password for tests
+cat << EOF > $HOME/.pgpass
+*:*:*:$DB_USER:$DB_PW
+EOF
+chmod 0600 $HOME/.pgpass
+
+# Now create our database
+psql -h 127.0.0.1 -U $DB_USER -d template1 -c "DROP DATABASE IF EXISTS openstack_citest"
+createdb -h 127.0.0.1 -U $DB_USER -l C -T template0 -E utf8 openstack_citest