[openstack-dev] [ python-novaclient][ python-glanceclient][ python-cinderclient][ python-neutronclient] Remove x-openstack-request-id logging code as it is logged twice

Kekane, Abhishek Abhishek.Kekane at nttdata.com
Sat Jan 21 11:30:57 UTC 2017


Hi Steve,

Thank you for the update. I have already submitted patches for python-novaclient and python-novaclient for reviews and ready with python-cinderclient and python-novaclient patches. I will submit them ASAP when requirements.txt is synced with updated version of keystoneauth1.

Thank you,

Abhishek
________________________________
From: Steve Martinelli <s.martinelli at gmail.com>
Sent: Saturday, January 21, 2017 10:07:04 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [ python-novaclient][ python-glanceclient][ python-cinderclient][ python-neutronclient] Remove x-openstack-request-id logging code as it is logged twice



On Fri, Jan 20, 2017 at 10:53 PM, Kekane, Abhishek <Abhishek.Kekane at nttdata.com<mailto:Abhishek.Kekane at nttdata.com>> wrote:
Hi Dims,

Thank you for reply. I will propose a patch soon. Just for curiosity, keystoneauth1 >= 2.17.0 will not install 2.18.0?

It will, but if we make 2.18.0 the minimum then it will for sure install only that level.

> In the latest keystoneauth1 version 2.18.0, x-openstack-request-id is logged
> for every HTTP response. This keystoneauth1 version will be used for ocata.
>
> The same request id is also logged in 'request' method of SessionClient
> class for python-novaclient, python-glanceclient, python-cinderclient and
> python-neutronclient. Once requirements.txt is synced with
> global-requirements and it uses keystoneauth1 version 2.18.0 and above,
> x-openstack-request-id will be logged twice for these clients.

So I approved this change (sorry it took so long to review and merge), but I didn't realize it was going to impact python-{nova | glance | cinder | neutron}client. I think it's slightly unrealistic to ask four teams to remove the logging in the last week we release clients (I'm assuming we want to remove the functionality and not log things twice).

 - Would folks prefer I revert the keystoneauth change and re-release without it, and we can bring it back in Pike?
- Do teams have the bandwidth to remove the request id logging in the next few days?

Sorry for the confusion this caused.

______________________________________________________________________
Disclaimer: This email and any attachments are sent in strictest confidence
for the sole use of the addressee and may contain legally privileged,
confidential, and proprietary data. If you are not the intended recipient,
please advise the sender by replying promptly to this email and then delete
and destroy this email and any attachments without any further use, copying
or forwarding.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170121/91bc7d6d/attachment.html>


More information about the OpenStack-dev mailing list