[openstack-dev] request-id in API response

Sean Dague sean at dague.net
Fri Nov 29 16:00:36 UTC 2013

On 11/29/2013 10:33 AM, Jay Pipes wrote:
> On 11/28/2013 07:45 AM, Akihiro Motoki wrote:
>> Hi,
>> I am working on adding request-id to API response in Neutron.
>> After I checked what header is used in other projects
>> header name varies project by project.
>> It seems there is no consensus what header is recommended
>> and it is better to have some consensus.
>>    nova:     x-compute-request-id
>>    cinder:   x-compute-request-id
>>    glance:   x-openstack-request-id
>>    neutron:  x-network-request-id  (under review)
>> request-id is assigned and used inside of each project now,
>> so x-<service>-request-id looks good. On the other hand,
>> if we have a plan to enhance request-id across projects,
>> x-openstack-request-id looks better.
> My vote is for:
> x-openstack-request-id
> With an implementation of "create a request UUID if none exists yet" in
> some standardized WSGI middleware...

Agreed. I don't think I see any value in having these have different
service names, having just x-openstack-request-id across all the
services seems a far better idea, and come back through and fix nova and
cinder to be that as well.


Sean Dague

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 482 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131129/351f0dd9/attachment.pgp>

More information about the OpenStack-dev mailing list