Re: [openstack-dev] [oslo][db] oslo.db repository review request

2014-05-30 Thread Matt Riedemann



On 4/25/2014 7:46 AM, Doug Hellmann wrote:

On Fri, Apr 25, 2014 at 8:33 AM, Matt Riedemann
mrie...@linux.vnet.ibm.com wrote:



On 4/18/2014 1:18 PM, Doug Hellmann wrote:


Nice work, Victor!

I left a few comments on the commits that were made after the original
history was exported from the incubator. There were a couple of small
things to address before importing the library, and a couple that can
wait until we have the normal code review system. I'd say just add new
commits to fix the issues, rather than trying to amend the existing
commits.

We haven't really discussed how to communicate when we agree the new
repository is ready to be imported, but it seems reasonable to use the
patch in openstack-infra/config that will be used to do the import:
https://review.openstack.org/#/c/78955/

Doug

On Fri, Apr 18, 2014 at 10:28 AM, Victor Sergeyev
vserge...@mirantis.com wrote:


Hello all,

During Icehouse release cycle our team has been working on splitting of
openstack common db code into a separate library blueprint [1]. At the
moment the issues, mentioned in this bp and [2] are solved and we are
moving
forward to graduation of oslo.db. You can find the new oslo.db code at
[3]

So, before moving forward, I want to ask Oslo team to review oslo.db
repository [3] and especially the commit, that allows the unit tests to
pass
[4].

Thanks,
Victor

[1] https://blueprints.launchpad.net/oslo/+spec/oslo-db-lib
[2] https://wiki.openstack.org/wiki/Oslo/GraduationStatus#oslo.db
[3] https://github.com/malor/oslo.db
[4]

https://github.com/malor/oslo.db/commit/276f7570d7af4a7a62d0e1ffb4edf904cfbf0600

___
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



I'm probably just late to the party, but simple question: why is it in the
malor group in github rather than the openstack group, like oslo.messaging
and oslo.rootwrap?  Is that temporary or will it be moved at some point?


This is the copy of the code being prepared to import into a new
oslo.db repository. It's easier to set up that temporary hosting on
github. The repo has been approved to be imported, and after that
happens it will be hosted on our git server like all of the other oslo
libraries.

Doug



--

Thanks,

Matt Riedemann



___
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



Are there any status updates on where we are with this [1]?  I see that 
oslo.db is in git.openstack.org now [2].  There is a super-alpha dev 
package on pypi [3], are we waiting for an official release?


I'd like to start moving nova over to using oslo.db or at least get an 
idea for how much work it's going to be.  I don't imagine it's going to 
be that difficult since I think a lot of the oslo.db code originated in 
nova.


[1] https://review.openstack.org/#/c/91407/
[2] http://git.openstack.org/cgit/openstack/oslo.db/
[3] https://pypi.python.org/pypi/oslo.db/0.0.1.dev15.g7efbf12

--

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][db] oslo.db repository review request

2014-05-30 Thread Roman Podoliaka
Hi Matt,

We're waiting for a few important fixes to be merged (usage of
oslo.config, eventlet tpool support). Once those are merged, we'll cut
the initial release.

Thanks,
Roman

On Fri, May 30, 2014 at 5:19 PM, Matt Riedemann
mrie...@linux.vnet.ibm.com wrote:


 On 4/25/2014 7:46 AM, Doug Hellmann wrote:

 On Fri, Apr 25, 2014 at 8:33 AM, Matt Riedemann
 mrie...@linux.vnet.ibm.com wrote:



 On 4/18/2014 1:18 PM, Doug Hellmann wrote:


 Nice work, Victor!

 I left a few comments on the commits that were made after the original
 history was exported from the incubator. There were a couple of small
 things to address before importing the library, and a couple that can
 wait until we have the normal code review system. I'd say just add new
 commits to fix the issues, rather than trying to amend the existing
 commits.

 We haven't really discussed how to communicate when we agree the new
 repository is ready to be imported, but it seems reasonable to use the
 patch in openstack-infra/config that will be used to do the import:
 https://review.openstack.org/#/c/78955/

 Doug

 On Fri, Apr 18, 2014 at 10:28 AM, Victor Sergeyev
 vserge...@mirantis.com wrote:


 Hello all,

 During Icehouse release cycle our team has been working on splitting of
 openstack common db code into a separate library blueprint [1]. At the
 moment the issues, mentioned in this bp and [2] are solved and we are
 moving
 forward to graduation of oslo.db. You can find the new oslo.db code at
 [3]

 So, before moving forward, I want to ask Oslo team to review oslo.db
 repository [3] and especially the commit, that allows the unit tests to
 pass
 [4].

 Thanks,
 Victor

 [1] https://blueprints.launchpad.net/oslo/+spec/oslo-db-lib
 [2] https://wiki.openstack.org/wiki/Oslo/GraduationStatus#oslo.db
 [3] https://github.com/malor/oslo.db
 [4]


 https://github.com/malor/oslo.db/commit/276f7570d7af4a7a62d0e1ffb4edf904cfbf0600

 ___
 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


 I'm probably just late to the party, but simple question: why is it in
 the
 malor group in github rather than the openstack group, like
 oslo.messaging
 and oslo.rootwrap?  Is that temporary or will it be moved at some point?


 This is the copy of the code being prepared to import into a new
 oslo.db repository. It's easier to set up that temporary hosting on
 github. The repo has been approved to be imported, and after that
 happens it will be hosted on our git server like all of the other oslo
 libraries.

 Doug


 --

 Thanks,

 Matt Riedemann



 ___
 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


 Are there any status updates on where we are with this [1]?  I see that
 oslo.db is in git.openstack.org now [2].  There is a super-alpha dev package
 on pypi [3], are we waiting for an official release?

 I'd like to start moving nova over to using oslo.db or at least get an idea
 for how much work it's going to be.  I don't imagine it's going to be that
 difficult since I think a lot of the oslo.db code originated in nova.

 [1] https://review.openstack.org/#/c/91407/
 [2] http://git.openstack.org/cgit/openstack/oslo.db/
 [3] https://pypi.python.org/pypi/oslo.db/0.0.1.dev15.g7efbf12


 --

 Thanks,

 Matt Riedemann


 ___
 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][db] oslo.db repository review request

2014-05-30 Thread Sergey Lukjanov
Hey Roman,

will it be the alpha version that should not be used by other projects
or it'll be ready to use?

Thanks.

