Versions Compared

Old Version 9

changes.mady.by.user Unknown User (clavalley)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (clavalley)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

According to Pisa Team (Michael Kuss, Johan Bregeon, Francesco Longo) work, the use of EGEE workers is a good solution to produce huge amounts of MonteCarlo simulation data.   On this purpose, they have created EGEE GLAST Virtual Organization which is now operational and through which GLAST software has been installed in some EGEE sites (see VO status document by M.Kuss in attachment).  An important amount of data has been produced using this system, independently of Pipeline2 interfaces and data management procedures.  

The development of the link between Pipeline2 interfaces and procedures will EGEE GLAST Virtual Organization infrastructure should then allow to use EGEE ressources to answer to MonteCarlo simulations Pipeline2 requests. 

...

Some implementation steps have been suggested as well:

  • org-glast-pipeline-server: the The files attached to the Job instance should be different for EGEE type tasks.   Then  this Then org-glast-pipeline-server package should be able to distinguish between an EGEE job and a SLAC/IN2P3 farms oneones, according to  taskConfig.xml file "type" variable value.
  • A new package contained in org-glast-jobcontrol jar file needs to be developped:  EGEEJobControlService (equivalent to LSFJobControlService and BQSJobControlService),  including appropriate submit(), getStatus() and cancel() methods.
  • Job outputs can remain in EGEE Storage Elements, providing provided that they are referenced in catalog databases, and that they can be easily downloaded by users