1 / 10

Activity Schema

Activity Schema. What we’ve discussed already A. Stephen M C Gough Imperial College London. Job. Job. Job. JSDL. JSDL. JSDL. JLM. JLM. JLM. …. …. …. RRL. RRL. RRL. JPL. JPL. JPL. WS-A. WS-A. WS-A. SDL. SDL. SDL. …. …. ….

gudrun
Download Presentation

Activity Schema

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Activity Schema What we’ve discussed already A. Stephen MCGough Imperial College London

  2. Job Job Job JSDL JSDL JSDL JLM JLM JLM … … … RRL RRL RRL JPL JPL JPL WS-A WS-A WS-A SDL SDL SDL … … … JSDL: Conceptual relation with other standards Workflow Job JSDL JLM … RRL JPL SDL WS-A … RRL - Resource Requirements Language SDL – Scheduling Description Language WS-A – WS-Agreement JLM – Job Lifetime Management JPL – Job Policy Language

  3. JSDL Document Life Cycle • A JSDL document may be • Abstract • Only the minimum information necessary • For example, application name and input files • Runnable at sites that understand this level of description • Refined • More detail provided • Target site, number of CPUs, which data source • May be refined several times • Tied to a specific site/system • Incarnated (Unicore speak); or • Grounded (Globus speak) • This model is supported/allowed but not required by JSDL BES (GridSAM)

  4. GridSAMJob Submission and Monitoring Web Service

  5. Integration with OMII Distribution

  6. Deployment Scenario: Globus 2.4.3

  7. JSDL Extension Example • <?xml version="1.0" encoding="UTF-8"?> <JobDefinition xmlns="http://schemas.ggf.org/jsdl/2005/11/jsdl"> • <JobDescription> <POSIXApplication xmlns="http://schemas.ggf.org/jsdl/2005/11/jsdl-posix"> • <Executable>/bin/echo</Executable> • <Argument>hello world</Argument> • </POSIXApplication> • </JobDescription> • <MyProxy xmlns="urn:gridsam:myproxy"> • <ProxyServer>myproxy.ncsa.uiuc.edu</ProxyServer> • <ProxyServerDN> • /C=US/O=National Center for Supercomputing • Applications/CN=bosco.ncsa.uiuc.edu</ProxyServerDN> • <ProxyServerPort>7512</ProxyServerPort> • <ProxyServerUserName>myusername</ProxyServerUserName> • <ProxyServerPassPhrase>mypassphrase</ProxyServerPassPhrase> • <ProxyServerLifetime>7512</ProxyServerLifetime> • </MyProxy> • </JobDescription> • </JobDefinition>

  8. Or… • Use GridSAM to add this info into a vanilla JSDL document for you • gridsam-submit -sn ngs -myproxy -myproxyuser myusername -myproxyhost myproxy.ncsa.uiuc.edu -j <HOME>/helloworld.jsdl • MyProxy passphrase: ******** • urn:gridsam:ff80808201afccc00101afccc3900001

  9. myproxy:MyProxyServer: MyProxy server hostname • myproxy:ProxyServerDN: Expected MyProxy server distinguished name so GridSAM can authenticate the server. • myproxy:ProxyServerPort: MyProxy server port. The default is 7512. • myproxy:ProxyServerUserName: The MyProxy username • myproxy:ProxyServerPassPhrase: The plain-text MyProxy passphrase. User should authenticate and authorise the GridSAM server before passing this information across the network. • myproxy:ProxyServerLifetime: The lifetime of the delegated proxy retrieved from the MyProxy server.

  10. Questions? Official Download http://www.omii.ac.uk Project Information and Documentation http://gridsam.sourceforge.net

More Related