Create a unified request identifier

Registered by Tiago Mello

This ML thread from December has refined what "cross-service request ID" means:

http://lists.openstack.org/pipermail/openstack-dev/2013-December/020774.html

1. There shouldn't be a cross-service request ID, but instead a mapping of the request IDs from the calling service to the answering service.

2. The log message containing the mapping will be in the n-api log.

3. The x-openstack-request-id header will be used across projects; for nova (and cinder), x-compute-request-id will be deprecated in the future.

4. Since nova will be the one logging the mapping, the clients will need to provide the x-openstack-request-id value back with its response.

5. Since this will be rolled-out across services, common components should be shared in oslo.

-----
More details in:
https://blueprints.launchpad.net/nova/+spec/cross-service-request-id

Related blueprint: https://blueprints.launchpad.net/keystone/+spec/keystone-request-tracking

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Tiago Mello
Direction:
Needs approval
Assignee:
Tiago Mello
Definition:
Superseded
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Steve Martinelli

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/cross-service-request-id,n,z

Addressed by: https://review.openstack.org/70823
    Sync request_id middleware for Keystone

(stevemar) 2016-02-02: this has been superseded by oslo.middleware's request id, which is now included in keystone

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.