Mandate and expected results

• Define a proposal for a parallel execution framework within EMI

EMI Technical Objectives in Context (derived from Compute Area Work Plan, DJRA1.1.2)

• (A11.1) Define a proposal for a parallel execution framework within EMI (M18)
• (A12.1) Implementation of the proposal for a parallel execution framework within EMI (M32)
• (A13.4) Enable capabilities to support cross-middleware multi-core, multi-node execution (M36)

Task Force Leader

• Enol Fernández (gLite-MPI PT)

Task Force Members

• John Gordon (Accounting)
• Bernd Schuller (UNICORE)
• Christian Ulrik Soettrup (ARC)
• Salvatore Monforte (gLite)

Tracking

• EMI Development Tracker - task #21764: https://savannah.cern.ch/task/?21764

Status

The MPI TF has agreed on using the EMI-ES ParallelEnvironment as the common framework for executing jobs. After reviewing specification version 0.3, we have proposed the following modifications:

• (implementation) Change type of ParallelEnvironment Type field to "xsd:string"
• (semantic) Term "Slot" is confusing. Should be clearer
• (semantic) ProcessesPerSlot should be ProcessesPerHost
• (semantic) ProcessesPerHost and ThreadsPerProcess need flag "useSlotsPerHost" to indicate that the actual value of "SlotsPerHost" should be used

Any other parameter needed will be given using the option element.

As backend implementation, mpi-start will be adapted to the different mechanisms provided by each CE to develop the ParallelEnvironment. This would allow a common set of features for all the stacks. For very specific site configuration, mpi-start team will try to develop appropriate solutions, although is up to the site admins to decide the final implementation to use.

-- EnolFernandezDelCastillo - 04-Aug-2011

• EMI-ParallelJobFramework-0.1.doc: Parallel Job Framework Design