Skip to main content

Home/ GSCD_TE/ Group items tagged example

Rss Feed Group items tagged

jes stranig

Application Metadata XML - GRIA - 0 views

  • 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.
    • jes stranig
       
      Creation d'un DataStrager par input lors de son utilisation
florian bernard

Links with Other Services - GRIA - 0 views

  • Managed Services The SLA service is of no use if it does not manage any functional services. There are five conditions that must be met in order for a functional service to be managed: At the functional service: The SLA service must be in the functional service's list of "Trusted Management Services". The SLA service's CA certificate must be a trusted CA in the functional service's key-store. The SLA service must be in the "management-services" group of the functional service. At the SLA service: The functional service's CA certificate must be a trusted CA in the SLA service's key-store. The functional service must be in the "sla-managed-services" group of the SLA service. If the functional services that require managing are hosted on the same machine as the SLA service (and therefore share the same certificate) then steps 2-5 are not necessary, otherwise see below for more detail.
    • florian bernard
       
      TE1: Pour lier un service fonctionnel au SLA manager le service doit implementer certaines contraintes.
florian bernard

Client Programming Tutorial - GRIA - 0 views

  • 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.  
florian bernard

Re: [gria] GRIA 5.3 released - 0 views

  • 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.
1 - 4 of 4
Showing 20 items per page