FYI -------- Original Message -------- Subject: Thebes Code Update Date: Tue, 10 Mar 2009 11:02:00 -0400 From: Tim Bornholtz <tim@bornholtz.com> Reply-To: thebes-l@georgetown.edu To: thebes-l@georgetown.edu I've been working on the Thebes code that receives a request as JSDL and submits the job via DRMAA. I think that I've got all of the DRMAA API working except for submitting bulk jobs (massively serial jobs, for example multiple iterations of the same job with slightly modified input files. Like, 10000 instances of the same job, each with a different input file). I'm not quite sure what the best way to deal with the bulk jobs yet. Any input would be appreciated. I've been avoiding a lot of the security work but we're getting to a point where that's all that is left. From the SOAP service I can get at the headers and read the attributes but I'm not really sure what to do with them yet. So far the code is based on Apache Axis and Apache Rampart for the security. Rampart can use SAML assertions but they are SAML 1.0. There are some really nice and important things in SAML 2.0. Also, the SAML handling is rudimentary at best in Rampart. Shibboleth has a very mature attribute acceptance policy engine that would really provide a lot of benefits for Thebes. But we're back to the old question of how to properly integrate Thebes with Shibboleth. I'd also like to extend the Genesis II JSDL Tool to be able to directly submit a Thebes job. I've looked at the code of JSDL Tool but that's about it for now. As always, feedback / thoughts / criticism is welcome and appreciated. Thanks, Tim Bornholtz