[openstack-dev] [nova][heat][[keystone] RFC: introducing "request identification"

Takahiro Shida shida.takahiro at gmail.com
Wed Nov 27 05:45:28 UTC 2013

Hi all,

I'm also interested in this issue.

> Create a unified request identifier
> https://blueprints.launchpad.net/nova/+spec/cross-service-request-id

I checked this BP and the following review.

There are many comments. Finally, this review looks rejected by "user
specified correlation-id" is useless and insecure.

>> 3. Enable keystone to generate "request identification" (we can call it
'request-token', for example).
> -2

So, this idea will be helpful to solve the "cross-service-request-id"
Because the correlation-id specified by keystone.

How about nova guys and keystone guys ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131127/153433c9/attachment.html>

More information about the OpenStack-dev mailing list