Migrations may create MyISAM tables

[Dolph Mathews]

Following bug 1189633, it was discovered that keystone's migrations do not explicitly define InnoDB as the desired storage engine, although that is what we recommend and test against.

In the case of RHEL, mysql's default storage engine is set to MyISAM, which causes keystone-manage db_sync to fail as of migration 23 due to a lack of support for constraints.

[Dolph Mathews (dolph)]

This is related to nova's bug 741274

[Alvaro Lopez (aloga)]

Related with https://bugs.launchpad.net/keystone/+bug/1131174

[Alvaro Lopez (aloga)]

Adressed in https://review.openstack.org/#/c/33102/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/33102
Committed: http://github.com/openstack/keystone/commit/cd8fa2b0e7ca002b7621fe0e35b921154946e12b
Submitter: Jenkins
Branch: master

commit cd8fa2b0e7ca002b7621fe0e35b921154946e12b
Author: Brant Knudson <email address hidden>
Date: Fri Jun 14 13:03:41 2013 -0500

    Use InnoDB for MySQL

    This change adds a migration to convert any non-InnoDB tables to
    InnoDB.

    On some systems, the default engine is MyISAM, which doesn't
    support features used by Keystone (foreign keys).

    The approach is the same as what's used in Nova. A test is added
    to ensure that all tables use InnoDB after migration. The test
    passes when all the tables are mysql_engine='InnoDB'. This is
    accomplished by adding a new migration that migrates all the
    tables that aren't InnoDB to InnoDB.

    Fixes bug 1191110.

    Change-Id: I220f7642f5468c5cf4194f248210f90ff983b6e5