On Fri, May 30, 2014 at 6:36 PM, Roman Podoliaka
rpodoly...@mirantis.com wrote:
 Hi Matt,

 We're waiting for a few important fixes to be merged (usage of
 oslo.config, eventlet tpool support). Once those are merged, we'll cut
 the initial release.

 Thanks,
 Roman

 On Fri, May 30, 2014 at 5:19 PM, Matt Riedemann
 mrie...@linux.vnet.ibm.com wrote:


 On 4/25/2014 7:46 AM, Doug Hellmann wrote:

 On Fri, Apr 25, 2014 at 8:33 AM, Matt Riedemann
 mrie...@linux.vnet.ibm.com wrote:



 On 4/18/2014 1:18 PM, Doug Hellmann wrote:


 Nice work, Victor!

 I left a few comments on the commits that were made after the original
 history was exported from the incubator. There were a couple of small
 things to address before importing the library, and a couple that can
 wait until we have the normal code review system. I'd say just add new
 commits to fix the issues, rather than trying to amend the existing
 commits.

 We haven't really discussed how to communicate when we agree the new
 repository is ready to be imported, but it seems reasonable to use the
 patch in openstack-infra/config that will be used to do the import:
 https://review.openstack.org/#/c/78955/

 Doug

 On Fri, Apr 18, 2014 at 10:28 AM, Victor Sergeyev
 vserge...@mirantis.com wrote:


 Hello all,

 During Icehouse release cycle our team has been working on splitting of
 openstack common db code into a separate library blueprint [1]. At the
 moment the issues, mentioned in this bp and [2] are solved and we are
 moving
 forward to graduation of oslo.db. You can find the new oslo.db code at
 [3]

 So, before moving forward, I want to ask Oslo team to review oslo.db
 repository [3] and especially the commit, that allows the unit tests to
 pass
 [4].

 Thanks,
 Victor

 [1] https://blueprints.launchpad.net/oslo/+spec/oslo-db-lib
 [2] https://wiki.openstack.org/wiki/Oslo/GraduationStatus#oslo.db
 [3] https://github.com/malor/oslo.db
 [4]


 https://github.com/malor/oslo.db/commit/276f7570d7af4a7a62d0e1ffb4edf904cfbf0600

 ___
 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


 I'm probably just late to the party, but simple question: why is it in
 the
 malor group in github rather than the openstack group, like
 oslo.messaging
 and oslo.rootwrap?  Is that temporary or will it be moved at some point?


 This is the copy of the code being prepared to import into a new
 oslo.db repository. It's easier to set up that temporary hosting on
 github. The repo has been approved to be imported, and after that
 happens it will be hosted on our git server like all of the other oslo
 libraries.

 Doug


 --

 Thanks,

 Matt Riedemann



 ___
 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


 Are there any status updates on where we are with this [1]?  I see that
 oslo.db is in git.openstack.org now [2].  There is a super-alpha dev package
 on pypi [3], are we waiting for an official release?

 I'd like to start moving nova over to using oslo.db or at least get an idea
 for how much work it's going to be.  I don't imagine it's going to be that
 difficult since I think a lot of the oslo.db code originated in nova.

 [1] https://review.openstack.org/#/c/91407/
 [2] http://git.openstack.org/cgit/openstack/oslo.db/
 [3] https://pypi.python.org/pypi/oslo.db/0.0.1.dev15.g7efbf12


 --

 Thanks,

 Matt Riedemann


 ___
 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



-- 
Sincerely yours,
Sergey Lukjanov
Sahara Technical Lead
(OpenStack Data Processing)
Principal Software Engineer
Mirantis Inc.

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


Re: [openstack-dev] [oslo][db] oslo.db repository review request

2014-05-30 Thread Doug Hellmann
On Fri, May 30, 2014 at 11:06 AM, Sergey Lukjanov
slukja...@mirantis.com wrote:
 Hey Roman,

 will it be the alpha version that should not be used by other projects
 or it'll be ready to use?

The current plan is to do alpha releases of oslo libraries during this
cycle, with a final official release at the end. We're close to
finishing the infra work we need to make that possible.

Doug



 Thanks.

 On Fri, May 30, 2014 at 6:36 PM, Roman Podoliaka
 rpodoly...@mirantis.com wrote:
 Hi Matt,

 We're waiting for a few important fixes to be merged (usage of
 oslo.config, eventlet tpool support). Once those are merged, we'll cut
 the initial release.

 Thanks,
 Roman

 On Fri, May 30, 2014 at 5:19 PM, Matt Riedemann
 mrie...@linux.vnet.ibm.com wrote:


 On 4/25/2014 7:46 AM, Doug Hellmann wrote:

 On Fri, Apr 25, 2014 at 8:33 AM, Matt Riedemann
 mrie...@linux.vnet.ibm.com wrote:



 On 4/18/2014 1:18 PM, Doug Hellmann wrote:


 Nice work, Victor!

 I left a few comments on the commits that were made after the original
 history was exported from the incubator. There were a couple of small
 things to address before importing the library, and a couple that can
 wait until we have the normal code review system. I'd say just add new
 commits to fix the issues, rather than trying to amend the existing
 commits.

 We haven't really discussed how to communicate when we agree the new
 repository is ready to be imported, but it seems reasonable to use the
 patch in openstack-infra/config that will be used to do the import:
 https://review.openstack.org/#/c/78955/

 Doug

 On Fri, Apr 18, 2014 at 10:28 AM, Victor Sergeyev
 vserge...@mirantis.com wrote:


 Hello all,

 During Icehouse release cycle our team has been working on splitting of
 openstack common db code into a separate library blueprint [1]. At the
 moment the issues, mentioned in this bp and [2] are solved and we are
 moving
 forward to graduation of oslo.db. You can find the new oslo.db code at
 [3]

 So, before moving forward, I want to ask Oslo team to review oslo.db
 repository [3] and especially the commit, that allows the unit tests to
 pass
 [4].

 Thanks,
 Victor

 [1] https://blueprints.launchpad.net/oslo/+spec/oslo-db-lib
 [2] https://wiki.openstack.org/wiki/Oslo/GraduationStatus#oslo.db
 [3] https://github.com/malor/oslo.db
 [4]


 https://github.com/malor/oslo.db/commit/276f7570d7af4a7a62d0e1ffb4edf904cfbf0600

 ___
 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


 I'm probably just late to the party, but simple question: why is it in
 the
 malor group in github rather than the openstack group, like
 oslo.messaging
 and oslo.rootwrap?  Is that temporary or will it be moved at some point?


 This is the copy of the code being prepared to import into a new
 oslo.db repository. It's easier to set up that temporary hosting on
 github. The repo has been approved to be imported, and after that
 happens it will be hosted on our git server like all of the other oslo
 libraries.

 Doug


 --

 Thanks,

 Matt Riedemann



 ___
 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


 Are there any status updates on where we are with this [1]?  I see that
 oslo.db is in git.openstack.org now [2].  There is a super-alpha dev package
 on pypi [3], are we waiting for an official release?

 I'd like to start moving nova over to using oslo.db or at least get an idea
 for how much work it's going to be.  I don't imagine it's going to be that
 difficult since I think a lot of the oslo.db code originated in nova.

 [1] https://review.openstack.org/#/c/91407/
 [2] http://git.openstack.org/cgit/openstack/oslo.db/
 [3] https://pypi.python.org/pypi/oslo.db/0.0.1.dev15.g7efbf12


 --

 Thanks,

 Matt Riedemann


 ___
 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



 --
 Sincerely yours,
 Sergey Lukjanov
 Sahara Technical Lead
 (OpenStack Data Processing)
 Principal Software Engineer
 Mirantis Inc.

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 

