Create a unified request identifier
This ML thread from December has refined what "cross-service request ID" means:
http://
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-
4. Since nova will be the one logging the mapping, the clients will need to provide the x-openstack-
5. Since this will be rolled-out across services, common components should be shared in oslo.
-----
More details in:
https:/
Related blueprint: https:/
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
- Started by
- Completed by
- Steve Martinelli
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
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