[openstack-dev] [oslo][oslo.db] MySQL Cluster support

Octave J. Orgeron octave.orgeron at oracle.com
Thu Feb 2 16:40:23 UTC 2017


Hi Doug,

One could try to detect the default engine. However, in MySQL Cluster, 
you can support multiple storage engines. Only NDB is fully clustered 
and replicated, so if you accidentally set a table to be InnoDB it won't 
be replicated . So it makes more sense for the operator to be explicit 
on which engine they want to use.

Thanks,
Octave

On 2/2/2017 6:46 AM, Doug Hellmann wrote:
> 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
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

Oracle <http://www.oracle.com/>
Octave J. Orgeron | Sr. Principal Architect and Software Engineer
Oracle Linux OpenStack
Mobile: +1-720-616-1550 <tel:+17206161550>
500 Eldorado Blvd. | Broomfield, CO 80021
Certified Oracle Enterprise Architect: Systems Infrastructure 
<http://www.oracle.com/us/solutions/enterprise-architecture/index.html>
Green Oracle <http://www.oracle.com/commitment> Oracle is committed to 
developing practices and products that help protect the environment

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170202/238bbf3a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: oracle_sig_logo.gif
Type: image/gif
Size: 658 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170202/238bbf3a/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: oea_logo.jpg
Type: image/jpeg
Size: 2398 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170202/238bbf3a/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: green-for-email-sig_0.gif
Type: image/gif
Size: 356 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170202/238bbf3a/attachment-0001.gif>


More information about the OpenStack-dev mailing list