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

Doug Hellmann doug.hellmann at dreamhost.com
Fri May 30 15:30:36 UTC 2014


On Fri, May 30, 2014 at 11:06 AM, Sergey Lukjanov
<slukjanov at 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
> <rpodolyaka at 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
>> <mriedem at 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
>>>> <mriedem at 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
>>>>>> <vsergeyev at 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 at lists.openstack.org
>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> OpenStack-dev mailing list
>>>>>> OpenStack-dev at 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 at lists.openstack.org
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>>
>>>> _______________________________________________
>>>> OpenStack-dev mailing list
>>>> OpenStack-dev at 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 at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at 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 at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



More information about the OpenStack-dev mailing list