Re: [openstack-dev] oslo.db 1.1.0 released

2014-11-18 Thread Roman Podoliaka
Matt, This is really weird. Victor and I will take a closer look. Thanks, Roman On Tue, Nov 18, 2014 at 5:22 AM, Matt Riedemann mrie...@linux.vnet.ibm.com wrote: On 11/17/2014 9:36 AM, Victor Sergeyev wrote: Hello All! Oslo team is pleased to announce the new release of Oslo database

Re: [openstack-dev] oslo.db 1.1.0 released

2014-11-18 Thread Endre Karlson
Not sure if relevant but some tests on changes to requirements where failing today too on the postgres job Endre Karlson Matt, This is really weird. Victor and I will take a closer look. Thanks, Roman On Tue, Nov 18, 2014 at 5:22 AM, Matt Riedemann mrie...@linux.vnet.ibm.com wrote: On

Re: [openstack-dev] oslo.db 1.1.0 released

2014-11-18 Thread Matt Riedemann
On 11/17/2014 9:36 AM, Victor Sergeyev wrote: Hello All! Oslo team is pleased to announce the new release of Oslo database handling library - oslo.db 1.1.0 List of changes: $ git log --oneline --no-merges 1.0.2..master 1b0c2b1 Imported Translations from Transifex 9aa02f4 Updated from global

Re: [openstack-dev] oslo.db 1.1.0 released

2014-11-18 Thread Victor Sergeyev
Matt, As for race in Nova - it caused by deprecated is_backend_avail() function, which calls _ensure_backenv_available() method, which creates a SQLAlchemy engine and opens a test connection, but doesn't call engine.dispose(). Depending on Python interpreter version, this connection may remain

Re: [openstack-dev] oslo.db 1.1.0 released

2014-11-18 Thread Sean Dague
Is there a more minimal version of https://review.openstack.org/#/c/103920/ that *just* fixes this issue. So we can evaluate the refactor on it's own, but get the bug fixed more immediately. Also can I request that when deprecating methods in oslo libraries we use a standard deprecation

Re: [openstack-dev] oslo.db 1.1.0 released

2014-11-18 Thread Victor Sergeyev
Well, we can re-define is_backend_avail() in Nova code and use it instead of oslo.db's function. it looks a bit ugly but it will be fast Also can I request that when deprecating methods in oslo libraries we use a standard deprecation mechanism so that warnings are emitted when this method is

Re: [openstack-dev] oslo.db 1.1.0 released

2014-11-18 Thread Mike Bayer
On Nov 18, 2014, at 11:47 AM, Sean Dague s...@dague.net wrote: Also can I request that when deprecating methods in oslo libraries we use a standard deprecation mechanism so that warnings are emitted when this method is used. +1 for DeprecationWarnings, I noticed oslo.db doesn’t seem to

Re: [openstack-dev] oslo.db 1.1.0 released

2014-11-18 Thread Doug Hellmann
On Nov 18, 2014, at 12:26 PM, Mike Bayer mba...@redhat.com wrote: On Nov 18, 2014, at 11:47 AM, Sean Dague s...@dague.net wrote: Also can I request that when deprecating methods in oslo libraries we use a standard deprecation mechanism so that warnings are emitted when this method is

Re: [openstack-dev] oslo.db 1.1.0 released

2014-11-18 Thread Matt Riedemann
On 11/18/2014 10:17 AM, Victor Sergeyev wrote: Matt, As for race in Nova - it caused by deprecated is_backend_avail() function, which calls _ensure_backenv_available() method, which creates a SQLAlchemy engine and opens a test connection, but doesn't call engine.dispose(). Depending on Python

Re: [openstack-dev] oslo.db 1.1.0 released

2014-11-17 Thread Mike Bayer
go team oslo!!! On Nov 17, 2014, at 10:36 AM, Victor Sergeyev vserge...@mirantis.com wrote: Hello All! Oslo team is pleased to announce the new release of Oslo database handling library - oslo.db 1.1.0 List of changes: $ git log --oneline --no-merges 1.0.2..master 1b0c2b1

Re: [openstack-dev] oslo.db 1.1.0 released

2014-11-17 Thread Matt Riedemann
On 11/17/2014 9:36 AM, Victor Sergeyev wrote: Hello All! Oslo team is pleased to announce the new release of Oslo database handling library - oslo.db 1.1.0 List of changes: $ git log --oneline --no-merges 1.0.2..master 1b0c2b1 Imported Translations from Transifex 9aa02f4 Updated from global