[openstack-dev] [python-keystoneclient] Return request-id to caller

Hi Keystone devs, Blueprint [1] related to request-ids is approved for Mitaka and its implementation [2] is up for review for quite a long time. And, I have submitted a blueprint about logging [3]. I would like to include these patch in Ocata. Could you review it? [1]

Re: [openstack-dev] [python-keystoneclient] Return request-id to caller

Hi, keystone devs, Thank you for your many comments about my patch [1]. I modified this patch in reference to your comments. I want to get many opinions about this new Patch Set. Could you review it? [1]: https://review.openstack.org/#/c/261188/ Thank you, On Tue, 31 May 2016 20:46:36 +0900

Re: [openstack-dev] [python-keystoneclient] Return request-id to caller

Hi, keystone devs, Thank you for your many opinions about request id mapping. I fixed this patch [1] by the way that Brant and Cao gave me suggestions [2]. Could you review it? [1] https://review.openstack.org/#/c/261188/ [2] http://paste.openstack.org/show/495040/ Thank you, On Wed, 20 Apr

Re: [openstack-dev] [python-keystoneclient] Return request-id to caller

On Wed, Apr 13, 2016 at 6:07 AM, David Stanek wrote: > On Wed, Apr 13, 2016 at 3:26 AM koshiya maho > wrote: > >> >> My request to all keystone cores to give their suggestions about the same. >> >> > I'll test this a little and see if I can see

Re: [openstack-dev] [python-keystoneclient] Return request-id to caller

On Wed, Apr 20, 2016 at 6:31 AM, Duncan Thomas wrote: > On 20 April 2016 at 08:08, koshiya maho > wrote: > > >> This design was discussed, reviewed and approved in cross-projects [1] and >> already implemented in nova, cinder and neutron. >>

Re: [openstack-dev] [python-keystoneclient] Return request-id to caller

On 20 April 2016 at 08:08, koshiya maho wrote: > This design was discussed, reviewed and approved in cross-projects [1] and > already implemented in nova, cinder and neutron. > At this point if we change the implementation then it will not be > consistent across core

Re: [openstack-dev] [python-keystoneclient] Return request-id to caller

Hi Brant, David, Thank you for your opinions. On Wed, 13 Apr 2016 13:07:55 + David Stanek wrote: > On Wed, Apr 13, 2016 at 3:26 AM koshiya maho > wrote: > > > > > My request to all keystone cores to give their suggestions about the same.

Re: [openstack-dev] [python-keystoneclient] Return request-id to caller

On Wed, Apr 13, 2016 at 3:26 AM koshiya maho wrote: > > My request to all keystone cores to give their suggestions about the same. > > I'll test this a little and see if I can see how it breaks. Overall I'm not really a fan of this design. It's just a hack to add

[openstack-dev] [python-keystoneclient] Return request-id to caller

Hi All, I have submitted patches [1] for returning request-id to the caller on which Brant has raised his concerns [2]; Brant’s concern: We've tried a couple of times to have the client return metadata for the lists returned and we wound up reverting the change both times because it broke

[openstack-dev] [python-keystoneclient] Return request-id to caller

Hi Keystone devs, Blueprint [1] related to request-ids is approved for Mitaka and its implementation [2] is up for review for quite a long time. I would like to apply for a goal for this blueprint so that it can be included in Newton. [1]

[openstack-dev] [python-keystoneclient] return-request-id-to-caller

Hi, I want to add support for returning 'x-openstack-request-id' in python-keystoneclient as per the design proposed in cross-project specs. Cross-project spec has been already approved. : https://specs.openstack.org/openstack/openstack-specs/specs/return-request-id.html So, I'd like you to

Re: [openstack-dev] [python-keystoneclient] return-request-id-to-caller

On Tue, Dec 22, 2015 at 2:02 AM, koshiya maho wrote: > Hi, > > I want to add support for returning 'x-openstack-request-id' in > python-keystoneclient as per the design proposed in cross-project specs. > > Cross-project spec has been already approved. : > >