Re: [openstack-dev] [oslo][db] oslo.db repository review request

2014-05-30 Thread Sergey Lukjanov
So, it means that we'll be able to migrate to oslo.db lib in the end
of Juno? or early K?

On Fri, May 30, 2014 at 7:30 PM, Doug Hellmann
doug.hellm...@dreamhost.com wrote:
 On Fri, May 30, 2014 at 11:06 AM, Sergey Lukjanov
 slukja...@mirantis.com wrote:
 Hey Roman,

 will it be the alpha version that should not be used by other projects
 or it'll be ready to use?

 The current plan is to do alpha releases of oslo libraries during this
 cycle, with a final official release at the end. We're close to
 finishing the infra work we need to make that possible.

 Doug



 Thanks.

 On Fri, May 30, 2014 at 6:36 PM, Roman Podoliaka
 rpodoly...@mirantis.com wrote:
 Hi Matt,

 We're waiting for a few important fixes to be merged (usage of
 oslo.config, eventlet tpool support). Once those are merged, we'll cut
 the initial release.

 Thanks,
 Roman

 On Fri, May 30, 2014 at 5:19 PM, Matt Riedemann
 mrie...@linux.vnet.ibm.com wrote:


 On 4/25/2014 7:46 AM, Doug Hellmann wrote:

 On Fri, Apr 25, 2014 at 8:33 AM, Matt Riedemann
 mrie...@linux.vnet.ibm.com wrote:



 On 4/18/2014 1:18 PM, Doug Hellmann wrote:


 Nice work, Victor!

 I left a few comments on the commits that were made after the original
 history was exported from the incubator. There were a couple of small
 things to address before importing the library, and a couple that can
 wait until we have the normal code review system. I'd say just add new
 commits to fix the issues, rather than trying to amend the existing
 commits.

 We haven't really discussed how to communicate when we agree the new
 repository is ready to be imported, but it seems reasonable to use the
 patch in openstack-infra/config that will be used to do the import:
 https://review.openstack.org/#/c/78955/

 Doug

 On Fri, Apr 18, 2014 at 10:28 AM, Victor Sergeyev
 vserge...@mirantis.com wrote:


 Hello all,

 During Icehouse release cycle our team has been working on splitting of
 openstack common db code into a separate library blueprint [1]. At the
 moment the issues, mentioned in this bp and [2] are solved and we are
 moving
 forward to graduation of oslo.db. You can find the new oslo.db code at
 [3]

 So, before moving forward, I want to ask Oslo team to review oslo.db
 repository [3] and especially the commit, that allows the unit tests to
 pass
 [4].

 Thanks,
 Victor

 [1] https://blueprints.launchpad.net/oslo/+spec/oslo-db-lib
 [2] https://wiki.openstack.org/wiki/Oslo/GraduationStatus#oslo.db
 [3] https://github.com/malor/oslo.db
 [4]


 https://github.com/malor/oslo.db/commit/276f7570d7af4a7a62d0e1ffb4edf904cfbf0600

 ___
 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


 I'm probably just late to the party, but simple question: why is it in
 the
 malor group in github rather than the openstack group, like
 oslo.messaging
 and oslo.rootwrap?  Is that temporary or will it be moved at some point?


 This is the copy of the code being prepared to import into a new
 oslo.db repository. It's easier to set up that temporary hosting on
 github. The repo has been approved to be imported, and after that
 happens it will be hosted on our git server like all of the other oslo
 libraries.

 Doug


 --

 Thanks,

 Matt Riedemann



 ___
 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


 Are there any status updates on where we are with this [1]?  I see that
 oslo.db is in git.openstack.org now [2].  There is a super-alpha dev 
 package
 on pypi [3], are we waiting for an official release?

 I'd like to start moving nova over to using oslo.db or at least get an idea
 for how much work it's going to be.  I don't imagine it's going to be that
 difficult since I think a lot of the oslo.db code originated in nova.

 [1] https://review.openstack.org/#/c/91407/
 [2] http://git.openstack.org/cgit/openstack/oslo.db/
 [3] https://pypi.python.org/pypi/oslo.db/0.0.1.dev15.g7efbf12


 --

 Thanks,

 Matt Riedemann


 ___
 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



 --
 Sincerely yours,
 Sergey Lukjanov
 Sahara Technical Lead
 (OpenStack Data Processing)
 Principal Software Engineer
 Mirantis 

Re: [openstack-dev] [oslo][db] oslo.db repository review request

2014-05-30 Thread Roman Podoliaka
Hi Sergey,

tl;dr

I'd like to be a ready to use version, but not 1.0.0.

So it's a good question and I'd like to hear more input on this from all.

If we start from 1.0.0, this will mean that we'll be very limited in
terms of changes to public API we can make without bumping the MAJOR
part of the version number. I don't expect the number of those changes
to be big, but I also don't want us to happen in a situation when we
have oslo.db 3.0.0 in a few months (if we follow semver
pragmatically).

Perhaps, we should stick to 0.MINOR.PATCH versioning for now (as e.g.
SQLAlchemy and TripleO projects do)? These won't be alphas, but rather
ready to use versions. And we would still have a bit more 'freedom' to
do small API changes bumping the MINOR part of the version number (we
could also do intermediate releases deprecating some stuff, so we
don't break people projects every time we make some API change).

Thanks,
Roman

On Fri, May 30, 2014 at 6:06 PM, Sergey Lukjanov slukja...@mirantis.com wrote:
 Hey Roman,

 will it be the alpha version that should not be used by other projects
 or it'll be ready to use?

 Thanks.

 On Fri, May 30, 2014 at 6:36 PM, Roman Podoliaka
 rpodoly...@mirantis.com wrote:
 Hi Matt,

 We're waiting for a few important fixes to be merged (usage of
 oslo.config, eventlet tpool support). Once those are merged, we'll cut
 the initial release.

 Thanks,
 Roman

 On Fri, May 30, 2014 at 5:19 PM, Matt Riedemann
 mrie...@linux.vnet.ibm.com wrote:


 On 4/25/2014 7:46 AM, Doug Hellmann wrote:

 On Fri, Apr 25, 2014 at 8:33 AM, Matt Riedemann
 mrie...@linux.vnet.ibm.com wrote:



 On 4/18/2014 1:18 PM, Doug Hellmann wrote:


 Nice work, Victor!

 I left a few comments on the commits that were made after the original
 history was exported from the incubator. There were a couple of small
 things to address before importing the library, and a couple that can
 wait until we have the normal code review system. I'd say just add new
 commits to fix the issues, rather than trying to amend the existing
 commits.

 We haven't really discussed how to communicate when we agree the new
 repository is ready to be imported, but it seems reasonable to use the
 patch in openstack-infra/config that will be used to do the import:
 https://review.openstack.org/#/c/78955/

 Doug

 On Fri, Apr 18, 2014 at 10:28 AM, Victor Sergeyev
 vserge...@mirantis.com wrote:


 Hello all,

 During Icehouse release cycle our team has been working on splitting of
 openstack common db code into a separate library blueprint [1]. At the
 moment the issues, mentioned in this bp and [2] are solved and we are
 moving
 forward to graduation of oslo.db. You can find the new oslo.db code at
 [3]

 So, before moving forward, I want to ask Oslo team to review oslo.db
 repository [3] and especially the commit, that allows the unit tests to
 pass
 [4].

 Thanks,
 Victor

 [1] https://blueprints.launchpad.net/oslo/+spec/oslo-db-lib
 [2] https://wiki.openstack.org/wiki/Oslo/GraduationStatus#oslo.db
 [3] https://github.com/malor/oslo.db
 [4]


 https://github.com/malor/oslo.db/commit/276f7570d7af4a7a62d0e1ffb4edf904cfbf0600

 ___
 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


 I'm probably just late to the party, but simple question: why is it in
 the
 malor group in github rather than the openstack group, like
 oslo.messaging
 and oslo.rootwrap?  Is that temporary or will it be moved at some point?


 This is the copy of the code being prepared to import into a new
 oslo.db repository. It's easier to set up that temporary hosting on
 github. The repo has been approved to be imported, and after that
 happens it will be hosted on our git server like all of the other oslo
 libraries.

 Doug


 --

 Thanks,

 Matt Riedemann



 ___
 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


 Are there any status updates on where we are with this [1]?  I see that
 oslo.db is in git.openstack.org now [2].  There is a super-alpha dev package
 on pypi [3], are we waiting for an official release?

 I'd like to start moving nova over to using oslo.db or at least get an idea
 for how much work it's going to be.  I don't imagine it's going to be that
 difficult since I think a lot of the oslo.db code originated in nova.

 [1] https://review.openstack.org/#/c/91407/
 [2] http://git.openstack.org/cgit/openstack/oslo.db/
 [3] 

Re: [openstack-dev] [oslo][db] oslo.db repository review request

2014-05-30 Thread Igor Kalnitsky
Hi guys,

+1 to Roman's suggestion.

I think we have to use 0.MINOR.PATCH at least during a few cycles.
API changes aren't a problem if we use a specific (frozen) version in
requirements.

Thanks,
Igor


On Fri, May 30, 2014 at 6:37 PM, Roman Podoliaka rpodoly...@mirantis.com
wrote:

 Hi Sergey,

 tl;dr

 I'd like to be a ready to use version, but not 1.0.0.

 So it's a good question and I'd like to hear more input on this from all.

 If we start from 1.0.0, this will mean that we'll be very limited in
 terms of changes to public API we can make without bumping the MAJOR
 part of the version number. I don't expect the number of those changes
 to be big, but I also don't want us to happen in a situation when we
 have oslo.db 3.0.0 in a few months (if we follow semver
 pragmatically).

 Perhaps, we should stick to 0.MINOR.PATCH versioning for now (as e.g.
 SQLAlchemy and TripleO projects do)? These won't be alphas, but rather
 ready to use versions. And we would still have a bit more 'freedom' to
 do small API changes bumping the MINOR part of the version number (we
 could also do intermediate releases deprecating some stuff, so we
 don't break people projects every time we make some API change).

 Thanks,
 Roman

 On Fri, May 30, 2014 at 6:06 PM, Sergey Lukjanov slukja...@mirantis.com
 wrote:
  Hey Roman,
 
  will it be the alpha version that should not be used by other projects
  or it'll be ready to use?
 
  Thanks.
 
  On Fri, May 30, 2014 at 6:36 PM, Roman Podoliaka
  rpodoly...@mirantis.com wrote:
  Hi Matt,
 
  We're waiting for a few important fixes to be merged (usage of
  oslo.config, eventlet tpool support). Once those are merged, we'll cut
  the initial release.
 
  Thanks,
  Roman
 
  On Fri, May 30, 2014 at 5:19 PM, Matt Riedemann
  mrie...@linux.vnet.ibm.com wrote:
 
 
  On 4/25/2014 7:46 AM, Doug Hellmann wrote:
 
  On Fri, Apr 25, 2014 at 8:33 AM, Matt Riedemann
  mrie...@linux.vnet.ibm.com wrote:
 
 
 
  On 4/18/2014 1:18 PM, Doug Hellmann wrote:
 
 
  Nice work, Victor!
 
  I left a few comments on the commits that were made after the
 original
  history was exported from the incubator. There were a couple of
 small
  things to address before importing the library, and a couple that
 can
  wait until we have the normal code review system. I'd say just add
 new
  commits to fix the issues, rather than trying to amend the existing
  commits.
 
  We haven't really discussed how to communicate when we agree the new
  repository is ready to be imported, but it seems reasonable to use
 the
  patch in openstack-infra/config that will be used to do the import:
  https://review.openstack.org/#/c/78955/
 
  Doug
 
  On Fri, Apr 18, 2014 at 10:28 AM, Victor Sergeyev
  vserge...@mirantis.com wrote:
 
 
  Hello all,
 
  During Icehouse release cycle our team has been working on
 splitting of
  openstack common db code into a separate library blueprint [1]. At
 the
  moment the issues, mentioned in this bp and [2] are solved and we
 are
  moving
  forward to graduation of oslo.db. You can find the new oslo.db
 code at
  [3]
 
  So, before moving forward, I want to ask Oslo team to review
 oslo.db
  repository [3] and especially the commit, that allows the unit
 tests to
  pass
  [4].
 
  Thanks,
  Victor
 
  [1] https://blueprints.launchpad.net/oslo/+spec/oslo-db-lib
  [2] https://wiki.openstack.org/wiki/Oslo/GraduationStatus#oslo.db
  [3] https://github.com/malor/oslo.db
  [4]
 
 
 
 https://github.com/malor/oslo.db/commit/276f7570d7af4a7a62d0e1ffb4edf904cfbf0600
 
  ___
  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
 
 
  I'm probably just late to the party, but simple question: why is it
 in
  the
  malor group in github rather than the openstack group, like
  oslo.messaging
  and oslo.rootwrap?  Is that temporary or will it be moved at some
 point?
 
 
  This is the copy of the code being prepared to import into a new
  oslo.db repository. It's easier to set up that temporary hosting on
  github. The repo has been approved to be imported, and after that
  happens it will be hosted on our git server like all of the other oslo
  libraries.
 
  Doug
 
 
  --
 
  Thanks,
 
  Matt Riedemann
 
 
 
  ___
  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
 
 
  Are there any status updates on where we are with this [1]?  I see that
  oslo.db is in git.openstack.org now [2].  There is a 

Re: [openstack-dev] [oslo][db] oslo.db repository review request

2014-05-30 Thread Doug Hellmann
No matter what version number we use, we will have to be careful about
API changes. We cannot have 2 versions of the same library installed
at the same time, so in order for devstack to work (and therefore the
gate), we will have to make all changes backwards-compatible and
support older APIs until our projects have migrated to the new APIs.

This is *exactly* why we have the Oslo incubator. It gives us a place
to work out stable APIs in a way that does not restrict when and how
updates can be made. since the syncs can be handled by projects at
their own pace.

Doug

On Fri, May 30, 2014 at 11:37 AM, Roman Podoliaka
rpodoly...@mirantis.com wrote:
 Hi Sergey,

 tl;dr

 I'd like to be a ready to use version, but not 1.0.0.

 So it's a good question and I'd like to hear more input on this from all.

 If we start from 1.0.0, this will mean that we'll be very limited in
 terms of changes to public API we can make without bumping the MAJOR
 part of the version number. I don't expect the number of those changes
 to be big, but I also don't want us to happen in a situation when we
 have oslo.db 3.0.0 in a few months (if we follow semver
 pragmatically).

 Perhaps, we should stick to 0.MINOR.PATCH versioning for now (as e.g.
 SQLAlchemy and TripleO projects do)? These won't be alphas, but rather
 ready to use versions. And we would still have a bit more 'freedom' to
 do small API changes bumping the MINOR part of the version number (we
 could also do intermediate releases deprecating some stuff, so we
 don't break people projects every time we make some API change).

 Thanks,
 Roman

 On Fri, May 30, 2014 at 6:06 PM, Sergey Lukjanov slukja...@mirantis.com 
 wrote:
 Hey Roman,

 will it be the alpha version that should not be used by other projects
 or it'll be ready to use?

 Thanks.

 On Fri, May 30, 2014 at 6:36 PM, Roman Podoliaka
 rpodoly...@mirantis.com wrote:
 Hi Matt,

 We're waiting for a few important fixes to be merged (usage of
 oslo.config, eventlet tpool support). Once those are merged, we'll cut
 the initial release.

 Thanks,
 Roman

 On Fri, May 30, 2014 at 5:19 PM, Matt Riedemann
 mrie...@linux.vnet.ibm.com wrote:


 On 4/25/2014 7:46 AM, Doug Hellmann wrote:

 On Fri, Apr 25, 2014 at 8:33 AM, Matt Riedemann
 mrie...@linux.vnet.ibm.com wrote:



 On 4/18/2014 1:18 PM, Doug Hellmann wrote:


 Nice work, Victor!

 I left a few comments on the commits that were made after the original
 history was exported from the incubator. There were a couple of small
 things to address before importing the library, and a couple that can
 wait until we have the normal code review system. I'd say just add new
 commits to fix the issues, rather than trying to amend the existing
 commits.

 We haven't really discussed how to communicate when we agree the new
 repository is ready to be imported, but it seems reasonable to use the
 patch in openstack-infra/config that will be used to do the import:
 https://review.openstack.org/#/c/78955/

 Doug

 On Fri, Apr 18, 2014 at 10:28 AM, Victor Sergeyev
 vserge...@mirantis.com wrote:


 Hello all,

 During Icehouse release cycle our team has been working on splitting of
 openstack common db code into a separate library blueprint [1]. At the
 moment the issues, mentioned in this bp and [2] are solved and we are
 moving
 forward to graduation of oslo.db. You can find the new oslo.db code at
 [3]

 So, before moving forward, I want to ask Oslo team to review oslo.db
 repository [3] and especially the commit, that allows the unit tests to
 pass
 [4].

 Thanks,
 Victor

 [1] https://blueprints.launchpad.net/oslo/+spec/oslo-db-lib
 [2] https://wiki.openstack.org/wiki/Oslo/GraduationStatus#oslo.db
 [3] https://github.com/malor/oslo.db
 [4]


 https://github.com/malor/oslo.db/commit/276f7570d7af4a7a62d0e1ffb4edf904cfbf0600

 ___
 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


 I'm probably just late to the party, but simple question: why is it in
 the
 malor group in github rather than the openstack group, like
 oslo.messaging
 and oslo.rootwrap?  Is that temporary or will it be moved at some point?


 This is the copy of the code being prepared to import into a new
 oslo.db repository. It's easier to set up that temporary hosting on
 github. The repo has been approved to be imported, and after that
 happens it will be hosted on our git server like all of the other oslo
 libraries.

 Doug


 --

 Thanks,

 Matt Riedemann



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


 ___
 OpenStack-dev mailing list
 

Re: [openstack-dev] [oslo][db] oslo.db repository review request

2014-05-30 Thread Doug Hellmann
On Fri, May 30, 2014 at 11:37 AM, Sergey Lukjanov
slukja...@mirantis.com wrote:
 So, it means that we'll be able to migrate to oslo.db lib in the end
 of Juno? or early K?


Projects will be able to start migrating to the oslo.db during this
cycle. We will have a non-alpha release by the end of Juno.

Doug


 On Fri, May 30, 2014 at 7:30 PM, Doug Hellmann
 doug.hellm...@dreamhost.com wrote:
 On Fri, May 30, 2014 at 11:06 AM, Sergey Lukjanov
 slukja...@mirantis.com wrote:
 Hey Roman,

 will it be the alpha version that should not be used by other projects
 or it'll be ready to use?

 The current plan is to do alpha releases of oslo libraries during this
 cycle, with a final official release at the end. We're close to
 finishing the infra work we need to make that possible.

 Doug



 Thanks.

 On Fri, May 30, 2014 at 6:36 PM, Roman Podoliaka
 rpodoly...@mirantis.com wrote:
 Hi Matt,

 We're waiting for a few important fixes to be merged (usage of
 oslo.config, eventlet tpool support). Once those are merged, we'll cut
 the initial release.

 Thanks,
 Roman

 On Fri, May 30, 2014 at 5:19 PM, Matt Riedemann
 mrie...@linux.vnet.ibm.com wrote:


 On 4/25/2014 7:46 AM, Doug Hellmann wrote:

 On Fri, Apr 25, 2014 at 8:33 AM, Matt Riedemann
 mrie...@linux.vnet.ibm.com wrote:



 On 4/18/2014 1:18 PM, Doug Hellmann wrote:


 Nice work, Victor!

 I left a few comments on the commits that were made after the original
 history was exported from the incubator. There were a couple of small
 things to address before importing the library, and a couple that can
 wait until we have the normal code review system. I'd say just add new
 commits to fix the issues, rather than trying to amend the existing
 commits.

 We haven't really discussed how to communicate when we agree the new
 repository is ready to be imported, but it seems reasonable to use the
 patch in openstack-infra/config that will be used to do the import:
 https://review.openstack.org/#/c/78955/

 Doug

 On Fri, Apr 18, 2014 at 10:28 AM, Victor Sergeyev
 vserge...@mirantis.com wrote:


 Hello all,

 During Icehouse release cycle our team has been working on splitting 
 of
 openstack common db code into a separate library blueprint [1]. At the
 moment the issues, mentioned in this bp and [2] are solved and we are
 moving
 forward to graduation of oslo.db. You can find the new oslo.db code at
 [3]

 So, before moving forward, I want to ask Oslo team to review oslo.db
 repository [3] and especially the commit, that allows the unit tests 
 to
 pass
 [4].

 Thanks,
 Victor

 [1] https://blueprints.launchpad.net/oslo/+spec/oslo-db-lib
 [2] https://wiki.openstack.org/wiki/Oslo/GraduationStatus#oslo.db
 [3] https://github.com/malor/oslo.db
 [4]


 https://github.com/malor/oslo.db/commit/276f7570d7af4a7a62d0e1ffb4edf904cfbf0600

 ___
 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


 I'm probably just late to the party, but simple question: why is it in
 the
 malor group in github rather than the openstack group, like
 oslo.messaging
 and oslo.rootwrap?  Is that temporary or will it be moved at some point?


 This is the copy of the code being prepared to import into a new
 oslo.db repository. It's easier to set up that temporary hosting on
 github. The repo has been approved to be imported, and after that
 happens it will be hosted on our git server like all of the other oslo
 libraries.

 Doug


 --

 Thanks,

 Matt Riedemann



 ___
 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


 Are there any status updates on where we are with this [1]?  I see that
 oslo.db is in git.openstack.org now [2].  There is a super-alpha dev 
 package
 on pypi [3], are we waiting for an official release?

 I'd like to start moving nova over to using oslo.db or at least get an 
 idea
 for how much work it's going to be.  I don't imagine it's going to be that
 difficult since I think a lot of the oslo.db code originated in nova.

 [1] https://review.openstack.org/#/c/91407/
 [2] http://git.openstack.org/cgit/openstack/oslo.db/
 [3] https://pypi.python.org/pypi/oslo.db/0.0.1.dev15.g7efbf12


 --

 Thanks,

 Matt Riedemann


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

 ___
 OpenStack-dev mailing list
 

