Re: [openstack-dev] [oslo] dependency analysis for graduating more oslo libraries

2014-01-15 Thread Doug Hellmann 
On Wed, Jan 15, 2014 at 11:49 AM, Joshua Harlow wrote:

>  Very nice write up +1
>
>  A question, many modules are pulling in oslo.log as seen from the
> dependency graph which itself then pulls in oslo.config. Is the plan to
> just have all these modules use the regular python logging and have
> oslo.log be a plugin/formatter/adapter to python logging?
>

If we can set up oslo logging to maintain the context data that we add
now, then yes we could change the other libraries to just use python's
logging module directly. I think the work that's being done on using a
custom formatter instead of a logging adapter will let us do that.



>
>  Likely people that would use those libraries and that aren't tied to
> openstack want to provide/configure there own logging (which is normally
> done via python logging configuration files and such...)
>
>  A side question: what are all these libraries going to be named, seems
> like we need a lot of creative library names (not just prefix everything
> with oslo) :-)
>

I'm using the oslo prefix for now for convenience. We can come up with more
creative names for libraries that have no other oslo dependencies as we
create those releases.


>
> Sent from my really tiny device...
>
> On Jan 14, 2014, at 11:53 AM, "Doug Hellmann" 
> wrote:
>
>   I've spent some time over the past day or two looking at the
> dependencies between modules in the oslo incubator, trying to balance the
> desire to have a small number of libraries with themes that make sense and
> the need to eliminate circular dependencies.
>
>  The results of all of this are posted to
> https://wiki.openstack.org/wiki/Oslo/GraduationStatus, where I have
> grouped the modules together into proposed libraries.
>
>  The dependencies between the libraries can be seen in several graphs
> I've prepared and posted to
> https://wiki.openstack.org/wiki/Oslo/Dependencies
>
>  Once we settle on the list of libraries, the next step is to look at the
> lowest level libraries to see what steps need to be taken before they can
> be released. I plan to start on that after the icehouse-2 deadline.
>
>  Oslo team (and other interested parties), please take a look at the two
> wiki pages above and provide any feedback you have here on this ML thread.
>
>  Thanks,
> 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
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo] dependency analysis for graduating more oslo libraries

2014-01-15 Thread Joshua Harlow 
Very nice write up +1

A question, many modules are pulling in oslo.log as seen from the dependency 
graph which itself then pulls in oslo.config. Is the plan to just have all 
these modules use the regular python logging and have oslo.log be a 
plugin/formatter/adapter to python logging?

Likely people that would use those libraries and that aren't tied to openstack 
want to provide/configure there own logging (which is normally done via python 
logging configuration files and such...)

A side question: what are all these libraries going to be named, seems like we 
need a lot of creative library names (not just prefix everything with oslo) :-)

Sent from my really tiny device...

On Jan 14, 2014, at 11:53 AM, "Doug Hellmann" 
mailto:doug.hellm...@dreamhost.com>> wrote:

I've spent some time over the past day or two looking at the dependencies 
between modules in the oslo incubator, trying to balance the desire to have a 
small number of libraries with themes that make sense and the need to eliminate 
circular dependencies.

The results of all of this are posted to 
https://wiki.openstack.org/wiki/Oslo/GraduationStatus, where I have grouped the 
modules together into proposed libraries.

The dependencies between the libraries can be seen in several graphs I've 
prepared and posted to https://wiki.openstack.org/wiki/Oslo/Dependencies

Once we settle on the list of libraries, the next step is to look at the lowest 
level libraries to see what steps need to be taken before they can be released. 
I plan to start on that after the icehouse-2 deadline.

Oslo team (and other interested parties), please take a look at the two wiki 
pages above and provide any feedback you have here on this ML thread.

Thanks,
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] dependency analysis for graduating more oslo libraries

2014-01-15 Thread Doug Hellmann 
On Wed, Jan 15, 2014 at 11:09 AM, Vishvananda Ishaya
wrote:

