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.
EEP Pilot4
Jump to navigation
Jump to search
| EGI EUDAT PRACE collaboration menu: | Home • | Pilot 1 • | Pilot 2 • | Pilot 3 • | Pilot 4 |
Welcome to the wiki space of the EGI/EUDAT/PRACE (EEP) collaboration.
Several pilot activities were defined to address specific but generic use cases of usage of different resource infrastructures.
Pilot 4: Monitoring and resource discovery
Contacts
Coordinator: Stephen Burke/EGI.eu (EGI)
Mailing list: eep-pilot4 at mailman.egi.eu
Information
- Participants
- Infrastructures: EGI (S. Burke, T. Ferrari, G. Sipos), EUDAT (M. van de Sanden), PRACE (T. Eissler, I. Saverchenko)
- Technology Providers: TBD
- Communities: MAPPER (I. Saverchenko), VERCE (I. Klampanos)
- Meeting and minutes
- Actions
Mandate
- harvesting information on service end-points available, their properties and status from different infrastructures:
- EUDAT:
- which data stores in the data federation are accessible (e.g. not in downtime, allowing a given user/user community to get space)
- how much space is available
- EGI:
- EUDAT:
- PRACE:
- which compute resources that are accessible to me, should be used at a given time, in particular to support tightly coupled simulations?
- which resources provide the best network transfer perfomarce
- PRACE:
- definition of a profile of minimum information that should be available from different infrastructures
- definition of information schema supported by all infrastructures (or a subset of them)
Milestones
(define)