Re: [openstack-dev] [oslo][db] oslo.db repository review request

2014-05-30 Thread Sergey Lukjanov
Doug, thanks for the clarification re migration time.

I'm absolutely agree with point about need to keep API backward compat.

On Sat, May 31, 2014 at 1:04 AM, Doug Hellmann
doug.hellm...@dreamhost.com wrote:
 No matter what version number we use, we will have to be careful about
 API changes. We cannot have 2 versions of the same library installed
 at the same time, so in order for devstack to work (and therefore the
 gate), we will have to make all changes backwards-compatible and
 support older APIs until our projects have migrated to the new APIs.

 This is *exactly* why we have the Oslo incubator. It gives us a place
 to work out stable APIs in a way that does not restrict when and how
 updates can be made. since the syncs can be handled by projects at
 their own pace.

 Doug

 On Fri, May 30, 2014 at 11:37 AM, Roman Podoliaka
 rpodoly...@mirantis.com wrote:
 Hi Sergey,

 tl;dr

 I'd like to be a ready to use version, but not 1.0.0.

 So it's a good question and I'd like to hear more input on this from all.

 If we start from 1.0.0, this will mean that we'll be very limited in
 terms of changes to public API we can make without bumping the MAJOR
 part of the version number. I don't expect the number of those changes
 to be big, but I also don't want us to happen in a situation when we
 have oslo.db 3.0.0 in a few months (if we follow semver
 pragmatically).

 Perhaps, we should stick to 0.MINOR.PATCH versioning for now (as e.g.
 SQLAlchemy and TripleO projects do)? These won't be alphas, but rather
 ready to use versions. And we would still have a bit more 'freedom' to
 do small API changes bumping the MINOR part of the version number (we
 could also do intermediate releases deprecating some stuff, so we
 don't break people projects every time we make some API change).

 Thanks,
 Roman

 On Fri, May 30, 2014 at 6:06 PM, Sergey Lukjanov slukja...@mirantis.com 
 wrote:
 Hey Roman,

 will it be the alpha version that should not be used by other projects
 or it'll be ready to use?

 Thanks.

 On Fri, May 30, 2014 at 6:36 PM, Roman Podoliaka
 rpodoly...@mirantis.com wrote:
 Hi Matt,

 We're waiting for a few important fixes to be merged (usage of
 oslo.config, eventlet tpool support). Once those are merged, we'll cut
 the initial release.

 Thanks,
 Roman

 On Fri, May 30, 2014 at 5:19 PM, Matt Riedemann
 mrie...@linux.vnet.ibm.com wrote:


 On 4/25/2014 7:46 AM, Doug Hellmann wrote:

 On Fri, Apr 25, 2014 at 8:33 AM, Matt Riedemann
 mrie...@linux.vnet.ibm.com wrote:



 On 4/18/2014 1:18 PM, Doug Hellmann wrote:


 Nice work, Victor!

 I left a few comments on the commits that were made after the original
 history was exported from the incubator. There were a couple of small
 things to address before importing the library, and a couple that can
 wait until we have the normal code review system. I'd say just add new
 commits to fix the issues, rather than trying to amend the existing
 commits.

 We haven't really discussed how to communicate when we agree the new
 repository is ready to be imported, but it seems reasonable to use the
 patch in openstack-infra/config that will be used to do the import:
 https://review.openstack.org/#/c/78955/

 Doug

 On Fri, Apr 18, 2014 at 10:28 AM, Victor Sergeyev
 vserge...@mirantis.com wrote:


 Hello all,

 During Icehouse release cycle our team has been working on splitting 
 of
 openstack common db code into a separate library blueprint [1]. At the
 moment the issues, mentioned in this bp and [2] are solved and we are
 moving
 forward to graduation of oslo.db. You can find the new oslo.db code at
 [3]

 So, before moving forward, I want to ask Oslo team to review oslo.db
 repository [3] and especially the commit, that allows the unit tests 
 to
 pass
 [4].

 Thanks,
 Victor

 [1] https://blueprints.launchpad.net/oslo/+spec/oslo-db-lib
 [2] https://wiki.openstack.org/wiki/Oslo/GraduationStatus#oslo.db
 [3] https://github.com/malor/oslo.db
 [4]


 https://github.com/malor/oslo.db/commit/276f7570d7af4a7a62d0e1ffb4edf904cfbf0600

 ___
 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


 I'm probably just late to the party, but simple question: why is it in
 the
 malor group in github rather than the openstack group, like
 oslo.messaging
 and oslo.rootwrap?  Is that temporary or will it be moved at some point?


 This is the copy of the code being prepared to import into a new
 oslo.db repository. It's easier to set up that temporary hosting on
 github. The repo has been approved to be imported, and after that
 happens it will be hosted on our git server like all of the other oslo
 libraries.

 Doug


 --

 Thanks,

 Matt Riedemann



 

Re: [openstack-dev] [oslo][db] oslo.db repository review request

