Group items tagged

UsernameIdentityProviderA new key-pair is generated and given a certificate signed by another Identity. This is for use in portals where users only have usernames and passwords rather then key-pairs.

UsernameIdentityProviderA new key-pair is generated and given a certificate signed by another Identity. This is for use in portals where users only have usernames and passwords rather then key-pairs.

KrbIdentityProvider An Identity is fetched from a Kerberos service. This allows users with a Kerberos or Active Directory login to get an Identity automatically.

The bulk of the changes in 5.3 are to the client API. One exciting new > feature is built-in support for Groovy, a scripting language with a > Java-like syntax. For example, the following script will upload the > "source.jpg" file, process it with the "paint" application on > griademo1 > and then download the result:

> def GRIADEMO1_JOB_SERVICE_WSDL = > "https://griademo1.it-innovation.soton.ac.uk/gria-basic-app-services/services/JobService?wsdl > > " > def JOB_TYPE = "http://it-innovation.soton.ac.uk/grid/imagemagick/paint > " > def jobService = > serviceFactory.createServiceProxy(GRIADEMO1_JOB_SERVICE_WSDL) > def swirlJob = jobService.createJob(JOB_TYPE, "My swirl job") > swirlJob.input("inputImage").saveFromFile(new File("source.jpg")) > swirlJob.startJob(null) > while (swirlJob.stillActive()) { > println "Waiting..." > Thread.sleep(1000) > } > swirlJob.output("outputImage").read(new File("result.jpg")) > swirlJob.destroy() > > To try it, save the script as "paint.groovy" and then run the client > like this (you'll need a "source.jpg" file too, of course): > > $ gridcli ./paint.groovy > > The above script also demonstrates the new API. "serviceFactory" takes > the URL of a service's WSDL and creates a proxy for it. Notice that, > unlike the 5.2 API, 5.3 does not require you to store the proxy in a > repository.

Running a Groovy script   This is the easiest way to access the Java API. To try it out, create a script named test.groovy containing: println "Starting Groovy script!" def jobService = serviceFactory.createServiceProxy("https://host:8443/gria-basic-app-services/services/JobService?wsdl") println "Getting ID..." def id = jobService.getServiceProviderID() println "Job service identity: " + id Replace host with the address of your GRIA job service. The script is run by passing it as an argument to the normal gridcli command. For example: $ gridcli test.groovy Starting Groovy script! Getting ID... Job service identity: <subject> <subject> will appear at the identity of your job service. The configured keystore and active plugins are the same as when running the GRIA client normally.  

Advanced usage Input arrays An application might require arrays of inputs, whose exact sizes are specified by the user when creating the job. This is supported by GRIA using the minOccurs, maxOccurs and defaultSize attributes on DataStager elements. For example, if your application took between 2 and 8 images as input, you might use the following XML: <DataStager type="input" name="inputImage" minOccurs="2" maxOccurs="8" defaultSize="2"> <Description>Input image</Description> <MimeType>image</MimeType></DataStager> You can use the defaultSize attribute to support older clients that do not know how to specify the desired size of arrays.

Advanced usage Input arrays An application might require arrays of inputs, whose exact sizes are specified by the user when creating the job. This is supported by GRIA using the minOccurs, maxOccurs and defaultSize attributes on DataStager elements. For example, if your application took between 2 and 8 images as input, you might use the following XML: <DataStager type="input" name="inputImage" minOccurs="2" maxOccurs="8" defaultSize="2"> <Description>Input image</Description> <MimeType>image</MimeType></DataStager> You can use the defaultSize attribute to support older clients that do not know how to specify the desired size of arrays.

Advanced usage Input arrays An application might require arrays of inputs, whose exact sizes are specified by the user when creating the job. This is supported by GRIA using the minOccurs, maxOccurs and defaultSize attributes on DataStager elements. For example, if your application took between 2 and 8 images as input, you might use the following XML: <DataStager type="input" name="inputImage" minOccurs="2" maxOccurs="8" defaultSize="2"> <Description>Input image</Description> <MimeType>image</MimeType></DataStager> You can use the defaultSize attribute to support older clients that do not know how to specify the desired size of arrays.

Management View The management view displays resources under the resource which they are managed by. This relationship is a parent-child relationship and this can be seen in the resources endpoint reference, right click a resource and select View EPR there is a managingresource element which tells us the endpoint of the managing resource. If a resource is unmanaged then it appears under the Management Resources node otherwise it appears under its managing resource.

Management View The management view displays resources under the resource which they are managed by. This relationship is a parent-child relationship and this can be seen in the resources endpoint reference, right click a resource and select View EPR there is a managingresource element which tells us the endpoint of the managing resource. If a resource is unmanaged then it appears under the Management Resources node otherwise it appears under its managing resource.

For Linux, the first line of the script (eg. #!/usr/bin/python) is used to determine which interpreter to use. The filename extension can be anything (eg. startJob.py, startJob.sh).

The application wrapper scripts are deployed along with the applications - either on a shared file system or individually on each compute node. Their function is to provide a uniform interface to the Job Service for starting, monitoring and stopping applications.

This allows you to access managed Basic Application Services on griademo2. You can now use the client to store data and run jobs, much as you did before, but managed by the SLA that you proposed and billing to the trade account that you have just opened: