Re: [openstack-dev] [oslo] Openstack and SQLAlchemy

2014-07-08 Thread Ihar Hrachyshka
-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 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
 solve).
 
 https://wiki.openstack.org/wiki/OpenStack_and_SQLAlchemy#MySQLdb_.2B_eventlet_.3D_sad


>>>

>>>
 
It's eminently solvable.
>>> 
>>> Facebook and Google engineers have already created a
>>> nonblocking MySQLdb fork here:
>>> 
>>> https://github.com/chipturner/MySQLdb1
>>> 
>>> We just need to test it properly, package it up properly and
>>> get it upstreamed into MySQLdb.
>>> 
>> 
>> I'm not sure whether it will be easy to push upstream to merge
>> those patches, or make all distributions to ship a non-official
>> fork in place of the original project. For the latter, I even
>> doubt it's realistic.
> 
> You mean, like shipping MariaDB instead of MySQL?
> 
> Oh. Snap.

:)

There is a slight difference here. The MySQLdb1 fork is officially
deprecated and unsupported by its authors, while MariaDB has community
around it.

> 
> -jay
> 
> ___ OpenStack-dev
> mailing list OpenStack-dev@lists.openstack.org 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJTu/8WAAoJEC5aWaUY1u57ORwH/2TvKJzqRKBwnpJY7tct4VM/
R0ZxRmQiuAJjeQm2LV7eY1PSPlX2yPnIj2rk6mzBVU3YDi+ddx4cPa91yexrafe5
PQaiLajeJzBB24RnxNwFiPkk8wDzzOn5vP+DmzzDp05Gkzf7EBbVKIw86PF4hk4o
mAE4X1YQc1i9bpgBNs+WIX+WMQfSDoftho4ZaBC5tawZ1yoseYDzRTja6sqCSP8U
xGZovhCG2iGTzz8m0RbJRK6IS+mBSLMO0vLQirj1r45tt7dX/2nmV8RuSGbmcBt+
AU90f2pKlo4naByxDsZWssM2VyKjpUt+d+Vt3/6f6F8tXSGB9AT3RTP3HjRLJLQ=
=gqF+
-END PGP SIGNATURE-

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo] Openstack and SQLAlchemy

2014-07-08 Thread Jay Pipes

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 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 solve).

https://wiki.openstack.org/wiki/OpenStack_and_SQLAlchemy#MySQLdb_.2B_eventlet_.3D_sad






It's eminently solvable.

Facebook and Google engineers have already created a nonblocking
MySQLdb fork here:

https://github.com/chipturner/MySQLdb1

We just need to test it properly, package it up properly and get
it upstreamed into MySQLdb.



I'm not sure whether it will be easy to push upstream to merge those
patches, or make all distributions to ship a non-official fork in
place of the original project. For the latter, I even doubt it's
realistic.


You mean, like shipping MariaDB instead of MySQL?

Oh. Snap.

-jay

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo] Openstack and SQLAlchemy

2014-07-08 Thread Ihar Hrachyshka
-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 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 solve).
>> 
>> https://wiki.openstack.org/wiki/OpenStack_and_SQLAlchemy#MySQLdb_.2B_eventlet_.3D_sad
>>
>
>> 
> It's eminently solvable.
> 
> Facebook and Google engineers have already created a nonblocking
> MySQLdb fork here:
> 
> https://github.com/chipturner/MySQLdb1
> 
> We just need to test it properly, package it up properly and get
> it upstreamed into MySQLdb.
> 

I'm not sure whether it will be easy to push upstream to merge those
patches, or make all distributions to ship a non-official fork in
place of the original project. For the latter, I even doubt it's
realistic.