>
> On Jan 15, 2014, at 6:40 AM, Doug Hellmann 
> wrote:
>
>
>
>
> On Wed, Jan 15, 2014 at 6:51 AM, Victor Sergeyev 
> wrote:
>
>> Hello All.
>>
>> As for lockutils - a few days ago I wondered why we used custom oslo
>> module instead of lockfile library [1]. AFAIK, it must be due to this bug
>> [2] (please fix me, if I wrong).
>>
>> This library is available on github [3] and there is a pull-request
>> fixing the bug [4], but unfortunately it hasn’t been merged yet. And seems
>> that this project is not maintained anymore - author told, that he “haven't
>> done anything with it in a few years” [5].
>>
>> So my question is - can we start maintaining this library (put it on
>> stackforge) and use it instead of oslo.lockutils? Or maybe we could include
>> parts of oslo.lockutils into lockfile? Or vice versa, incorporate lockfile
>> into oslo.lockutils?
>>
>
> That might make sense.
>
> It looks like the lockfile package on PyPI is meant to be portable to
> Windows, and I'm not sure if we care about that. Does it provide any other
> useful features or API improvements over the lockfiles module we have?
> We'll still need a wrapper, since we have configuration options in our
> module now.
>
> How much work would it be to transition to the other library?
>
> Doug
>
>
> We used lockfile in the early days of openstack:
>
> https://github.com/openstack/nova/blob/essex-rc2/nova/utils.py#L957
>
> and it was plagued with many problems. Switching to fsync based locks
> solved a lot of these
> issues.
>

Hurray for institutional memory! :-)

Thanks, Vish, we'll stick with the version in oslo and work on fixing any
issues it has.

Doug



>
> Vish
>
>
>
>>
>> [1] https://pypi.python.org/pypi/lockfile
>> [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632857
>> [3] https://github.com/smontanaro/pylockfile
>> [4] https://github.com/smontanaro/pylockfile/pull/3
>> [5] https://github.com/smontanaro/pylockfile/pull/3#issuecomment-32085554
>>
>>
>> On Wed, Jan 15, 2014 at 1:00 AM, Michael Still  wrote:
>>
>>> On Wed, Jan 15, 2014 at 9:27 AM, Ben Nemec 
>>> wrote:
>>>
>>> > It would be nice to get lockutils graduated to solve some of the issues
>>> > mentioned in the oslo.db section, but I believe we do have an
>>> outstanding
>>> > question regarding its behavior without lock_path being set.  I think
>>> Clint
>>> > was on board with Sean's proposed solution after quite a bit of
>>> discussion
>>> > (
>>> http://lists.openstack.org/pipermail/openstack-dev/2013-December/021620.html
>>> ),
>>> > so it's possible we could just restore that patch and call it done,
>>> but it
>>> > should probably be addressed somehow before graduation.
>>>
>>> I committed a while ago (at the last summit IIRC) to working on
>>> getting lockutils released as a library, but I haven't managed to get
>>> that done yet. If it is blocking other people I can prioritise that
>>> work to being higher on my todo list.
>>>
>>> Part of the problem here is that its my first oslo graduation, so I
>>> need to figure out what to do...
>>>
>>> Michael
>>>
>>> --
>>> Rackspace Australia
>>>
>>> ___
>>> 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
>
>
>
> ___
> 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] dependency analysis for graduating more oslo libraries

2014-01-15 Thread Vishvananda Ishaya 

On Jan 15, 2014, at 6:40 AM, Doug Hellmann  wrote:

