Changes between Version 10 and Version 11 of QCG-AdvancedClient

Show
Ignore:
Timestamp:
11/18/12 20:53:54 (12 years ago)
Author:
mmamonski
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QCG-AdvancedClient

    v10 v11  
    1 Currently submitting co-allocated MUSCLE application is only possible using the XML !JobProfile (compare [[QCG-SimpleClient]]). Beside the different job description format you have to end the `qcg-sub` command with the `QCG` keyword: 
     1Currently submitting co-allocated MUSCLE application is only possible using the XML !JobProfile (compare [[QCG-SimpleClient]]). Beside the different job description format you have to suffix the `qcg-sub` command with the `QCG` keyword: 
    22{{{ 
    33$ qcg-sub muscle.xml QCG 
    44}}}  
    5 == Example of co-allocated MUSCLE job == 
     5== Example (Fusion - Transport Turbulence Equilibrium) == 
     6 * Install your application on every cluster you wish to use 
     7 * register it on every cluster using [http://apps.man.poznan.pl/trac/qcg-computing/wiki/ComunityModules QCG Community Modules (QCE)] mechanism: 
     8{{{ 
     9qcg-module-create -g plggmuscle Fusion/Turbulence 
     10}}} 
     11The module must bear the same name on every cluster. Inside the module you can set/prepend any environment variable, add dependencies to other modules, e.g.: 
     12{{{ 
     13#%Module 1.0 
     14 
     15 
     16proc ModulesHelp { } { 
     17        puts stderr "\tName: Fusion/Turbulence" 
     18        puts stderr "\tVersion: 0.1" 
     19        puts stderr "\tMaintainer: plgmamonski" 
     20} 
     21 
     22module-whatis   "Fusion/Turbulence, 0.1" 
     23 
     24#add path to the native MUSCLE kernels 
     25prepend-path PATH /home/plgrid-groups/plggmuscle/fusionkernels/bin/ 
     26 
     27set curMod [module-info name] 
     28 
     29if { [ module-info mode load ] } { 
     30        puts stderr "$curMod load complete." 
     31} 
     32 
     33if { [ module-info mode remove ] } { 
     34        puts stderr "$curMod unload complete." 
     35} 
     36}}} 
     37You can set there two environment variables interpreted by the MUSCLE framework: 
     38 * MUSCLE_CLASSPATH 
     39 * MUSCLE_LIBPATH 
     40to set Java classpath and the path of dynamically loadable libraries. Thanks to this mechanism you can use single abstract CxA that do not contain any site-specific paths. Also you can load the module in interactive QCG job: 
     41{{{ 
     42bash-4.1$ module load Fusion/Turbulence 
     43Fusion/Turbulence load complete 
     44}}} 
     45* Prepare XML job description: 
    646{{{ 
    747<qcgJob appId="MAPPER" xmlns:jxb="http://java.sun.com/xml/ns/jaxb" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">