/Ihar
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJTu6/qAAoJEC5aWaUY1u57VmAIAOKv/2EOJc7IS3FJn7KssG3R
LPopiA8B2hlgfQYeNe6iHdXGmco6zZsCk1DBDbb6XhMMyM/svnG0B2d74q7fexsp
OakerOri52qxvhLWZFacbT854i+H9sO+75sbpsOOAvO9Msqw/binb1kfLkdD1ROl
2aLsuBX5+lrYS/BAua74RTIciW87qLzkUqIhwxd46N4oAw95gMC7mwivMvip96NY
+cAzP4ggFtUvBAXuP8O127tmVjuLVbu1PSCJAA1Cfm0aUpbPPGsugiorMarjCkE4
j4OHrUXY9zXmkhhdESg/Z4f0zyAipFSVSkhwKFTzP7Om5mwJYS9mKkgEI0DGtYY=
=vYa8
-END PGP SIGNATURE-

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo] Openstack and SQLAlchemy

2014-07-08 Thread Ihar Hrachyshka
-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.
>>> 
>>> 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 neutron, for example, and makes me wonder
>>> if it could help with the neutron db lock timeouts we see in
>>> the gate [2].  Don't let the bug status fool you, that thing is
>>> still showing up, or a variant of it is.
>>> 
>>> There are at least 6 lock-related neutron bugs hitting the gate
>>> [3].
>>> 
>>> [1] https://review.openstack.org/59760 [2]
>>> https://bugs.launchpad.net/neutron/+bug/1283522 [3]
>>> http://status.openstack.org/elastic-recheck/
>> 
>> 
>> yeah, tpool, correct me if I'm misunderstanding, we take some API
>> code that is 90% fetching from the database, we have it all under
>> eventlet, the purpose of which is, IO can be shoveled out to an
>> arbitrary degree, e.g. 500 concurrent connections type of thing,
>> but then we take all the IO (MySQL access) and put it into a
>> thread pool anyway.
> 
> Yep. It makes no sense to do that, IMO.
> 
> The solution is to use a non-blocking MySQLdb library which will
> yield appropriately for evented solutions like gevent and
> eventlet.
> 

FYI I've posted a neutron proposal to switch to MySQL Connector at:
https://review.openstack.org/104905

/Ihar
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJTu67+AAoJEC5aWaUY1u57sPQIAKGOyJRohkemZLno7QF20OId
zM7tIuy7J96qzEj7FIEeDJCv3BPl21BsJS/XLcQKDCXCVbZVDTo1Pp8W3a2EoY1L
w3EPl5OVMsZT6h44Ln63KKsn+cjyFg1oJ377cfU+E8MOZ62gxPgGt6q/E0n89/hq
zRTk5lh4jkAIuM5NSJ15Gmyfkps+/m3YvrutzH6hE3mYuLMWozS5RIP2mEH+DDLS
s3aRtDCdizEYU+/wrBgoeH5NeYfR6rB4akGLL7yfqF86lFvHSO40tTWZRdpdPlMU
8zfySY0U3x1AMbX7HToglq6mTevjDjD3kv7e4BrRS6zUgIW3VOSe1uge0cORYZI=
=dTxT
-END PGP SIGNATURE-

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo] Openstack and SQLAlchemy

2014-07-07 Thread Matt Riedemann



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 the moment to check if it's in other projects, but I'm not
seeing it in neutron, for example, and makes me wonder if it could
help with the neutron db lock timeouts we see in the gate [2].  Don't
let the bug status fool you, that thing is still showing up, or a
variant of it is.

There are at least 6 lock-related neutron bugs hitting the gate [3].

[1] https://review.openstack.org/59760
[2] https://bugs.launchpad.net/neutron/+bug/1283522
[3] http://status.openstack.org/elastic-recheck/



yeah, tpool, correct me if I'm misunderstanding, we take some API code
that is 90% fetching from the database, we have it all under eventlet,
the purpose of which is, IO can be shoveled out to an arbitrary degree,
e.g. 500 concurrent connections type of thing, but then we take all the
IO (MySQL access) and put it into a thread pool anyway.


