On 09:50 Dec 22, Doug Hellmann wrote:
> Excerpts from Kekane, Abhishek's message of 2015-12-18 06:27:59 +:
> > My point here is, should we follow this new approach in all python-clients
> > to maintain the consistency across openstack?
>
> The original design was discussed, reviewed, and if
Excerpts from Kekane, Abhishek's message of 2015-12-18 06:27:59 +:
> Hi Devs,
>
> I have submitted a cross-project specs [1] for returning request-id to the
> caller which was approved. For implementation we have submitted patches in
> python-cinderclient [2] as per design in cross-project
Hi Devs,
I have submitted a cross-project specs [1] for returning request-id to the
caller which was approved. For implementation we have submitted patches in
python-cinderclient [2] as per design in cross-project specs. However we have
found one issue while implementing this design in
-Original Message-
From: Gorka Eguileor [mailto:gegui...@redhat.com]
Sent: 29 July 2015 15:07
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [all] cross project communication: Return
request-id to caller
On Tue, Jul 28, 2015 at 09:48:25AM -0400
On Tue, Jul 28, 2015 at 09:48:25AM -0400, Doug Hellmann wrote:
Excerpts from Gorka Eguileor's message of 2015-07-28 10:37:42 +0200:
On Fri, Jul 24, 2015 at 10:08:45AM -0400, Doug Hellmann wrote:
Excerpts from Kekane, Abhishek's message of 2015-07-24 06:33:00 +:
Hi Devs,
On Fri, Jul 24, 2015 at 10:08:45AM -0400, Doug Hellmann wrote:
Excerpts from Kekane, Abhishek's message of 2015-07-24 06:33:00 +:
Hi Devs,
X-Openstack-Request-Id. We have analysed python-cinderclient,
python-glanceclient, python-novaclient, python-keystoneclient and
Excerpts from Gorka Eguileor's message of 2015-07-28 10:37:42 +0200:
On Fri, Jul 24, 2015 at 10:08:45AM -0400, Doug Hellmann wrote:
Excerpts from Kekane, Abhishek's message of 2015-07-24 06:33:00 +:
Hi Devs,
X-Openstack-Request-Id. We have analysed python-cinderclient,
Hi Devs,
X-Openstack-Request-Id. We have analysed python-cinderclient,
python-glanceclient, python-novaclient, python-keystoneclient and
python-neutronclient to check the return types.
There are 9 ways return values are returned from python clients:
1. List
2. Dict
3. Resource class object
4.
Excerpts from Kekane, Abhishek's message of 2015-07-24 06:33:00 +:
Hi Devs,
X-Openstack-Request-Id. We have analysed python-cinderclient,
python-glanceclient, python-novaclient, python-keystoneclient and
python-neutronclient to check the return types.
There are 9 ways return values
@lists.openstack.org)
Subject: Re: [openstack-dev] [all] cross project communication: Return
request-id to caller
Did you get to talk with anyone in the LogWG (
https://wiki.openstack.org/wiki/LogWorkingGroup )? In wonder what kind of
recommendations, standards we can come up with while
Thanks Regards,
Abhishek Kekane
-Original Message-
From: Nikhil Komawar [mailto:nik.koma...@gmail.com]
Sent: 28 May 2015 12:34
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [all] cross project communication: Return
request-id to caller
Did you get to talk
(mailto:openstack-dev@lists.openstack.org)
Subject: Re: [openstack-dev] [all] cross project communication: Return
request-id to caller
Did you get to talk with anyone in the LogWG (
https://wiki.openstack.org/wiki/LogWorkingGroup )? In wonder what kind of
recommendations, standards we can
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [all] cross project communication: Return
request-id to caller
Did you get to talk with anyone in the LogWG (
https://wiki.openstack.org/wiki/LogWorkingGroup )? In wonder what kind of
recommendations, standards we can come up
.
Abhishek Kekane
From: Joe Gordon [mailto:joe.gord...@gmail.com]
Sent: 28 May 2015 00:31
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [all] cross project communication: Return
request-id to caller
On Wed, May 27, 2015 at 12:06 AM, Kekane, Abhishek
] [all] cross project communication:
Return request-id to caller
On Wed, May 27, 2015 at 12:06 AM, Kekane, Abhishek
abhishek.kek...@nttdata.com mailto:abhishek.kek...@nttdata.com wrote:
Hi Devs,
Each OpenStack service sends a request ID header with HTTP responses.
This request
On Wed, May 27, 2015 at 10:31 AM, Mike Bayer mba...@redhat.com wrote:
On 5/27/15 3:06 AM, Kekane, Abhishek wrote:
Hi Devs,
Each OpenStack service sends a request ID header with HTTP responses. This
request ID can be useful for tracking down problems in the logs. However,
when
On Wed, May 27, 2015 at 12:06 AM, Kekane, Abhishek
abhishek.kek...@nttdata.com wrote:
Hi Devs,
Each OpenStack service sends a request ID header with HTTP responses. This
request ID can be useful for tracking down problems in the logs. However,
when operation crosses service boundaries,
On 5/27/15, 10:15, Doug Hellmann d...@doughellmann.com wrote:
Excerpts from Kekane, Abhishek's message of 2015-05-27 07:06:56 +:
Hi Devs,
Each OpenStack service sends a request ID header with HTTP responses.
This request ID can be useful for tracking down problems in the logs.
However,
Excerpts from Kekane, Abhishek's message of 2015-05-27 07:06:56 +:
Hi Devs,
Each OpenStack service sends a request ID header with HTTP responses. This
request ID can be useful for tracking down problems in the logs. However,
when operation crosses service boundaries, this tracking can
On 5/27/15 3:06 AM, Kekane, Abhishek wrote:
Hi Devs,
Each OpenStack service sends a request ID header with HTTP responses.
This request ID can be useful for tracking down problems in the logs.
However, when operation crosses service boundaries, this tracking can
become difficult, as each
Hi Devs,
Each OpenStack service sends a request ID header with HTTP responses. This
request ID can be useful for tracking down problems in the logs. However, when
operation crosses service boundaries, this tracking can become difficult, as
each service has its own request ID. Request ID is not
21 matches
Mail list logo
