12/12/2011 - MPI VT Management meeting

Date: 12/12/2011 Present: Ivan Diaz Alvarez, Zdenek Sustr, Roberto Dopazo

Alvaro not present, delegated Ivan Enol not present, travelling

• MPI current status in EGI (20 min)
  • Accounting system.

Ivan: No special accounting support. Only way to recognize MPI jobs is to check jobs with >100 % efficiency - Still development to be done. - Apel needs to give data.

• • Information system.

- Problems with criteria for detecting MPI. - Checking for MPI availability -- mostly decided by checking installed applications. - Not all sites reporting MPI capability correctly - Ivan: For BDII, the metrics portal checks the GlueHostApplicationSoftwareRunTimeEnvironment property for the *MPI* regular expression. - Action: Sites need to set properties correctly.

• • Batch systems support.

- Roberto: starting work on MPI support for SGE, to be ready for EMI2 - The main problem with the batch system is that it is not receiving reliable info from information system (not truly a batch system matter)

• • VOs/users/sites usage.

- MPI VO -- bring together sites and users interested in MPI - This VO is NOT indended for everyday use by all users wishing to use MPI - This VO IS intended for users who wish to cooperate with the VT to make MPI support in EGI better - The main reason for its establishment is to collect experience that will be later adopted by regular VOs - Ivan: User Community under SA3 would also be a good idea. - Name "MPI" considered too promissing (users could beleive it is for everyday, full-featured use of MPI) - Decided on name "MPI Kickstart" - CESNET will use its VOMS to setup the VO

• MPI VT actions (30 min)
  • MPI documentation in EGI.

- All recipients, please, provide links that you know of: - Site Admin documentation - User documentation - This documentation will be reviewded and we will decide what needs updating or extendidng.

• • Monitoring probes

- Not clear how to implement. It is possible to check if site has enough slots to run parallel jobs, or run "average" jobs, but larger jobs (more slots) may still fail

• • Gather information from MPI sites.

- After establishing the VO, and contacting sites for resources, more requests for informaion can be added. - We need to agree what info we want before that

• • MPI whish list.

- Check Savannah - Formal support for maintaining a "wish list" or feature requests or ... will be established if need arises.

• Next meeting:

• • Since many pariticipants have not been present today, the time of the next meeting will be decided asynchronously through e-mail or doodle.