sqlalchemy migration doesn't work well

[Feilong Wang]

There are 2 issues with current migration script, though the logic works fine.

1. Sqlalchemy's table name is case sensitive
2. Currently, Zaqar doesn't support poolgroup table. That piece of code should be moved into separated patch when we want to support that.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/416785

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/416785
Committed: https://git.openstack.org/cgit/openstack/zaqar/commit/?id=1ddd9ca5c0df41d740fd58a12b4f4bb1a8926c77
Submitter: Jenkins
Branch: master

commit 1ddd9ca5c0df41d740fd58a12b4f4bb1a8926c77
Author: Fei Long Wang <email address hidden>
Date: Thu Jan 5 13:26:46 2017 +1300

    Fix sqlalchemy migration

    1. Fix the case of table names
    2. Fix the sqlalchemy migration tests

    NOTE: The sqlalchemy migrations test depends on oslo_db's migration
    test which requires mysql user 'openstack_citest' with password
    'openstack_citest' otherwise the test will be skipped.

    Closes-Bug: #1654105

    Change-Id: Ia672440a948fa4784f6dd1aa6d5fed0bc3915663

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/zaqar 4.0.0.0rc1 release candidate.