2014-05-21 Thread Ben Nemec
On 05/14/2014 09:38 AM, Victor Stinner wrote:
 Le mardi 13 mai 2014, 07:31:34 Doug Hellmann a écrit :
 Since we think we have been able to solve all of the issues we were
 having with namespace packages before, ...
 
 I just tried to start my DevStack and again, I had issues with a builtin 
 olso module: import oslo.config doesn't work, whereas olso.config was 
 installed (system wide) by pip.
 
 pip list|grep olso told me that oslo.config, oslo.messaging, oslo.rootwrap 
 and oslo.vmware are installed.
 
 My workaround is to uninstall all olso modules:
 sudo pip uninstall oslo.config oslo.messaging oslo.rootwrap oslo.vmware
 
 ./stack.sh reinstalls them and now it works.

One of the parts of the fix was to have Devstack stop installing oslo.*
packages as editable, so if you first ran it before that changed then
this makes sense.

 
 --
 
 Current state:
 
 haypo@devstackdev$ pip list|grep oslo
 oslo.config (1.3.0a0.40.gb347519)
 oslo.messaging (1.3.0.8.gc0c8557)
 oslo.rootwrap (1.2.0)
 oslo.vmware (0.3.1.g49097c0)
 
 haypo@devstackdev$ python
 Python 2.7.5 (default, Feb 19 2014, 13:47:28) 
 [GCC 4.8.2 20131212 (Red Hat 4.8.2-7)] on linux2
 Type help, copyright, credits or license for more information.
 import oslo
 oslo
 module 'oslo' (built-in)
 import oslo.config
 import oslo.messaging
 import oslo.rootwrap
 import oslo.vmware
 
 
 I never understood how these .pth files work.
 
 haypo@devstackdev$ cd /usr/lib/python2.7/site-packages
 
 haypo@devstackdev$ ls oslo*.pth -1
 oslo.config-1.3.0a0.40.gb347519-py2.7-nspkg.pth
 oslo.messaging-1.3.0.8.gc0c8557-py2.7-nspkg.pth
 oslo.rootwrap-1.2.0-py2.7-nspkg.pth
 oslo.vmware-0.3.1.g49097c0-py2.7-nspkg.pth
 
 haypo@devstackdev$ md5sum oslo*.pth 
 002fd4bf040a30d396d4df8e1ed378a8  oslo.config-1.3.0a0.40.gb347519-py2.7-
 nspkg.pth
 002fd4bf040a30d396d4df8e1ed378a8  oslo.messaging-1.3.0.8.gc0c8557-py2.7-
 nspkg.pth
 002fd4bf040a30d396d4df8e1ed378a8  oslo.rootwrap-1.2.0-py2.7-nspkg.pth
 002fd4bf040a30d396d4df8e1ed378a8  oslo.vmware-0.3.1.g49097c0-py2.7-nspkg.pth
 
 haypo@devstackdev$ cat oslo.config-1.3.0a0.40.gb347519-py2.7-nspkg.pth
 import sys,types,os; p = os.path.join(sys._getframe(1).f_locals['sitedir'], 
 *('oslo',)); ie = os.path.exists(os.path.join(p,'__init__.py')); m = not ie 
 and sys.modules.setdefault('oslo',types.ModuleType('oslo')); mp = (m or []) 
 and m.__dict__.setdefault('__path__',[]); (p not in mp) and mp.append(p)
 
 Victor
 
 ___
 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][db] oslo.db repository review request

2014-05-14 Thread Victor Stinner
Le mardi 13 mai 2014, 07:31:34 Doug Hellmann a écrit :
 Since we think we have been able to solve all of the issues we were
 having with namespace packages before, ...

I just tried to start my DevStack and again, I had issues with a builtin 
olso module: import oslo.config doesn't work, whereas olso.config was 
installed (system wide) by pip.

pip list|grep olso told me that oslo.config, oslo.messaging, oslo.rootwrap 
and oslo.vmware are installed.

My workaround is to uninstall all olso modules:
sudo pip uninstall oslo.config oslo.messaging oslo.rootwrap oslo.vmware

./stack.sh reinstalls them and now it works.

--

Current state:

haypo@devstackdev$ pip list|grep oslo
oslo.config (1.3.0a0.40.gb347519)
oslo.messaging (1.3.0.8.gc0c8557)
oslo.rootwrap (1.2.0)
oslo.vmware (0.3.1.g49097c0)

haypo@devstackdev$ python
Python 2.7.5 (default, Feb 19 2014, 13:47:28) 
[GCC 4.8.2 20131212 (Red Hat 4.8.2-7)] on linux2
Type help, copyright, credits or license for more information.
 import oslo
 oslo
module 'oslo' (built-in)
 import oslo.config
 import oslo.messaging
 import oslo.rootwrap
 import oslo.vmware


I never understood how these .pth files work.

haypo@devstackdev$ cd /usr/lib/python2.7/site-packages

haypo@devstackdev$ ls oslo*.pth -1
oslo.config-1.3.0a0.40.gb347519-py2.7-nspkg.pth
oslo.messaging-1.3.0.8.gc0c8557-py2.7-nspkg.pth
oslo.rootwrap-1.2.0-py2.7-nspkg.pth
oslo.vmware-0.3.1.g49097c0-py2.7-nspkg.pth

haypo@devstackdev$ md5sum oslo*.pth 
002fd4bf040a30d396d4df8e1ed378a8  oslo.config-1.3.0a0.40.gb347519-py2.7-
nspkg.pth
002fd4bf040a30d396d4df8e1ed378a8  oslo.messaging-1.3.0.8.gc0c8557-py2.7-
nspkg.pth
002fd4bf040a30d396d4df8e1ed378a8  oslo.rootwrap-1.2.0-py2.7-nspkg.pth
002fd4bf040a30d396d4df8e1ed378a8  oslo.vmware-0.3.1.g49097c0-py2.7-nspkg.pth

haypo@devstackdev$ cat oslo.config-1.3.0a0.40.gb347519-py2.7-nspkg.pth
import sys,types,os; p = os.path.join(sys._getframe(1).f_locals['sitedir'], 
*('oslo',)); ie = os.path.exists(os.path.join(p,'__init__.py')); m = not ie 
and sys.modules.setdefault('oslo',types.ModuleType('oslo')); mp = (m or []) 
and m.__dict__.setdefault('__path__',[]); (p not in mp) and mp.append(p)

Victor

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


Re: [openstack-dev] [oslo][db] oslo.db repository review request

2014-05-13 Thread Doug Hellmann
On Mon, May 12, 2014 at 8:35 AM, Victor Stinner
victor.stin...@enovance.com wrote:
 Hi,

 Le vendredi 18 avril 2014, 17:28:04 Victor Sergeyev a écrit :
 During Icehouse release cycle our team has been working on splitting of
 openstack common db code into a separate library blueprint [1]. At the
 moment the issues, mentioned in this bp and [2] are solved and we are
 moving forward to graduation of oslo.db. You can find the new oslo.db code
 at [3]

 There was a discussion recently about the oslo namespace. Sorry, but I don't
 remember the decision.

 Should the new module be called oslo.db or olsodb?

 (I would prefer oslodb, it avoids issues with the oslo package.)

