I had not realized this until doing the research at the Summit about request_id middleware in the base iaas services, that glance did something quite different than the others (and has always allowed the request_id to be set).
I'd actually like to modify that behavior to setting the new global_request_id variable in oslo.context instead - https://review.openstack.org/#/c/468443/ which gives you 2 ids that can be tracked, one per inbound request, and one that might be set globally. It's a small change (a larger change to use the oslo.middleware would be a bit more complicated, and while good long term, is beyond scope right now), but I wanted to get an idea how this sits with the glance team. Thanks in advance, -Sean -- Sean Dague http://dague.net __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
