Use oslo middleware request id

Registered by Neha Alhat on 2019-01-10

Create a request identifier associated with an API request that crosses OpenStack service boundaries. This will enable more effective debugging of requests that span multiple services. Use oslo middleware which will generate unique `request_id` for each Restful API call. Adding this middleware will mean that Blazar now returns the additional X-OpenStack-Request-ID header.
Along with this operator can see both 'request_id' and 'global_request_id' in logs for better tracing.

Proposal:
- Upon receiving a request, use oslo middleware to generate a UUID to identify the request.
- The oslo middleware used to generate the request ID will attach the x-openstack-request-id header to the response.

Blueprint information

Status:
Not started
Approver:
Pierre Riteau
Priority:
Undefined
Drafter:
Neha Alhat
Direction:
Needs approval
Assignee:
Neha Alhat
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

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

Addressed by: https://review.openstack.org/637140
    Add request_id middleware support

Gerrit topic: https://review.opendev.org/#/q/topic:bug/1740091

Addressed by: https://review.opendev.org/637140
    Add request_id middleware support

Gerrit topic: https://review.opendev.org/#/q/topic:bp/oslo-middleware-request-id

Addressed by: https://review.opendev.org/666202
    Create placement client for each request

Addressed by: https://review.opendev.org/670995
    Show global req id in devstack environment

Gerrit topic: https://review.opendev.org/#/q/topic:global_request_id

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.