Hi Dejan and Jun, We hope to have next CDDLM and OGSA joint call on July 10 (3-5pm PT) and we really need your feedback and attendance. You can find the latest materials from gridForge https://forge.gridforum.org/sf/go/doc13640?nav=1 https://forge.gridforum.org/sf/go/doc13637?nav=1 https://forge.gridforum.org/sf/go/doc13638?nav=1 https://forge.gridforum.org/sf/go/doc13639?nav=1 Dejan and Jun: Can check the above CDL documents before the call?
* CDL documents review
Hiro produced and sent out new versions of the CDL documents. A few remaining issues were discussed.
- Location of application binary (to deploy from) and format. Agreed that in general the client would not know these (but may know under certain circumstances). So in general - deployer (or perhaps developer) produces (original) CDL - Client produces jsdl - And a repository or some other internal component keeps track of binaries and related information - Permission and Owner of files. - The binary does not have to be owned by the user running the job; user just needs to be able to execute. - Simplest case assume that the correct permissions/ownership are set in the archive - If the desire is to show it as an example in the CDL something like "root.bin 755" or perhaps "blast.blast 755" or 555 is appropriate. - These are also affected by system policy. - pre-script - Hiro has talked with Chris Smith and they have removed the pre-script. - Assume instead that the db is pre-formatted (perhaps by an earlier user job) and that it can be made available by requesting a specific filesystem be made available on the host. - Hiro added 'database' filesystem.
ACTION: Hiro to ask Jun and Dejan to check the CDL documents ACTION: Hiro to also make any relevant updates to the Scenarios text ACTION: Jun/Hiro to also prepare the post-deployment BLAST CDL document
Thanks, -- Hiro Kishimoto