The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
VT MPI within EGI
Jump to navigation
Jump to search
General Project Information
- Leader: CZ ?, ES ?, IE ?
- Mailing List: Not yet known
- Status: Active
- Start Date: 10/Nov/2011
- End Date: Expected to finish before the middle of January 2015
- Meetings:
Motivation
The MPI VO could solve a number of problems:�
- dedicated CPUs for MPI jobs�
- MPI specific test probes can run on all sites using the VO Monitoring services of Ibergrid (EGI-InSPIRE VO Services group)�
- accounting for MPI jobs
- improved communication with MPI users (those who heavily use MPI will be in this VO)
Output
A set of resources and feedback to resource centers, user communities and technology providers on how to improve MPI within�EGI.
Tasks
Despite a dedicated SA3 activity to support�MPI there still seem to be significant issues in uptake and satisfaction amongst the user communities.
- Work with user communities�and projects that use MPI resources (e.g. ITER, MAPPER, A&A, etc) to demonstrate that MPI can work successfully in EGI.
- Attributes/groups� within the VO can be used to provide application level access control.
- Bridge between MPI users and developers of MPI support within EGI.
Members
- EGI.eu: Karolis Eigelis
- NGIs: CZ, MC, HR, ES, PT, IE, GR, IT, SK
Resources
- CRM system: <TO_COME>
Progress
- Task 1
- Task 2
- ...
- Task N