<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Mike,<br>
    <br>
    I've sent out another email that gives some more insight into how
    this will work for the other OpenStack services. The hook in the
    oslo.db namespace gives a global configuration point for enabling
    the patches elsewhere.<br>
    <br>
    Thanks,<br>
    Octave<br>
    <br>
    <div class="moz-cite-prefix">On 2/2/2017 9:24 AM, Mike Bayer wrote:<br>
    </div>
    <blockquote
      cite="mid:48ffa1aa-1d09-9386-5025-e75022847c08@redhat.com"
      type="cite">
      <br>
      <br>
      On 02/02/2017 10:25 AM, Monty Taylor wrote:
      <br>
      <blockquote type="cite">On 02/01/2017 09:33 PM, Octave J. Orgeron
        wrote:
        <br>
        <blockquote type="cite">Hi Folks,
          <br>
          <br>
          I'm working on adding support for MySQL Cluster to the core
          OpenStack
          <br>
          services. This will enable the community to benefit from an
          <br>
          active/active, auto-sharding, and scale-out MySQL database. My
          approach
          <br>
          is to have a single configuration setting in each core
          OpenStack service
          <br>
          in the oslo.db configuration section called
          mysql_storage_engine that
          <br>
          will enable the logic in the SQL Alchemy or Alembic upgrade
          scripts to
          <br>
          handle the differences between InnoDB and NDB storage engines
          <br>
          respectively. When enabled, this logic will make the required
          table
          <br>
          schema changes around:
          <br>
          <br>
            * Row character length limits 65k -> 14k
          <br>
            * Proper SQL ordering of foreign key, constraints, and index
          operations
          <br>
            * Interception of savepoint and nested operations
          <br>
          <br>
          By default this functionality will not be enabled and will
          have no
          <br>
          impact on the default InnoDB functionality. These changes have
          been
          <br>
          tested on Kilo and Mitaka in previous releases of our
          OpenStack
          <br>
          distributions with Tempest. I'm working on updating these
          patches for
          <br>
          upstream consumption. We are also working on a 3rd party CI
          for
          <br>
          regression testing against MySQL Cluster for the community.
          <br>
          <br>
          The first change set is for oslo.db and can be reviewed at:
          <br>
          <br>
          <a class="moz-txt-link-freetext" href="https://review.openstack.org/427970">https://review.openstack.org/427970</a>
          <br>
        </blockquote>
        <br>
        Yay!
        <br>
        <br>
        (You may not be aware, but there are several of us who used to
        be on the
        <br>
        MySQL Cluster team who are now on OpenStack. I've been wanting
        good NDB
        <br>
        support for a while. So thank you!)
        <br>
      </blockquote>
      <br>
      as I noted on the review it would be nice to have some specifics
      of how this is to be accomplished as the code review posted
      doesn't show anything of how this would work.
      <br>
      <br>
      <br>
      <br>
      <br>
      <blockquote type="cite">
        <br>
        <br>
__________________________________________________________________________
        <br>
        OpenStack Development Mailing List (not for usage questions)
        <br>
        Unsubscribe:
        <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
        <br>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
        <br>
        <br>
      </blockquote>
      <br>
__________________________________________________________________________
      <br>
      OpenStack Development Mailing List (not for usage questions)
      <br>
      Unsubscribe:
      <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
      <br>
      <a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
      <br>
      <br>
    </blockquote>
    <br>
    <div class="moz-signature">-- <br>
      <br>
      <p>
        <a href="http://www.oracle.com/" target="_blank"><img
            src="cid:part1.03020005.03000703@oracle.com" alt="Oracle"
            border="0" height="26" width="114"></a><br>
        <font color="#666666" size="2" face="Verdana, Arial, Helvetica,
          sans-serif">Octave J. Orgeron | Sr. Principal Architect and
          Software Engineer<br>
          <font color="#ff0000">Oracle</font> Linux OpenStack<br>
          Mobile: <a href="tel:+17206161550">+1-720-616-1550</a><br>
          500 Eldorado Blvd. | Broomfield, CO 80021<br>
          <a
href="http://www.oracle.com/us/solutions/enterprise-architecture/index.html"><img
              src="cid:part4.08040504.08060206@oracle.com"
              alt="Certified Oracle Enterprise Architect: Systems
              Infrastructure" border="0" height="42" width="182"></a><br>
          <a href="http://www.oracle.com/commitment" target="_blank"><img
              src="cid:part6.04090103.01080707@oracle.com" alt="Green
              Oracle" align="absmiddle" border="0" height="28"
              width="44"></a>
          <font color="#4B7D42" size="1" face="Verdana, Arial,
            Helvetica, sans-serif">Oracle is committed to developing
            practices and products that help protect the environment</font>
        </font></p>
      <font color="#666666" size="2" face="Verdana, Arial, Helvetica,
        sans-serif">
      </font></div>
  </body>
</html>