[openstack-dev] request-id in API response

Jay Pipes jaypipes at gmail.com
Fri Nov 29 15:33:04 UTC 2013


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...

Best,
-jay



More information about the OpenStack-dev mailing list