Open Stack

Excerpts from Octave J. Orgeron's message of 2017-02-01 20:33:38 -0700:
> Hi Folks,
> 
> I'm working on adding support for MySQL Cluster to the core OpenStack 
> services. This will enable the community to benefit from an 
> active/active, auto-sharding, and scale-out MySQL database. My approach 
> is to have a single configuration setting in each core OpenStack service 
> in the oslo.db configuration section called mysql_storage_engine that 
> will enable the logic in the SQL Alchemy or Alembic upgrade scripts to 
> handle the differences between InnoDB and NDB storage engines 
> respectively. When enabled, this logic will make the required table 
> schema changes around:
> 
>   * Row character length limits 65k -> 14k
>   * Proper SQL ordering of foreign key, constraints, and index operations
>   * Interception of savepoint and nested operations
> 
> By default this functionality will not be enabled and will have no 
> impact on the default InnoDB functionality. These changes have been 
> tested on Kilo and Mitaka in previous releases of our OpenStack 
> distributions with Tempest. I'm working on updating these patches for 
> upstream consumption. We are also working on a 3rd party CI for 
> regression testing against MySQL Cluster for the community.
> 
> The first change set is for oslo.db and can be reviewed at:
> 
> https://review.openstack.org/427970
> 
> Thanks,
> Octave
> 

Is it possible to detect the storage engine at runtime, instead of
having the operator configure it?

Doug