> 
> 
> 
> On Wed, Jan 15, 2014 at 6:51 AM, Victor Sergeyev  
> wrote:
> Hello All.
> 
> As for lockutils - a few days ago I wondered why we used custom oslo module 
> instead of lockfile library [1]. AFAIK, it must be due to this bug [2] 
> (please fix me, if I wrong).
> 
> This library is available on github [3] and there is a pull-request fixing 
> the bug [4], but unfortunately it hasn’t been merged yet. And seems that this 
> project is not maintained anymore - author told, that he “haven't done 
> anything with it in a few years” [5]. 
> 
> So my question is - can we start maintaining this library (put it on 
> stackforge) and use it instead of oslo.lockutils? Or maybe we could include 
> parts of oslo.lockutils into lockfile? Or vice versa, incorporate lockfile 
> into oslo.lockutils?
> 
> That might make sense.
> 
> It looks like the lockfile package on PyPI is meant to be portable to 
> Windows, and I'm not sure if we care about that. Does it provide any other 
> useful features or API improvements over the lockfiles module we have? We'll 
> still need a wrapper, since we have configuration options in our module now.
> 
> How much work would it be to transition to the other library?
> 
> Doug

We used lockfile in the early days of openstack:

https://github.com/openstack/nova/blob/essex-rc2/nova/utils.py#L957

and it was plagued with many problems. Switching to fsync based locks solved a 
lot of these
issues.

Vish

>  
> 
> [1] https://pypi.python.org/pypi/lockfile
> [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632857
> [3] https://github.com/smontanaro/pylockfile
> [4] https://github.com/smontanaro/pylockfile/pull/3
> [5] https://github.com/smontanaro/pylockfile/pull/3#issuecomment-32085554
> 
> 
> On Wed, Jan 15, 2014 at 1:00 AM, Michael Still  wrote:
> On Wed, Jan 15, 2014 at 9:27 AM, Ben Nemec  wrote:
> 
> > It would be nice to get lockutils graduated to solve some of the issues
> > mentioned in the oslo.db section, but I believe we do have an outstanding
> > question regarding its behavior without lock_path being set.  I think Clint
> > was on board with Sean's proposed solution after quite a bit of discussion
> > (http://lists.openstack.org/pipermail/openstack-dev/2013-December/021620.html),
> > so it's possible we could just restore that patch and call it done, but it
> > should probably be addressed somehow before graduation.
> 
> I committed a while ago (at the last summit IIRC) to working on
> getting lockutils released as a library, but I haven't managed to get
> that done yet. If it is blocking other people I can prioritise that
> work to being higher on my todo list.
> 
> Part of the problem here is that its my first oslo graduation, so I
> need to figure out what to do...
> 
> Michael
> 
> --
> Rackspace Australia
> 
> ___
> 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



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo] dependency analysis for graduating more oslo libraries

2014-01-15 Thread Julien Danjou 
On Wed, Jan 15 2014, Ben Nemec wrote:

> The problem is that lockfile doesn't really solve our current problem,
> which is where to put the lock files. Fortunately, it sounds like Julien
> is working on changes to lockutils to remove the file based locking,
> which should solve the issues we're having with it right now. 

That's true, but that won't solve this for Windows I'm afraid. Though if
someone knows a solution to have file free lock in Windows, I'll be
happy to hear it.

-- 
Julien Danjou
/* Free Software hacker * independent consultant
   http://julien.danjou.info */


signature.asc
Description: 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] dependency analysis for graduating more oslo libraries

2014-01-15 Thread Ben Nemec 
 

On 2014-01-15 05:51, Victor Sergeyev wrote: 

