GLITE Tutorial

Advanced gLite: Distributed Applications (1)

An application may consist of multiple jobs that run concurrently on different CEs and communicate with each other.
Every job has to be informed about the contact data of its partners:
  • For every job, require full Internet access from the CE:
      Requirements = ... && 
        other.GlueHostNetworkAdapterOutboundIP
        == true;
    
  • For every job, manually select an eligible CE:
      glite-wms-job-list-match -a jdlFile
    
  • For every job, write the contact information of all communication partners (name of CE and the number of an unassigned port) into an input file for that job:
      hostname:port
    
  • Submit every job to the selected CE.
      glite-wms-job-submit -rCE jdlFile
    
  • Each job determines from the input file the required information and contacts its communication partners correspondingly.
    Problem: when the jobs start, previously unassigned port numbers may already be in use.
While this strategy can be automatized by a script, it represents a "hack".
#IMAGEALT#

EGEE JKU RISC