Yep. It makes no sense to do that, IMO.

The solution is to use a non-blocking MySQLdb library which will yield
appropriately for evented solutions like gevent and eventlet.

Best,
-jay

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



Yeah, nevermind my comment, since it's not working without an eventlet 
patch, details in the nova bug here [1].  And it sounds like it's still 
not 100% with the patch.


[1] https://bugs.launchpad.net/nova/+bug/1171601

--

Thanks,

Matt Riedemann


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo] Openstack and SQLAlchemy

2014-07-07 Thread Jay Pipes



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 projects, but I'm not
seeing it in neutron, for example, and makes me wonder if it could
help with the neutron db lock timeouts we see in the gate [2].  Don't
let the bug status fool you, that thing is still showing up, or a
variant of it is.

There are at least 6 lock-related neutron bugs hitting the gate [3].

[1] https://review.openstack.org/59760
[2] https://bugs.launchpad.net/neutron/+bug/1283522
[3] http://status.openstack.org/elastic-recheck/



yeah, tpool, correct me if I'm misunderstanding, we take some API code
that is 90% fetching from the database, we have it all under eventlet,
the purpose of which is, IO can be shoveled out to an arbitrary degree,
e.g. 500 concurrent connections type of thing, but then we take all the
IO (MySQL access) and put it into a thread pool anyway.


Yep. It makes no sense to do that, IMO.

The solution is to use a non-blocking MySQLdb library which will yield 
appropriately for evented solutions like gevent and eventlet.


Best,
-jay

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo] Openstack and SQLAlchemy

2014-07-07 Thread Mike Bayer

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 neutron, for example, and makes me wonder if it could
> help with the neutron db lock timeouts we see in the gate [2].  Don't
> let the bug status fool you, that thing is still showing up, or a
> variant of it is.
>
> There are at least 6 lock-related neutron bugs hitting the gate [3].
>
> [1] https://review.openstack.org/59760
> [2] https://bugs.launchpad.net/neutron/+bug/1283522
> [3] http://status.openstack.org/elastic-recheck/


yeah, tpool, correct me if I'm misunderstanding, we take some API code
that is 90% fetching from the database, we have it all under eventlet,
the purpose of which is, IO can be shoveled out to an arbitrary degree,
e.g. 500 concurrent connections type of thing, but then we take all the
IO (MySQL access) and put it into a thread pool anyway.

Why are we doing this?   Assuming we currently have a 500+ concurrent DB
connections use case, has anyone demonstrated this actually working? 

Keep in mind, I'm a total dummy with async - other than the usual client
side JS/AJAX experience, I have very little "purely async API"
experience.But I've been putting out these questions on twitter and
elsewhere for some time and nobody is saying that I'm totally getting it
wrong.  I *should* be wrong.



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo] Openstack and SQLAlchemy

2014-07-07 Thread Jay Pipes

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 well (though I think it's
pretty easy to solve).

https://wiki.openstack.org/wiki/OpenStack_and_SQLAlchemy#MySQLdb_.2B_eventlet_.3D_sad


It's eminently solvable.

Facebook and Google engineers have already created a nonblocking MySQLdb 
fork here:


https://github.com/chipturner/MySQLdb1

We just need to test it properly, package it up properly and get it 
upstreamed into MySQLdb.


Best,
-jay


On 6/30/14, 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 carrying Openstack's database integration story forward.
To that extent I am focused on the oslo.db project which going forward
will serve as the basis for database patterns used by other Openstack
applications.

I've summarized what I've learned from the community over the past month
in a wiki entry at:

https://wiki.openstack.org/wiki/Openstack_and_SQLAlchemy

The page also refers to an ORM performance proof of concept which you
can see at https://github.com/zzzeek/nova_poc.

The goal of this wiki page is to publish to the community what's come up
for me so far, to get additional information and comments, and finally
to help me narrow down the areas in which the community would most
benefit by my contributions.

