Roman Podoliaka 314496a581 Prevent races in opportunistic db test cases
Opportunistic db test cases create schemas on demand, so that each
test case which inherits the base test case class, will get its own
db schema (i. e. races between tests are not possible).

In order to do schema provisioning we have to connect to RDBMS server
first. So far we've been connecting to the openstack_citest database,
which is guaranteed to exist on CI nodes. It turns out, there are a
few test cases in Nova (maybe in other projects as well), that drop
and recreate the openstack_citest database. If they happen to do that
when the opportunistic db fixture is in the middle of provisioning a
schema, those tests will fail (as there is an an open session to the
database and thus it can't be dropped).

This can be solved easily by changing the way we provision new
schemas in opportunistic db test cases as actually, we don't have to
connect to the openstack_citest database at all:

 - for MySQL we can use an empty db name to connect to MySQL server,
   but not to a particular database
 - PostgreSQL requires us to specify the database name. We can use
   the service postgres database here (PostgreSQL shell utils such
   as createdb, createuser, etc use it for the very same reason)

Closes-Bug: #1328997

Change-Id: I0dc0becc5cb40d3dab3289c865a96113522a0b9a
2014-06-13 15:04:45 +03:00
openstack Remove common context from oslo.db 2014-06-04 17:53:26 +03:00
sqlalchemy Prevent races in opportunistic db test cases 2014-06-13 15:04:45 +03:00
__init__.py Fix the graduate.sh script result 2014-04-18 11:33:16 +03:00
api.py Fix usage of oslo.config 2014-05-27 15:58:22 +03:00
concurrency.py Add eventlet.tpool.Proxy for DB API calls 2014-06-06 18:16:00 +03:00
exception.py Make the tests passing 2014-04-18 12:51:26 +03:00
options.py Handle slave database connection in EngineFacade 2014-06-10 17:25:06 +03:00