GitHub PushEvent at 2014-05-07 01:10:34
Repository: openstack
Actor: openstack-gerrit
Payload: {"shas":[["8be31aa9d4e90f54d2626244c1a301e637b5bd3c","d95b56ce41a2e1ac4cecdd398defd7414407cc08@review.openstack.org","Updated openstack/openstack\nProject: openstack/nova  edac193a8971b70ce1739a716275c03d09c82379\n\nAdd x-openstack-request-id to nova v3 responses\n\nx-openstack-request-id is the common header name for request ID going\nforward. Nova, cinder, and neutron return this header. Using the\nrequest_id middleware is a convenient way to ensure this header is in\nthe response. We will also be using the middleware to generate the\nrequest ID.\n\nThe ID will be generated by the middleware and is inserted into the\nrequest environment. The current code generates the request ID in the\nconstructor of RequestContext; with this change, the ID is generated\nbeforehand and passed in to the RequestContext constructor. Not much\ndifferent here: a request ID is generated and is available for use in\nthe handling of the request.\n\nOn the response end, the middleware is again used, this time to\nattach the x-openstack-request-id header, using the value of the\ngenerated request ID.\n\nFor v3, we will be using the request_id middleware provided in oslo.\nFor v2, nova-specific middleware (compute_request_id.py) is used.\nTherefore, v3 responses will have the header x-openstack-request-id,\nand v2 responses will have the header x-compute-request-id (no\nchange). It is necessary to move the existing code out into\nmiddleware, so that the old header is not attached to v3 responses.\n\nUpgradeImpact: api-paste.ini is modified\n\nDocImpact: v3 responses of the API will only include x-openstack-request-id\n\nImplements: blueprint cross-service-request-id\nChange-Id: I5e370fd3de5ee2f8a8d13553015d88910ff5ea87","Jenkins",true]],"size":1,"ref":"refs/heads/master","head":"8be31aa9d4e90f54d2626244c1a301e637b5bd3c"}