I'd like to get a discussion going here, on the wiki, on IRC (where I am
on freenode with the nickname zzzeek) with the goal of solidifying the
blueprints, issues, and SQLAlchemy / Alembic features I'll be focusing
on as well as recruiting contributors to help in all those areas.  I
would welcome contributors on the SQLAlchemy / Alembic projects directly
as well, as we have many areas that are directly applicable to Openstack.

I'd like to thank Red Hat and the Openstack community for welcoming me
on board and I'm looking forward to digging in more deeply in the coming
months!

- mike



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo] Openstack and SQLAlchemy

2014-07-07 Thread Matt Riedemann



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 well (though I think it's
pretty easy to solve).

https://wiki.openstack.org/wiki/OpenStack_and_SQLAlchemy#MySQLdb_.2B_eventlet_.3D_sad



On 6/30/14, 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 carrying Openstack's database integration story forward.
To that extent I am focused on the oslo.db project which going forward
will serve as the basis for database patterns used by other Openstack
applications.

I've summarized what I've learned from the community over the past month
in a wiki entry at:

https://wiki.openstack.org/wiki/Openstack_and_SQLAlchemy

The page also refers to an ORM performance proof of concept which you
can see at https://github.com/zzzeek/nova_poc.

The goal of this wiki page is to publish to the community what's come up
for me so far, to get additional information and comments, and finally
to help me narrow down the areas in which the community would most
benefit by my contributions.

I'd like to get a discussion going here, on the wiki, on IRC (where I am
on freenode with the nickname zzzeek) with the goal of solidifying the
blueprints, issues, and SQLAlchemy / Alembic features I'll be focusing
on as well as recruiting contributors to help in all those areas.  I
would welcome contributors on the SQLAlchemy / Alembic projects directly
as well, as we have many areas that are directly applicable to Openstack.

I'd like to thank Red Hat and the Openstack community for welcoming me
on board and I'm looking forward to digging in more deeply in the coming
months!

- mike



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



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 neutron, for example, and makes me wonder if it could help with the 
neutron db lock timeouts we see in the gate [2].  Don't let the bug 
status fool you, that thing is still showing up, or a variant of it is.


There are at least 6 lock-related neutron bugs hitting the gate [3].

[1] https://review.openstack.org/59760
[2] https://bugs.launchpad.net/neutron/+bug/1283522
[3] http://status.openstack.org/elastic-recheck/

--

Thanks,

Matt Riedemann


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo] Openstack and SQLAlchemy

2014-07-03 Thread Doug Hellmann
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 carrying Openstack's database integration story forward.
> To that extent I am focused on the oslo.db project which going forward
> will serve as the basis for database patterns used by other Openstack
> applications.
>
> I've summarized what I've learned from the community over the past month
> in a wiki entry at:
>
> https://wiki.openstack.org/wiki/Openstack_and_SQLAlchemy
>
> The page also refers to an ORM performance proof of concept which you
> can see at https://github.com/zzzeek/nova_poc.
>
> The goal of this wiki page is to publish to the community what's come up
> for me so far, to get additional information and comments, and finally
> to help me narrow down the areas in which the community would most
> benefit by my contributions.
>
> I'd like to get a discussion going here, on the wiki, on IRC (where I am
> on freenode with the nickname zzzeek) with the goal of solidifying the
> blueprints, issues, and SQLAlchemy / Alembic features I'll be focusing
> on as well as recruiting contributors to help in all those areas.  I
> would welcome contributors on the SQLAlchemy / Alembic projects directly
> as well, as we have many areas that are directly applicable to Openstack.
>
> I'd like to thank Red Hat and the Openstack community for welcoming me
> on board and I'm looking forward to digging in more deeply in the coming
> months!
>
> - mike

Good stuff, Mike, thanks for writing it all down. I'm looking forward
to seeing how much performance can be improved without drastic
rewrites! :-)

