summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndreas Jaeger <aj@suse.com>2017-02-01 19:44:36 +0100
committerAndreas Jaeger <jaegerandi@gmail.com>2017-02-02 12:13:43 +0000
commit27793e6df9ddf2ce727b05cce31a000b97897c44 (patch)
treec4a53ef88923b13acc883bcbd24b0248a27245d1
parenta1cc77e72dbad29a14313965df73eab439c705ee (diff)
downloadkeystone-stable/mitaka.tar.gz
Prepare for using standard python testsmitaka-eolstable/mitaka
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 allows to change in project-config the python-db jobs to python-jobs since python-jobs will call this script initially. Update README for this. See also http://lists.openstack.org/pipermail/openstack-dev/2016-November/107784.html Needed-By: Ic42f8d5392ab1d9b52c6c84c92dee0092bd2779a Change-Id: I253726467151622e8aa3ff40bacc0b3f9903b342 (cherry picked from commit 61933fef10a092b951aae440800531fd8b44c558)
-rw-r--r--doc/source/devref/development.environment.rst6
-rwxr-xr-xtools/test-setup.sh57
2 files changed, 63 insertions, 0 deletions
diff --git a/doc/source/devref/development.environment.rst b/doc/source/devref/development.environment.rst
index 2718966aa..bef2acafc 100644
--- a/doc/source/devref/development.environment.rst
+++ b/doc/source/devref/development.environment.rst
@@ -173,3 +173,9 @@ You should then be able to `import keystone` using Python without issue:
If you can import Keystone without a traceback, you should be ready to move on
to :doc:`../developing`.
+
+Database setup
+==============
+
+The script ``tools/test-setup.sh`` sets up databases as used by the
+unit tests.
diff --git a/tools/test-setup.sh b/tools/test-setup.sh
new file mode 100755
index 000000000..07a078547
--- /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