CONDOR ADAPTOR ============== Overview -------- The Condor adaptor for SAGA provides the ability for Condor users to access its services through the simple programmatic interface of SAGA. Currently, the adaptor works in conjunction with the Condor command line tools to communicate with the Condor scheduler and start jobs on the default universe. Alternative implementations using SOAP and the GAHP protocol are planned, but not implemented. Status ------ Running interactive jobs is currently not supported. Suspend/resume also not supported. Setup ----- The Condor adaptor requires local access to the Condor binaries. Currently condor_submit, condor_rm and condor_q may be used as well. condor_status is useful in testing to check the status of submitted jobs. The path to the binaries must be supplied in the adaptor configuration file. Assuming Condor is locally installed and working, all implemented functionality should work. The adaptor can be tested even without a local Condor installation, by providing dummy scripts that forward the commands to an appropriate host, e.g., by ssh. A possible (if minimal) such script is: #!/bin/sh ssh user@host "/bin/sh -lc '$0' $@" With this approach all file staging will happen on the remote (ssh) host, though. Security issues and mitigation strategy --------------------------------------- When using the Condor command-line tools, we implicitly rely on the Condor setup and on the security context of the user to provide appropriate security. Furthermore, binaries are searched for and invoked only from user supplied paths in the configuration option "saga.adaptors..cli.bin_path". (TODO) Environment variables provided to Condor binaries should be minimized and sanitized. Configuration options will be added to allow the user to specify optional command-line arguments and environment variables to be used.