> Hello All. 
> 
> As for lockutils - a few days ago I wondered why we used custom oslo module 
> instead of lockfile library [1]. AFAIK, it must be due to this bug [2] 
> (please fix me, if I wrong). 
> 
> This library is available on github [3] and there is a pull-request fixing 
> the bug [4], but unfortunately it hasn't been merged yet. And seems that this 
> project is not maintained anymore - author told, that he "haven't done 
> anything with it in a few years" [5]. 
> 
> So my question is - can we start maintaining this library (put it on 
> stackforge) and use it instead of oslo.lockutils? Or maybe we could include 
> parts of oslo.lockutils into lockfile? Or vice versa, incorporate lockfile 
> into oslo.lockutils? 
> 
> [1] https://pypi.python.org/pypi/lockfile [1] 
> [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632857 [2] 
> [3] https://github.com/smontanaro/pylockfile [3] 
> [4] https://github.com/smontanaro/pylockfile/pull/3 [4] 
> [5] https://github.com/smontanaro/pylockfile/pull/3#issuecomment-32085554 [5]

The problem is that lockfile doesn't really solve our current problem,
which is where to put the lock files. Fortunately, it sounds like Julien
is working on changes to lockutils to remove the file based locking,
which should solve the issues we're having with it right now. 

-Ben 

> On Wed, Jan 15, 2014 at 1:00 AM, Michael Still  wrote:
> 
> On Wed, Jan 15, 2014 at 9:27 AM, Ben Nemec  wrote:
> 
>> It would be nice to get lockutils graduated to solve some of the issues
>> mentioned in the oslo.db section, but I believe we do have an outstanding
>> question regarding its behavior without lock_path being set. I think Clint
>> was on board with Sean's proposed solution after quite a bit of discussion
>> (http://lists.openstack.org/pipermail/openstack-dev/2013-December/021620.html
>>  [6]),
>> so it's possible we could just restore that patch and call it done, but it
>> should probably be addressed somehow before graduation.
> 
> I committed a while ago (at the last summit IIRC) to working on
> getting lockutils released as a library, but I haven't managed to get
> that done yet. If it is blocking other people I can prioritise that
> work to being higher on my todo list.
> 
> Part of the problem here is that its my first oslo graduation, so I
> need to figure out what to do...
> 
> Michael
> 
> --
> Rackspace Australia
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev [7]

 

Links:
--
[1] https://pypi.python.org/pypi/lockfile
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632857
[3] https://github.com/smontanaro/pylockfile
[4] https://github.com/smontanaro/pylockfile/pull/3
[5]
https://github.com/smontanaro/pylockfile/pull/3#issuecomment-32085554
[6]
http://lists.openstack.org/pipermail/openstack-dev/2013-December/021620.html
[7] 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] dependency analysis for graduating more oslo libraries

2014-01-15 Thread Doug Hellmann 
On Wed, Jan 15, 2014 at 6:51 AM, Victor Sergeyev wrote:

> Hello All.
>
> As for lockutils - a few days ago I wondered why we used custom oslo
> module instead of lockfile library [1]. AFAIK, it must be due to this bug
> [2] (please fix me, if I wrong).
>
> This library is available on github [3] and there is a pull-request fixing
> the bug [4], but unfortunately it hasn’t been merged yet. And seems that
> this project is not maintained anymore - author told, that he “haven't done
> anything with it in a few years” [5].
>
> So my question is - can we start maintaining this library (put it on
> stackforge) and use it instead of oslo.lockutils? Or maybe we could include
> parts of oslo.lockutils into lockfile? Or vice versa, incorporate lockfile
> into oslo.lockutils?
>

That might make sense.

It looks like the lockfile package on PyPI is meant to be portable to
Windows, and I'm not sure if we care about that. Does it provide any other
useful features or API improvements over the lockfiles module we have?
We'll still need a wrapper, since we have configuration options in our
module now.

How much work would it be to transition to the other library?

Doug


>
> [1] https://pypi.python.org/pypi/lockfile
> [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632857
> [3] https://github.com/smontanaro/pylockfile
> [4] https://github.com/smontanaro/pylockfile/pull/3
> [5] https://github.com/smontanaro/pylockfile/pull/3#issuecomment-32085554
>
>
> On Wed, Jan 15, 2014 at 1:00 AM, Michael Still  wrote:
>
>> On Wed, Jan 15, 2014 at 9:27 AM, Ben Nemec 
>> wrote:
>>
>> > It would be nice to get lockutils graduated to solve some of the issues
>> > mentioned in the oslo.db section, but I believe we do have an
>> outstanding
>> > question regarding its behavior without lock_path being set.  I think
>> Clint
>> > was on board with Sean's proposed solution after quite a bit of
>> discussion
>> > (
>> http://lists.openstack.org/pipermail/openstack-dev/2013-December/021620.html
>> ),
>> > so it's possible we could just restore that patch and call it done, but
>> it
>> > should probably be addressed somehow before graduation.
>>
>> I committed a while ago (at the last summit IIRC) to working on
>> getting lockutils released as a library, but I haven't managed to get
>> that done yet. If it is blocking other people I can prioritise that
>> work to being higher on my todo list.
>>
>> Part of the problem here is that its my first oslo graduation, so I
>> need to figure out what to do...
>>
>> Michael
>>
>> --
>> Rackspace Australia
>>
>> ___
>> 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] dependency analysis for graduating more oslo libraries