Since we think we have been able to solve all of the issues we were
having with namespace packages before, and renaming the existing
libraries using the namespace package would introduce complex
backwards compatibility issues (how would we update the code used by
old versions of apps?), we decided to go ahead and keep using the
namespace package.

Doug


 Victor (Stinner aka haypo)

 ___
 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][db] oslo.db repository review request

2014-05-12 Thread Victor Stinner
Hi,

Le vendredi 18 avril 2014, 17:28:04 Victor Sergeyev a écrit :
 During Icehouse release cycle our team has been working on splitting of
 openstack common db code into a separate library blueprint [1]. At the
 moment the issues, mentioned in this bp and [2] are solved and we are
 moving forward to graduation of oslo.db. You can find the new oslo.db code
 at [3]

There was a discussion recently about the oslo namespace. Sorry, but I don't 
remember the decision.

Should the new module be called oslo.db or olsodb?

(I would prefer oslodb, it avoids issues with the oslo package.)

Victor (Stinner aka haypo)

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


Re: [openstack-dev] [oslo][db] oslo.db repository review request

2014-04-25 Thread Matt Riedemann



On 4/18/2014 1:18 PM, Doug Hellmann wrote:

Nice work, Victor!

I left a few comments on the commits that were made after the original
history was exported from the incubator. There were a couple of small
things to address before importing the library, and a couple that can
wait until we have the normal code review system. I'd say just add new
commits to fix the issues, rather than trying to amend the existing
commits.

We haven't really discussed how to communicate when we agree the new
repository is ready to be imported, but it seems reasonable to use the
patch in openstack-infra/config that will be used to do the import:
https://review.openstack.org/#/c/78955/

Doug

On Fri, Apr 18, 2014 at 10:28 AM, Victor Sergeyev
vserge...@mirantis.com wrote:

Hello all,

During Icehouse release cycle our team has been working on splitting of
openstack common db code into a separate library blueprint [1]. At the
moment the issues, mentioned in this bp and [2] are solved and we are moving
forward to graduation of oslo.db. You can find the new oslo.db code at [3]

So, before moving forward, I want to ask Oslo team to review oslo.db
repository [3] and especially the commit, that allows the unit tests to pass
[4].

Thanks,
Victor

[1] https://blueprints.launchpad.net/oslo/+spec/oslo-db-lib
[2] https://wiki.openstack.org/wiki/Oslo/GraduationStatus#oslo.db
[3] https://github.com/malor/oslo.db
[4]
https://github.com/malor/oslo.db/commit/276f7570d7af4a7a62d0e1ffb4edf904cfbf0600

___
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



I'm probably just late to the party, but simple question: why is it in 
the malor group in github rather than the openstack group, like 
oslo.messaging and oslo.rootwrap?  Is that temporary or will it be moved 
at some point?


--

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][db] oslo.db repository review request

2014-04-25 Thread Julien Danjou
On Fri, Apr 25 2014, Matt Riedemann wrote:

 I'm probably just late to the party, but simple question: why is it in the
 malor group in github rather than the openstack group, like oslo.messaging
 and oslo.rootwrap?  Is that temporary or will it be moved at some point?

That's just for creating and validating it, it will be moved on
git.openstack.org, as usual, then.

-- 
Julien Danjou
/* Free Software hacker
   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][db] oslo.db repository review request

2014-04-25 Thread Doug Hellmann
On Fri, Apr 25, 2014 at 8:33 AM, Matt Riedemann
mrie...@linux.vnet.ibm.com wrote:


 On 4/18/2014 1:18 PM, Doug Hellmann wrote:

 Nice work, Victor!

 I left a few comments on the commits that were made after the original
 history was exported from the incubator. There were a couple of small
 things to address before importing the library, and a couple that can
 wait until we have the normal code review system. I'd say just add new
 commits to fix the issues, rather than trying to amend the existing
 commits.

 We haven't really discussed how to communicate when we agree the new
 repository is ready to be imported, but it seems reasonable to use the
 patch in openstack-infra/config that will be used to do the import:
 https://review.openstack.org/#/c/78955/

 Doug

 On Fri, Apr 18, 2014 at 10:28 AM, Victor Sergeyev
 vserge...@mirantis.com wrote:

 Hello all,

 During Icehouse release cycle our team has been working on splitting of
 openstack common db code into a separate library blueprint [1]. At the
 moment the issues, mentioned in this bp and [2] are solved and we are
 moving
 forward to graduation of oslo.db. You can find the new oslo.db code at
 [3]

 So, before moving forward, I want to ask Oslo team to review oslo.db
 repository [3] and especially the commit, that allows the unit tests to
 pass
 [4].

 Thanks,
 Victor

 [1] https://blueprints.launchpad.net/oslo/+spec/oslo-db-lib
 [2] https://wiki.openstack.org/wiki/Oslo/GraduationStatus#oslo.db
 [3] https://github.com/malor/oslo.db
 [4]

 https://github.com/malor/oslo.db/commit/276f7570d7af4a7a62d0e1ffb4edf904cfbf0600

 ___
 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


 I'm probably just late to the party, but simple question: why is it in the
 malor group in github rather than the openstack group, like oslo.messaging
 and oslo.rootwrap?  Is that temporary or will it be moved at some point?

This is the copy of the code being prepared to import into a new
oslo.db repository. It's easier to set up that temporary hosting on
github. The repo has been approved to be imported, and after that
happens it will be hosted on our git server like all of the other oslo
libraries.

Doug


 --

 Thanks,

 Matt Riedemann



 ___
 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][db] oslo.db repository review request

2014-04-18 Thread Doug Hellmann
Nice work, Victor!

I left a few comments on the commits that were made after the original
history was exported from the incubator. There were a couple of small
things to address before importing the library, and a couple that can
wait until we have the normal code review system. I'd say just add new
commits to fix the issues, rather than trying to amend the existing
commits.

We haven't really discussed how to communicate when we agree the new
repository is ready to be imported, but it seems reasonable to use the
patch in openstack-infra/config that will be used to do the import:
https://review.openstack.org/#/c/78955/

Doug

On Fri, Apr 18, 2014 at 10:28 AM, Victor Sergeyev
vserge...@mirantis.com wrote:
 Hello all,

 During Icehouse release cycle our team has been working on splitting of
 openstack common db code into a separate library blueprint [1]. At the
 moment the issues, mentioned in this bp and [2] are solved and we are moving
 forward to graduation of oslo.db. You can find the new oslo.db code at [3]

 So, before moving forward, I want to ask Oslo team to review oslo.db
 repository [3] and especially the commit, that allows the unit tests to pass
 [4].

 Thanks,
 Victor

 [1] https://blueprints.launchpad.net/oslo/+spec/oslo-db-lib
 [2] https://wiki.openstack.org/wiki/Oslo/GraduationStatus#oslo.db
 [3] https://github.com/malor/oslo.db
 [4]
 https://github.com/malor/oslo.db/commit/276f7570d7af4a7a62d0e1ffb4edf904cfbf0600

 ___
 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