-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/07/14 16:06, Jay Pipes wrote:
> On 07/08/2014 04:46 AM, Ihar Hrachyshka wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
>>
>> On 07/07/14 22:14, Jay Pipes wrote:
>>> On 07/02/2014 09:23 PM, Mike Bayer wrote:
I've just added a ne
On 07/08/2014 04:46 AM, Ihar Hrachyshka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/07/14 22:14, Jay Pipes wrote:
On 07/02/2014 09:23 PM, Mike Bayer wrote:
I've just added a new section to this wiki, "MySQLdb + eventlet =
sad", summarizing some discussions I've had in the past
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/07/14 22:14, Jay Pipes wrote:
> On 07/02/2014 09:23 PM, Mike Bayer wrote:
>> I've just added a new section to this wiki, "MySQLdb + eventlet =
>> sad", summarizing some discussions I've had in the past couple of
>> days about the ongoing issue
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/07/14 22:28, Jay Pipes wrote:
>
>
> On 07/07/2014 04:17 PM, Mike Bayer wrote:
>>
>> On 7/7/14, 3:57 PM, Matt Riedemann wrote:
>>>
>>>
>>>
>>> Regarding the eventlet + mysql sadness, I remembered this [1]
>>> in the nova.db.api code.
>>>
On 7/7/2014 3:28 PM, Jay Pipes wrote:
On 07/07/2014 04:17 PM, Mike Bayer wrote:
On 7/7/14, 3:57 PM, Matt Riedemann wrote:
Regarding the eventlet + mysql sadness, I remembered this [1] in the
nova.db.api code.
I'm not sure if that's just nova-specific right now, I'm a bit too
lazy at th
On 07/07/2014 04:17 PM, Mike Bayer wrote:
On 7/7/14, 3:57 PM, Matt Riedemann wrote:
Regarding the eventlet + mysql sadness, I remembered this [1] in the
nova.db.api code.
I'm not sure if that's just nova-specific right now, I'm a bit too
lazy at the moment to check if it's in other projec
On 7/7/14, 3:57 PM, Matt Riedemann wrote:
>
>
>
> Regarding the eventlet + mysql sadness, I remembered this [1] in the
> nova.db.api code.
>
> I'm not sure if that's just nova-specific right now, I'm a bit too
> lazy at the moment to check if it's in other projects, but I'm not
> seeing it in neut
On 07/02/2014 09:23 PM, Mike Bayer wrote:
I've just added a new section to this wiki, "MySQLdb + eventlet = sad",
summarizing some discussions I've had in the past couple of days about
the ongoing issue that MySQLdb and eventlet were not meant to be used
together. This is a big one to solve as
On 7/2/2014 8:23 PM, Mike Bayer wrote:
I've just added a new section to this wiki, "MySQLdb + eventlet = sad",
summarizing some discussions I've had in the past couple of days about
the ongoing issue that MySQLdb and eventlet were not meant to be used
together. This is a big one to solve as
On Mon, Jun 30, 2014 at 12:56 PM, Mike Bayer wrote:
> Hi all -
>
> For those who don't know me, I'm Mike Bayer, creator/maintainer of
> SQLAlchemy, Alembic migrations and Dogpile caching. In the past month
> I've become a full time Openstack developer working for Red Hat, given
> the task of car
I've just added a new section to this wiki, "MySQLdb + eventlet = sad",
summarizing some discussions I've had in the past couple of days about
the ongoing issue that MySQLdb and eventlet were not meant to be used
together. This is a big one to solve as well (though I think it's
pretty easy to so
woot!
From: Mike Bayer [mba...@redhat.com]
Sent: Monday, June 30, 2014 1:56 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [oslo] Openstack and SQLAlchemy
Hi all -
For those who don't know me, I
Hi all -
For those who don't know me, I'm Mike Bayer, creator/maintainer of
SQLAlchemy, Alembic migrations and Dogpile caching. In the past month
I've become a full time Openstack developer working for Red Hat, given
the task of carrying Openstack's database integration story forward.
To that
13 matches
Mail list logo