2014-01-15 Thread Doug Hellmann 
On Wed, Jan 15, 2014 at 5:24 AM, Flavio Percoco  wrote:

> On 14/01/14 14:48 -0500, Doug Hellmann wrote:
>
>> I've spent some time over the past day or two looking at the dependencies
>> between modules in the oslo incubator, trying to balance the desire to
>> have a
>> small number of libraries with themes that make sense and the need to
>> eliminate
>> circular dependencies.
>>
>> The results of all of this are posted to https://wiki.openstack.org/
>> wiki/Oslo/
>> GraduationStatus, where I have grouped the modules together into proposed
>> libraries.
>>
>> The dependencies between the libraries can be seen in several graphs I've
>> prepared and posted to https://wiki.openstack.org/wiki/Oslo/Dependencies
>>
>> Once we settle on the list of libraries, the next step is to look at the
>> lowest
>> level libraries to see what steps need to be taken before they can be
>> released.
>> I plan to start on that after the icehouse-2 deadline.
>>
>> Oslo team (and other interested parties), please take a look at the two
>> wiki
>> pages above and provide any feedback you have here on this ML thread.
>>
>
> +1 Thanks for the graphs.
>
> I took a look at it. There are some modules - oslo.cache, for example
> - which status should be updated - I don't think we'll need that
> memorycache module anymore once [0] lands.
>

Sure, I was tracking what to do with the files we have now. If memorycache
can be obsoleted, we'll have to update all of its current users to use the
replacement first. And (I think) obviously the new cache work you're doing
would go into that same oslo.cache library.



>
> In the dependencies diagrams, it looks like oslo.policy does not
> depend on anything. However, it should depend on oslo.text, oslo.log
> and oslo.utils. I'll update the graduation statys wiki.
>

Thanks. It looks like I may have missed a few others, too (I notice
reports doesn't list anything).



>
> Should we have a meeting after i-2 cut? I think we could go through
> the list again very quickly.
>

Yes, good idea. I'd like to try to get the status page in the wiki up to
date, and then use that to create a series of blueprints.

Doug



>
> [0] https://review.openstack.org/#/c/42878/
>
> Cheers,
> FF
>
> --
> @flaper87
> Flavio Percoco
>
> ___
> 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] dependency analysis for graduating more oslo libraries

2014-01-15 Thread Doug Hellmann 
On Tue, Jan 14, 2014 at 6:00 PM, Michael Still  wrote:

> On Wed, Jan 15, 2014 at 9:27 AM, Ben Nemec  wrote:
>
> > It would be nice to get lockutils graduated to solve some of the issues
> > mentioned in the oslo.db section, but I believe we do have an outstanding
> > question regarding its behavior without lock_path being set.  I think
> Clint
> > was on board with Sean's proposed solution after quite a bit of
> discussion
> > (
> http://lists.openstack.org/pipermail/openstack-dev/2013-December/021620.html
> ),
> > so it's possible we could just restore that patch and call it done, but
> it
> > should probably be addressed somehow before graduation.
>
> I committed a while ago (at the last summit IIRC) to working on
> getting lockutils released as a library, but I haven't managed to get
> that done yet. If it is blocking other people I can prioritise that
> work to being higher on my todo list.
>
> Part of the problem here is that its my first oslo graduation, so I
> need to figure out what to do...
>

