Submitting glideins using EC2 is hitting 8K limit for URI
Its not clear if we can do something in glideinwms or should we check with condor. Condor does EC2 submit using GET. HTTP has a limit or 8K. Until now using a grid proxy
This came up while testing Glideinwms submitting to Fermicloud. Neha created a proxy that by default was a 1024 bit proxy instead of 512 proxy. URI generated by condor to launch an ec2 instance was 8K+. Since we add proxy to the ec2 metadata, this is partially in our court too.
#3 Updated by Anthony Tiradani over 6 years ago
The Condor developers changed the HTTP method from GET to POST in HTCondor 8.1.5. POST has no explicit size limit. HTCondor 8.1.5 has been tested against OpenStack and is currently being used by CMS for the AI and HLT clouds for production work.
In the case of OpenStack, part of the scaling strategy is to front the EC2 protocol with Apache. Apache has a hard coded limit of 8K for GET. They do provide a knob to adjust that value, but for any value > 8K, you have to recompile Apache. Apache imposes no limit on POST.
What is being used to handle EC2 requests in OpenNebula?
Jetty has a 4K limit
Python's "built in" server doesn't limit GET (OK, there is no built in server, but creating a very simple HTTP server in python is trivial)
#4 Updated by Anthony Tiradani over 6 years ago
Further explanation can be found with some references here: http://stackoverflow.com/questions/2659952/maximum-length-of-http-get-request