OGSA-WG EMS Architecture Steven Newhouse & Andrew Grimshaw GGF17 in Tokyo Wed, May 10 5:45pm @ G405

GGF Intellectual Property Policy All statements related to the activities of the GGF and addressed to the GGF are subject to all provisions of Appendix B of GFD-C.1, which grants to the GGF and its participants certain licenses and rights in such statements. Such statements include verbal statements in GGF meetings, as well as written and electronic communications made at any time or place, which are addressed to any GGF working group or portion thereof, Where the GFSG knows of rights, or claimed rights, the GGF secretariat shall attempt to obtain from the claimant of such rights, a written assurance that upon approval by the GFSG of the relevant GGF document(s), any party will be able to obtain the right to implement, use and distribute the technology or works when implementing, using or distributing technology based upon the specific specification(s) under openly specified, reasonable, non-discriminatory terms. The working group or research group proposing the use of the technology with respect to which the proprietary rights are claimed may assist the GGF secretariat in this effort. The results of this procedure shall not affect advancement of document, except that the GFSG may defer approval where a delay may facilitate the obtaining of such assurances. The results will, however, be recorded by the GGF Secretariat, and made available. The GFSG may also direct that a summary of the results be included in any GFD published containing the specification.

EMS architecture scenarios (Steven) ESI & BES discussion (Andrew) Session Agenda EMS architecture scenarios (Steven) ESI & BES discussion (Andrew) Basic POSIX component (Hiro)

Deployment Infrastructure Host1 Host2 Host3 Portal Component archive (ACS?) Basic Posix component Basic Posix template Client BLAST binary Posix binary archive (ACS?)

BLAST CDL document Host1 Host2 Host3 Portal Component archive (ACS?) Basic Posix component CodeBase Basic Posix template Client Refer to <> BLAST binary executable Posix binary archive (ACS?) BLAST CDL document

Deploy Component Host1 Host2 Host3 Portal Component archive (ACS?) <> CodeBase Basic Posix component Refer to Basic Posix template Client executable BLAST binary Posix binary archive (ACS?) BLAST CDL document

Deploy BLAST binary Host1 Host3 Portal Component archive (ACS?) <> Portal Component archive (ACS?) <> executable Basic Posix component Basic Posix template Client executable BLAST binary Posix binary archive (ACS?) BLAST CDL document

Identified “gap” between family of CDDLM specs and EMS services Basic POSIX component Identified “gap” between family of CDDLM specs and EMS services Provide services Application binary installation File system mount Database setup (in case of BLAST) Provide output (will be incorporated in JSDL document) Application path Environment variables

CDL document includes Application binary installation If this application depends on specific libraries or other software, how to deploy them should be described by CDL File system mount <jsdl-posix:Executable>/usr/local/bin/blastall</jsdl-posix:Executable> Executable should be added from CDL output <jsdl:FileSystem name="TMP"> <jsdl:FileSystemType>temporary</jsdl:FileSystemType> <jsdl:Description> … </jsdl:Description> <jsdl:DiskSpace> <jsdl:LowerBoundedRange>10737418240.0</jsdl:LowerBoundedRange> </jsdl:DiskSpace> </jsdl:FileSystem> <jsdl:FileSystem name="HOME"> <jsdl:FileSystemType>normal</jsdl:FileSystemType> <jsdl:Description>Chris's home directory</jsdl:Description> <jsdl:MountPoint>/home/csmith</jsdl:MountPoint> Dejan to include filesystem mount in the CDL example

CDL document includes Database setup BLAST needs NDA sequence database(s) Popular databases are nr, nt, and est Each database is large file in specific format and should be deployed before running job <jsdl:Resources> …. <blast:database> <jsdl:FileName>db/ncbiblast/est</jsdl:FileName> <jsdl:FilesystemName>DB</jsdl:FilesystemName> </blast:database> </jsdl:Resources> Note by Chris Smith: There might be some more information needed depending on whether the database is already formatted, or if it's in FASTA format still. From the point of view of a provisioning engine, you might need to specify a command to run to format the FASTA file, or it might be a set of files that is the result of the formatting that need to be staged.

CDL document may include Set environment variables <jsdl-posix:Environment name="PATH">/usr/bin:/usr/local/bin:/usr/local/bio/bin </jsdl-posix:Environment> <jsdl-posix:Environment name="TMPDIR" filesystemName="TMP"/> Alternative: BES container sets them when job is initiated Env. Variables, path and tmpdir, are output of deployer JSDL document is instantiated by the output of deployer using CDL document

Companion template to Basic POSIX component Basic POSIX template Companion template to Basic POSIX component

Jointly develop BPC and BPT spec More example than BLAST Next steps Jointly develop BPC and BPT spec OGSA EMS & CDDLM-WG More example than BLAST OGSA EMS & JSDL-WG Put Job Manager in this deployment picture Put ACS in this picture Advanced Common Component