[mailto:joe.gord...@gmail.com]
*Sent:* 05 February 2015 22:50
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [python-cinderclient] Return request ID to
caller
On Wed, Feb 4, 2015 at 11:23 PM, Malawade, Abhijeet
abhijeet.malaw...@nttdata.com
[mailto:joe.gord...@gmail.com]
Sent: 05 February 2015 22:50
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [python-cinderclient] Return request ID to caller
On Wed, Feb 4, 2015 at 11:23 PM, Malawade, Abhijeet
abhijeet.malaw
On Wed, Feb 4, 2015 at 11:23 PM, Malawade, Abhijeet
abhijeet.malaw...@nttdata.com wrote:
Hi,
I have submitted patch for cinder-client [1] to 'Return tuple containing
header and body from client' instead of just response.
Also cinder spec for the same is under review [2].
This change
Hi,
I have submitted patch for cinder-client [1] to 'Return tuple containing header
and body from client' instead of just response.
Also cinder spec for the same is under review [2].
This change will break OpenStack services which are using cinder-client. To do
not break services which are
On 05:54 Fri 12 Dec , Malawade, Abhijeet wrote:
HI,
I want your thoughts on blueprint 'Log Request ID Mappings' for cross
projects.
BP: https://blueprints.launchpad.net/nova/+spec/log-request-id-mappings
It will enable operators to get request id's mappings easily and will be
useful
- Original Message -
From: Abhijeet Malawade abhijeet.malaw...@nttdata.com
To: openstack-dev@lists.openstack.org
Sent: Friday, 12 December, 2014 3:54:04 PM
Subject: [openstack-dev] [python-cinderclient] Return request ID to caller
HI,
I want your thoughts on blueprint
HI,
I want your thoughts on blueprint 'Log Request ID Mappings' for cross projects.
BP: https://blueprints.launchpad.net/nova/+spec/log-request-id-mappings
It will enable operators to get request id's mappings easily and will be useful
in analysing logs effectively.
For logging 'Request ID
