Ok, thanks Tuan. Renat Akhmerov @Nokia
On 29 May 2017, 17:38 +0700, lương hữu tuấn <tuantulu...@gmail.com>, wrote: > Hi Renat, > > Kong is going to move on with this patch and then i will continue with the > main problem of trust token in Mistral. > > Br, > > Tuan/Nokia > > > On Mon, May 29, 2017 at 9:20 AM, Renat Akhmerov <renat.akhme...@gmail.com> > > wrote: > > > Tuan, > > > > > > It’s ok, not always people have cycles to finish something upstream. No > > > need to explain that. All I’m worried about is getting this thing done. > > > So if you don’t have capacity please help transfer this work to someone > > > else. > > > > > > Thanks > > > > > > Renat > > > > > > On 29 May 2017, 13:36 +0700, lương hữu tuấn <tuantulu...@gmail.com>, > > > wrote: > > > > Hi Doug and Renat, > > > > > > > > I totally agree with what Doug mentioned in the previous mail. In fact, > > > > my patch is only the used for the purpose of "implementing trust > > > > token", not for full refactoring mistral context. Since i do not have > > > > my capacity for contributing to Mistral, my commit now is for the need > > > > of Nokia in using token when it is expired. > > > > > > > > From very beginning, i would like to refactor mistral context to fully > > > > use oslo-context. But if i wanted to refactor the whole mistral > > > > context, i would spend my whole capacity for upstream work which is not > > > > available for me. By the way, thanks Doug to review it, i know all the > > > > issues in your comments but as i said, it was hard for me for upstream > > > > work. But i will re-arrange my schedule to finish as Doug commented in > > > > the patch as well as switching to oslo-context > > > > > > > > @Renat: I will try to refactor the whole mistral context therefore > > > > there will not be any roadblocks. > > > > > > > > Br, > > > > > > > > Tuan > > > > > > > > > On Sat, May 27, 2017 at 2:08 AM, Vitaliy Nogin <vno...@mirantis.com> > > > > > wrote: > > > > > > Hi Doug, > > > > > > > > > > > > Anyway, thank for the notification. We are really appreciated. > > > > > > > > > > > > Regards, > > > > > > Vitaliy > > > > > > > > > > > > > 26 мая 2017 г., в 20:54, Doug Hellmann <d...@doughellmann.com> > > > > > > > написал(а): > > > > > > > > > > > > > > Excerpts from Saad Zaher's message of 2017-05-26 12:03:24 +0100: > > > > > > >> Hi Doug, > > > > > > >> > > > > > > >> Thanks for your review. Actually freezer has a separate repo for > > > > > > >> the api, > > > > > > >> it can be found here [1]. Freezer is using oslo.context since > > > > > > >> newton. If > > > > > > >> you have the time you can take a look at it and let us know if > > > > > > >> you have any > > > > > > >> comments. > > > > > > > > > > > > > > Ah, that explains why I couldn't find it in the freezer repo. :-) > > > > > > > > > > > > > > Doug > > > > > > > > > > > > > >> > > > > > > >> Thanks for your help > > > > > > >> > > > > > > >> [1] https://github.com/openstack/freezer-api > > > > > > >> > > > > > > >> Best Regards, > > > > > > >> Saad! > > > > > > >> > > > > > > >> On Fri, May 26, 2017 at 5:45 AM, Renat Akhmerov > > > > > > >> <renat.akhme...@gmail.com> > > > > > > >> wrote: > > > > > > >> > > > > > > >>> Thanks Doug. We’ll look into this. > > > > > > >>> > > > > > > >>> @Tuan, is there any roadblocks with the patch you’re working > > > > > > >>> on? [1] > > > > > > >>> > > > > > > >>> [1] https://review.openstack.org/#/c/455407/ > > > > > > >>> > > > > > > >>> > > > > > > >>> Renat > > > > > > >>> > > > > > > >>> On 26 May 2017, 01:54 +0700, Doug Hellmann > > > > > > >>> <d...@doughellmann.com>, wrote: > > > > > > >>> > > > > > > >>> The new work to add the exception information and request ID > > > > > > >>> tracing > > > > > > >>> depends on using both oslo.context and oslo.log to have all of > > > > > > >>> the > > > > > > >>> relevant pieces of information available as log messages are > > > > > > >>> emitted. > > > > > > >>> > > > > > > >>> In the course of reviewing the "done" status for those > > > > > > >>> initiatives, > > > > > > >>> I noticed that although mistral and freezer are using oslo.log, > > > > > > >>> neither uses oslo.context. That means neither project will get > > > > > > >>> the > > > > > > >>> extra debugging information, and neither project will see the > > > > > > >>> global > > > > > > >>> request ID in logs. > > > > > > >>> > > > > > > >>> I started looking at updating mistral's context to use > > > > > > >>> oslo.context > > > > > > >>> as a base class, but ran into some issues because of some > > > > > > >>> extensions > > > > > > >>> made to the existing class. I wasn't able to find where freezer > > > > > > >>> is > > > > > > >>> doing anything at all with an API request context. > > > > > > >>> > > > > > > >>> I'm available to help, if someone else wants to pick up the > > > > > > >>> work. > > > > > > >>> > > > > > > >>> Doug > > > > > > >>> > > > > > > >>> __________________________________________________________________________ > > > > > > >>> OpenStack Development Mailing List (not for usage questions) > > > > > > >>> Unsubscribe: > > > > > > >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > > > > > >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > >>> > > > > > > >>> > > > > > > >>> __________________________________________________________________________ > > > > > > >>> OpenStack Development Mailing List (not for usage questions) > > > > > > >>> Unsubscribe: > > > > > > >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > > > > > >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > >>> > > > > > > >>> > > > > > > >> > > > > > > > > > > > > > > __________________________________________________________________________ > > > > > > > OpenStack Development Mailing List (not for usage questions) > > > > > > > Unsubscribe: > > > > > > > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > > > > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > > > > > > > > > > > > > __________________________________________________________________________ > > > > > > OpenStack Development Mailing List (not for usage questions) > > > > > > Unsubscribe: > > > > > > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > > > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > > > __________________________________________________________________________ > > > > OpenStack Development Mailing List (not for usage questions) > > > > Unsubscribe: > > > > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > __________________________________________________________________________ > > > OpenStack Development Mailing List (not for usage questions) > > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
