Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

: Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here) So, To try to reach some kind of conclusion here I am wondering if it would be acceptable to folks (would people even adopt such a change?) if we (oslo folks/others) provided a new function in say lockutils.py

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

. From: Joshua Harlow [harlo...@fastmail.com] Sent: Wednesday, December 09, 2015 6:13 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here) So, To try to reach

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

So, To try to reach some kind of conclusion here I am wondering if it would be acceptable to folks (would people even adopt such a change?) if we (oslo folks/others) provided a new function in say lockutils.py (in oslo.concurrency) that would let users of oslo.concurrency pick which kind

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

On 12/01/2015 08:08 AM, Duncan Thomas wrote: > > > On 1 December 2015 at 13:40, Sean Dague > wrote: > > > The current approach means locks block on their own, are processed in > the order they come in, but deletes aren't possible. The busy lock

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

Sean Dague wrote: On 12/01/2015 08:08 AM, Duncan Thomas wrote: On 1 December 2015 at 13:40, Sean Dague> wrote: The current approach means locks block on their own, are processed in the order they come in, but deletes aren't possible. The busy

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

So my takeaway is we need each project to have something like: https://gist.github.com/harlowja/b4f0ddadbda1f92cc1e2 That could possibly exist in oslo (I just threw it together) but the idea is that a thread/greenthread would run that 'run_forever' method in that code and it would

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

Excerpts from Joshua Harlow's message of 2015-12-01 09:28:18 -0800: > Sean Dague wrote: > > On 12/01/2015 08:08 AM, Duncan Thomas wrote: > >> > >> On 1 December 2015 at 13:40, Sean Dague >> > wrote: > >> > >> > >> The current approach means locks block

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

On 11/30/2015 05:25 PM, Clint Byrum wrote: > Excerpts from Ben Nemec's message of 2015-11-30 13:22:23 -0800: >> On 11/30/2015 02:15 PM, Sean Dague wrote: >>> On 11/30/2015 03:01 PM, Robert Collins wrote: On 1 December 2015 at 08:37, Ben Nemec wrote: > On

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

On 1 December 2015 at 13:40, Sean Dague wrote: > > The current approach means locks block on their own, are processed in > the order they come in, but deletes aren't possible. The busy lock would > mean deletes were normal. Some extra cpu spent on waiting, and lock > order

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

On 11/30/2015 02:15 PM, Sean Dague wrote: > On 11/30/2015 03:01 PM, Robert Collins wrote: >> On 1 December 2015 at 08:37, Ben Nemec wrote: >>> On 11/30/2015 12:42 PM, Joshua Harlow wrote: Hi all, I just wanted to bring up an issue, possible solution and get

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

Ben Nemec wrote: On 11/30/2015 02:15 PM, Sean Dague wrote: On 11/30/2015 03:01 PM, Robert Collins wrote: On 1 December 2015 at 08:37, Ben Nemec wrote: On 11/30/2015 12:42 PM, Joshua Harlow wrote: Hi all, I just wanted to bring up an issue, possible solution and get

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

On 1 December 2015 at 08:37, Ben Nemec wrote: > On 11/30/2015 12:42 PM, Joshua Harlow wrote: >> Hi all, >> >> I just wanted to bring up an issue, possible solution and get feedback >> on it from folks because it seems to be an on-going problem that shows >> up not when an

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

Excerpts from Joshua Harlow's message of 2015-11-30 10:42:53 -0800: > Hi all, > > I just wanted to bring up an issue, possible solution and get feedback > on it from folks because it seems to be an on-going problem that shows > up not when an application is initially deployed but as on-going >

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

On 11/30/2015 12:42 PM, Joshua Harlow wrote: > Hi all, > > I just wanted to bring up an issue, possible solution and get feedback > on it from folks because it seems to be an on-going problem that shows > up not when an application is initially deployed but as on-going > operation and running

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

Ben Nemec wrote: On 11/30/2015 12:42 PM, Joshua Harlow wrote: Hi all, I just wanted to bring up an issue, possible solution and get feedback on it from folks because it seems to be an on-going problem that shows up not when an application is initially deployed but as on-going operation and

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

On 11/30/2015 03:01 PM, Robert Collins wrote: > On 1 December 2015 at 08:37, Ben Nemec wrote: >> On 11/30/2015 12:42 PM, Joshua Harlow wrote: >>> Hi all, >>> >>> I just wanted to bring up an issue, possible solution and get feedback >>> on it from folks because it seems to

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

Joshua Harlow wrote: Ben Nemec wrote: On 11/30/2015 12:42 PM, Joshua Harlow wrote: Hi all, I just wanted to bring up an issue, possible solution and get feedback on it from folks because it seems to be an on-going problem that shows up not when an application is initially deployed but as

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

Clint Byrum wrote: Excerpts from Joshua Harlow's message of 2015-11-30 10:42:53 -0800: Hi all, I just wanted to bring up an issue, possible solution and get feedback on it from folks because it seems to be an on-going problem that shows up not when an application is initially deployed but as

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

Sean Dague wrote: On 11/30/2015 03:01 PM, Robert Collins wrote: On 1 December 2015 at 08:37, Ben Nemec wrote: On 11/30/2015 12:42 PM, Joshua Harlow wrote: Hi all, I just wanted to bring up an issue, possible solution and get feedback on it from folks because it seems

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

On 11/30/2015 01:57 PM, Joshua Harlow wrote: > Ben Nemec wrote: >> On 11/30/2015 12:42 PM, Joshua Harlow wrote: >>> Hi all, >>> >>> I just wanted to bring up an issue, possible solution and get feedback >>> on it from folks because it seems to be an on-going problem that shows >>> up not when an

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

Sean Dague wrote: On 11/30/2015 03:01 PM, Robert Collins wrote: On 1 December 2015 at 08:37, Ben Nemec wrote: On 11/30/2015 12:42 PM, Joshua Harlow wrote: Hi all, I just wanted to bring up an issue, possible solution and get feedback on it from folks because it seems

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

Excerpts from Ben Nemec's message of 2015-11-30 13:22:23 -0800: > On 11/30/2015 02:15 PM, Sean Dague wrote: > > On 11/30/2015 03:01 PM, Robert Collins wrote: > >> On 1 December 2015 at 08:37, Ben Nemec wrote: > >>> On 11/30/2015 12:42 PM, Joshua Harlow wrote: > Hi