Another item on my list for soon-ish is to create a todo list that we can
use for graduation blueprints, and some more detailed directions. Thierry
started with some info about setting up the devstack-gate integration under
https://wiki.openstack.org/wiki/Oslo#Graduation but that's only one piece.

Doug



>
> Michael
>
> --
> Rackspace Australia
>
> ___
> 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] dependency analysis for graduating more oslo libraries

2014-01-15 Thread Victor Sergeyev 
Hello All.

As for lockutils - a few days ago I wondered why we used custom oslo module
instead of lockfile library [1]. AFAIK, it must be due to this bug [2]
(please fix me, if I wrong).

This library is available on github [3] and there is a pull-request fixing
the bug [4], but unfortunately it hasn’t been merged yet. And seems that
this project is not maintained anymore - author told, that he “haven't done
anything with it in a few years” [5].

So my question is - can we start maintaining this library (put it on
stackforge) and use it instead of oslo.lockutils? Or maybe we could include
parts of oslo.lockutils into lockfile? Or vice versa, incorporate lockfile
into oslo.lockutils?

[1] https://pypi.python.org/pypi/lockfile
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632857
[3] https://github.com/smontanaro/pylockfile
[4] https://github.com/smontanaro/pylockfile/pull/3
[5] https://github.com/smontanaro/pylockfile/pull/3#issuecomment-32085554


On Wed, Jan 15, 2014 at 1:00 AM, Michael Still  wrote:

> On Wed, Jan 15, 2014 at 9:27 AM, Ben Nemec  wrote:
>
> > It would be nice to get lockutils graduated to solve some of the issues
> > mentioned in the oslo.db section, but I believe we do have an outstanding
> > question regarding its behavior without lock_path being set.  I think
> Clint
> > was on board with Sean's proposed solution after quite a bit of
> discussion
> > (
> http://lists.openstack.org/pipermail/openstack-dev/2013-December/021620.html
> ),
> > so it's possible we could just restore that patch and call it done, but
> it
> > should probably be addressed somehow before graduation.
>
> I committed a while ago (at the last summit IIRC) to working on
> getting lockutils released as a library, but I haven't managed to get
> that done yet. If it is blocking other people I can prioritise that
> work to being higher on my todo list.
>
> Part of the problem here is that its my first oslo graduation, so I
> need to figure out what to do...
>
> Michael
>
> --
> Rackspace Australia
>
> ___
> 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] dependency analysis for graduating more oslo libraries

2014-01-15 Thread Julien Danjou 
On Tue, Jan 14 2014, Ben Nemec wrote:

> It would be nice to get lockutils graduated to solve some of the issues
> mentioned in the oslo.db section, but I believe we do have an
> outstanding question regarding its behavior without lock_path being set.
> I think Clint was on board with Sean's proposed solution after quite a
> bit of discussion
> (http://lists.openstack.org/pipermail/openstack-dev/2013-December/021620.html),
> so it's possible we could just restore that patch and call it done, but
> it should probably be addressed somehow before graduation. 

FWIW I'm also trying to work on
https://blueprints.launchpad.net/oslo/+spec/lockutils-posix-ipc which
might change lockutils a bit.

-- 
Julien Danjou
# Free Software hacker # independent consultant
# http://julien.danjou.info


signature.asc
Description: 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] dependency analysis for graduating more oslo libraries

2014-01-15 Thread Flavio Percoco 

On 14/01/14 14:48 -0500, Doug Hellmann wrote:

I've spent some time over the past day or two looking at the dependencies
between modules in the oslo incubator, trying to balance the desire to have a
small number of libraries with themes that make sense and the need to eliminate
circular dependencies.

The results of all of this are posted to https://wiki.openstack.org/wiki/Oslo/
GraduationStatus, where I have grouped the modules together into proposed
libraries.

The dependencies between the libraries can be seen in several graphs I've
prepared and posted to https://wiki.openstack.org/wiki/Oslo/Dependencies