Doug

>
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo] Openstack and SQLAlchemy

2014-07-02 Thread Mike Bayer

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 solve).

https://wiki.openstack.org/wiki/OpenStack_and_SQLAlchemy#MySQLdb_.2B_eventlet_.3D_sad



On 6/30/14, 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 carrying Openstack's database integration story forward.  
> To that extent I am focused on the oslo.db project which going forward
> will serve as the basis for database patterns used by other Openstack
> applications.
>
> I've summarized what I've learned from the community over the past month
> in a wiki entry at:
>
> https://wiki.openstack.org/wiki/Openstack_and_SQLAlchemy 
>
> The page also refers to an ORM performance proof of concept which you
> can see at https://github.com/zzzeek/nova_poc.
>
> The goal of this wiki page is to publish to the community what's come up
> for me so far, to get additional information and comments, and finally
> to help me narrow down the areas in which the community would most
> benefit by my contributions.
>
> I'd like to get a discussion going here, on the wiki, on IRC (where I am
> on freenode with the nickname zzzeek) with the goal of solidifying the
> blueprints, issues, and SQLAlchemy / Alembic features I'll be focusing
> on as well as recruiting contributors to help in all those areas.  I
> would welcome contributors on the SQLAlchemy / Alembic projects directly
> as well, as we have many areas that are directly applicable to Openstack.
>
> I'd like to thank Red Hat and the Openstack community for welcoming me
> on board and I'm looking forward to digging in more deeply in the coming
> months!
>
> - mike
>
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo] Openstack and SQLAlchemy

2014-06-30 Thread Sandy Walsh
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'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 extent I am focused on the oslo.db project which going forward
will serve as the basis for database patterns used by other Openstack
applications.

I've summarized what I've learned from the community over the past month
in a wiki entry at:

https://wiki.openstack.org/wiki/Openstack_and_SQLAlchemy

The page also refers to an ORM performance proof of concept which you
can see at https://github.com/zzzeek/nova_poc.

The goal of this wiki page is to publish to the community what's come up
for me so far, to get additional information and comments, and finally
to help me narrow down the areas in which the community would most
benefit by my contributions.

I'd like to get a discussion going here, on the wiki, on IRC (where I am
on freenode with the nickname zzzeek) with the goal of solidifying the
blueprints, issues, and SQLAlchemy / Alembic features I'll be focusing
on as well as recruiting contributors to help in all those areas.  I
would welcome contributors on the SQLAlchemy / Alembic projects directly
as well, as we have many areas that are directly applicable to Openstack.

I'd like to thank Red Hat and the Openstack community for welcoming me
on board and I'm looking forward to digging in more deeply in the coming
months!

- mike



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [oslo] Openstack and SQLAlchemy

2014-06-30 Thread Mike Bayer
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 extent I am focused on the oslo.db project which going forward
will serve as the basis for database patterns used by other Openstack
applications.

I've summarized what I've learned from the community over the past month
in a wiki entry at:

https://wiki.openstack.org/wiki/Openstack_and_SQLAlchemy 

The page also refers to an ORM performance proof of concept which you
can see at https://github.com/zzzeek/nova_poc.

The goal of this wiki page is to publish to the community what's come up
for me so far, to get additional information and comments, and finally
to help me narrow down the areas in which the community would most
benefit by my contributions.

I'd like to get a discussion going here, on the wiki, on IRC (where I am
on freenode with the nickname zzzeek) with the goal of solidifying the
blueprints, issues, and SQLAlchemy / Alembic features I'll be focusing
on as well as recruiting contributors to help in all those areas.  I
would welcome contributors on the SQLAlchemy / Alembic projects directly
as well, as we have many areas that are directly applicable to Openstack.

I'd like to thank Red Hat and the Openstack community for welcoming me
on board and I'm looking forward to digging in more deeply in the coming
months!

- mike



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev