MySQL engine doesn't specified at a table s with foreign key constraint.

[Ilya Pekelny]

By default the CI uses MyISAM MySQL engine which doesn't support foreign key constraint. Thus we must explicitly sign MySQL engine as InnoDB at every table declares foreign keys or which is a fk target. Otherwise foreign keys can't be declared.

[OpenStack Infra (hudson-openstack)]

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

[David Stanek (dstanek)]

Is this something we actually want to do? After reading the comment from jeblair the decision to use MyISAM is deliberate. This seems to be a deployment concern. I don't know if it's practical, but maybe someone is already using an alternative storage engine like IBMDB2I?

[Dolph Mathews (dolph)]

I've abandoned the referenced changed due to inactivity and failing tests. If this is still an issue, please reset the status.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Dolph Mathews (<email address hidden>) on branch: master
Review: https://review.openstack.org/138712
Reason: Abandoning due to inactivity and failing tests.

[Morgan Fainberg (mdrnstm)]

Marking as invalid since this should have expired as incomplete long ago.