Once we settle on the list of libraries, the next step is to look at the lowest
level libraries to see what steps need to be taken before they can be released.
I plan to start on that after the icehouse-2 deadline.

Oslo team (and other interested parties), please take a look at the two wiki
pages above and provide any feedback you have here on this ML thread.


+1 Thanks for the graphs.

I took a look at it. There are some modules - oslo.cache, for example
- which status should be updated - I don't think we'll need that
memorycache module anymore once [0] lands.

In the dependencies diagrams, it looks like oslo.policy does not
depend on anything. However, it should depend on oslo.text, oslo.log
and oslo.utils. I'll update the graduation statys wiki.

Should we have a meeting after i-2 cut? I think we could go through
the list again very quickly.

[0] https://review.openstack.org/#/c/42878/

Cheers,
FF

--
@flaper87
Flavio Percoco


pgp302nNOA49v.pgp
Description: 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] dependency analysis for graduating more oslo libraries

2014-01-14 Thread Michael Still 
On Wed, Jan 15, 2014 at 9:27 AM, Ben Nemec  wrote:

> It would be nice to get lockutils graduated to solve some of the issues
> mentioned in the oslo.db section, but I believe we do have an outstanding
> question regarding its behavior without lock_path being set.  I think Clint
> was on board with Sean's proposed solution after quite a bit of discussion
> (http://lists.openstack.org/pipermail/openstack-dev/2013-December/021620.html),
> so it's possible we could just restore that patch and call it done, but it
> should probably be addressed somehow before graduation.

I committed a while ago (at the last summit IIRC) to working on
getting lockutils released as a library, but I haven't managed to get
that done yet. If it is blocking other people I can prioritise that
work to being higher on my todo list.

Part of the problem here is that its my first oslo graduation, so I
need to figure out what to do...

Michael

-- 
Rackspace Australia

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

Re: [openstack-dev] [oslo] dependency analysis for graduating more oslo libraries

2014-01-14 Thread Michael Still 
On Wed, Jan 15, 2014 at 8:28 AM, Doug Hellmann
 wrote:
> The notes are from the summit discussion, and I didn't open the bugs. I'll
> do that this week. Should I assign them to you?

If you assign them to me I will take a look at them.

Michael

-- 
Rackspace Australia

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

Re: [openstack-dev] [oslo] dependency analysis for graduating more oslo libraries

2014-01-14 Thread Ben Nemec 
 

On 2014-01-14 13:48, Doug Hellmann wrote: 

> I've spent some time over the past day or two looking at the dependencies 
> between modules in the oslo incubator, trying to balance the desire to have a 
> small number of libraries with themes that make sense and the need to 
> eliminate circular dependencies. 
> 
> The results of all of this are posted to 
> https://wiki.openstack.org/wiki/Oslo/GraduationStatus [1], where I have 
> grouped the modules together into proposed libraries. 
> 
> The dependencies between the libraries can be seen in several graphs I've 
> prepared and posted to https://wiki.openstack.org/wiki/Oslo/Dependencies [2] 
> 
> Once we settle on the list of libraries, the next step is to look at the 
> lowest level libraries to see what steps need to be taken before they can be 
> released. I plan to start on that after the icehouse-2 deadline. 
> 
> Oslo team (and other interested parties), please take a look at the two wiki 
> pages above and provide any feedback you have here on this ML thread. 
> 
> Thanks,
> Doug

It would be nice to get lockutils graduated to solve some of the issues
mentioned in the oslo.db section, but I believe we do have an
outstanding question regarding its behavior without lock_path being set.
I think Clint was on board with Sean's proposed solution after quite a
bit of discussion
(http://lists.openstack.org/pipermail/openstack-dev/2013-December/021620.html),
so it's possible we could just restore that patch and call it done, but
it should probably be addressed somehow before graduation. 

-Ben 
 

Links:
--
[1] https://wiki.openstack.org/wiki/Oslo/GraduationStatus
[2] https://wiki.openstack.org/wiki/Oslo/Dependencies
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo] dependency analysis for graduating more oslo libraries

2014-01-14 Thread Doug Hellmann 
The notes are from the summit discussion, and I didn't open the bugs. I'll
do that this week. Should I assign them to you?

Doug


On Tue, Jan 14, 2014 at 3:58 PM, Michael Still  wrote:

> You mention some concerns with processutils on that wiki page that I
> was unaware of. I can't find bugs for them either. Do you have any
> pointers to what is being referred to there?
>
> Thanks,
> Michael
>
> On Wed, Jan 15, 2014 at 6:48 AM, Doug Hellmann
>  wrote:
> > I've spent some time over the past day or two looking at the dependencies
> > between modules in the oslo incubator, trying to balance the desire to
> have
> > a small number of libraries with themes that make sense and the need to
> > eliminate circular dependencies.
> >
> > The results of all of this are posted to
> > https://wiki.openstack.org/wiki/Oslo/GraduationStatus, where I have
> grouped
> > the modules together into proposed libraries.
> >
> > The dependencies between the libraries can be seen in several graphs I've
> > prepared and posted to https://wiki.openstack.org/wiki/Oslo/Dependencies
> >
> > Once we settle on the list of libraries, the next step is to look at the
> > lowest level libraries to see what steps need to be taken before they
> can be
> > released. I plan to start on that after the icehouse-2 deadline.
> >
> > Oslo team (and other interested parties), please take a look at the two
> wiki
> > pages above and provide any feedback you have here on this ML thread.
> >
> > Thanks,
> > Doug
> >
> >
> > ___
> > OpenStack-dev mailing list
> > OpenStack-dev@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
>
>
> --
> Rackspace Australia
>
> ___
> 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] dependency analysis for graduating more oslo libraries

2014-01-14 Thread Michael Still 
You mention some concerns with processutils on that wiki page that I
was unaware of. I can't find bugs for them either. Do you have any
pointers to what is being referred to there?

Thanks,
Michael

On Wed, Jan 15, 2014 at 6:48 AM, Doug Hellmann
 wrote:
> I've spent some time over the past day or two looking at the dependencies
> between modules in the oslo incubator, trying to balance the desire to have
> a small number of libraries with themes that make sense and the need to
> eliminate circular dependencies.
>
> The results of all of this are posted to
> https://wiki.openstack.org/wiki/Oslo/GraduationStatus, where I have grouped
> the modules together into proposed libraries.
>
> The dependencies between the libraries can be seen in several graphs I've
> prepared and posted to https://wiki.openstack.org/wiki/Oslo/Dependencies
>
> Once we settle on the list of libraries, the next step is to look at the
> lowest level libraries to see what steps need to be taken before they can be
> released. I plan to start on that after the icehouse-2 deadline.
>
> Oslo team (and other interested parties), please take a look at the two wiki
> pages above and provide any feedback you have here on this ML thread.
>
> Thanks,
> Doug
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Rackspace Australia

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

[openstack-dev] [oslo] dependency analysis for graduating more oslo libraries

2014-01-14 Thread Doug Hellmann 
I've spent some time over the past day or two looking at the dependencies
between modules in the oslo incubator, trying to balance the desire to have
a small number of libraries with themes that make sense and the need to
eliminate circular dependencies.

The results of all of this are posted to
https://wiki.openstack.org/wiki/Oslo/GraduationStatus, where I have grouped
the modules together into proposed libraries.

The dependencies between the libraries can be seen in several graphs I've
prepared and posted to https://wiki.openstack.org/wiki/Oslo/Dependencies

Once we settle on the list of libraries, the next step is to look at the
lowest level libraries to see what steps need to be taken before they can
be released. I plan to start on that after the icehouse-2 deadline.

Oslo team (and other interested parties), please take a look at the two
wiki pages above and provide any feedback you have here on this ML thread.

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