openstack/blazar
Code Issues Proposed changes
8663d58d1f
blazar/api-ref/source/v1
History
asmita singh 563e4a8da2 Send global_request_id for tracing calls 
This patch adds global_request_id to the constructor for nova client,
keystone client, neutron client and placement client which will pass the
global_request_id to these respective services on all API calls.
Supporting global_request_id makes debugging easier when requests reach
many different OpenStack services. The blazar global_request_id will be
sent to these services in the request header like below and it will be
available with context.global_request_id:

  -H "X-OpenStack-Request-ID: req-1a9b7b24-02ed-4400-bcc3-cc1bcbb59147"

Sample log output of neutron service for ``POST v1/floatingips`` API
which logs global request ID `req-e19f8f4f-40e7-441e-b776-7b43ed15c7dd`
is shown at: http://paste.openstack.org/show/753807

Oslo spec I65de8261746b25d45e105394f4eeb95b9cb3bd42
Change-Id: I5bb3631c4fb178293ee8eefbe1aa8b819a196a9f
2019-09-06 11:15:18 +02:00
..
floatingips.inc Expose floatingip APIs and virtual:floatingip resources 2019-03-19 09:59:53 +00:00
global-request-id.inc Send global_request_id for tracing calls 2019-09-06 11:15:18 +02:00
hosts.inc Support reservation_id parameter in List and Get Allocation API 2019-01-08 12:32:30 +00:00
index.rst Send global_request_id for tracing calls 2019-09-06 11:15:18 +02:00
leases.inc Fix POST and PUT status codes and update API Reference 2018-07-18 00:43:26 +00:00
parameters.yaml Send global_request_id for tracing calls 2019-09-06 11:15:18 +02:00
request-ids.inc Add request_id middleware support 2019-09-05 14:39:00 +00:00