[openstack-dev] [all] DevStack switching from MySQL-python to PyMySQL

Sean Dague sean at dague.net
Mon Oct 12 16:16:17 UTC 2015

On 10/12/2015 12:03 PM, Jesse Pretorius wrote:
> On 15 June 2015 at 12:30, Sean Dague <sean at dague.net
> <mailto:sean at dague.net>> wrote:
>     As a heads up for where we stand. The switch was flipped, but a lot of
>     neutron jobs (rally & tempest) went into a pretty high failure rate
>     after it was (all the other high volume jobs seemed fine).
>     We reverted the change here to unwedge things -
>     https://review.openstack.org/#/c/191010/
>     After a long conversation with Henry and Armando we came up with a new
>     plan, because we want the driver switch, and we want to figure out why
>     it causes a high Neutron failure rate, but we don't want to block
>     everything.
>     https://review.openstack.org/#/c/191121/ - make the default Neutron jobs
>     set some safe defaults (which are different than non Neutron job
>     defaults), but add a flag to make it possible to expose these issues.
>     Then add new non-voting check jobs to Neutron queue to expose these
>     issues - https://review.openstack.org/#/c/191141/. Hopefully allowing
>     interested parties to get to the bottom of these issues around the db
>     layer. It's in the check queue instead of the experimental queue to get
>     enough volume to figure out the pattern for the failures, because they
>     aren't 100%, and they seem to move around a bit.
>     Once https://review.openstack.org/#/c/191121/ is landed we'll revert
>     revert - https://review.openstack.org/#/c/191113/ and get everything
>     else back onto pymysql.
> Did this ever progress through to completion?

Yes, the last patch was landed on June 16th. We've been running on
pymysql for most of the liberty development cycle.


Sean Dague

More information about the OpenStack-dev mailing list