GZipped DBS Request Body

[klannon]

Impact of the new feature
WMAgent, and another other WM services that access DBS

Is your feature request related to a problem? Please describe.
The data sent over the network is higher than it needs. Gzipping the DBS request body payload can help significantly.

Describe the solution you'd like
After dmwm/DBS#648 is merged and deployed for DBS, modify any DBS API calls to gzip request body payloads.

Describe alternatives you've considered
Not doing it is the only alternative, but this leaves a significant reduction in network traffic volume on the table. This shouldn't be much work, so let's not choose the alternative.

Additional context
I think this would be a good candidate for a Q3 development item, so I've put it on that project, but feel free to adjust once we get to the Q3 planning.

[amaltaro]

Further information can be seen in this GH issue as well: #10451

[vkuznet]

@amaltaro I suggest that you extend the scope of this issue to provide gzip support in all WMCore http services. It is not only DBS issue since all WMCore services can benefit from such support, e.g. ReqMgr, MicroServices, etc. In #10451 I provided details of both CherryPy server and client which is required for that.

[vkuznet]

This issue will be resolved once we will add two pieces:

• switch DBSWriter to DBS Go implementation which already supports gzip encoding
• and, merge Define gzip encoding by default in the headers; properly decompress it #11041 which provides gzip encoding via Content-Encoding: gzip HTTP header
  Then, we only need to enforce WMAgents to use Content-Encoding: gzip as default HTTP header. I don't think we need to do anything special on this issue.

[amaltaro]

Moving it from Q2 to Q1 just so it gets properly accounted for.