Description of problem: When glance downloads images, it does not add to the HTTP request the header: Accept-Encoding: gzip, deflate This prevents it from getting compressed content. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I may be missing something here, but seems to me that .gz content can be used for the image content, it's just not deflated automatically on download. But there's nothing to stop the image downloader from unzipping after the fact. This seems logical to me, in terms of glance being agnostic to the image content format.
OK, I now see the point is to allow the image content to be compressed by the backend store as it's served out, as opposed to the compression being applied a priori to the image data before it's uploaded.
Just to make it a bit clearer: The idea here is that glance's stores should add gzip as its accepted encodings in order to be able to choose that format as encoding for data transmission.
The migration to python-requests will fix part of this bug since the default Accept-Encoding value for requests is: 'gzip, deflate, compress' Now, webob's response encode_content has to be call in glance in order to actually encode the response's content.
by editing the -paste.ini and api.conf file appropriately this works as expected; I'm closing the bug in VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2013-1859.html