Difference between revisions of "EEP Pilot4"
Jump to navigation
Jump to search
(Created page with "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 resour...") |
|||
(17 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
Welcome to the wiki space of the EGI/EUDAT/PRACE (EEP) collaboration. | {{Template:EEP_menubar}} | ||
[[Category:EGI EUDAT PRACE]] | |||
{{TOC_right}} | |||
'''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. | Several pilot activities were defined to address specific but generic use cases of usage of different resource infrastructures. | ||
= Pilot 4: Monitoring and resource discovery = | = Pilot 4: Monitoring and resource discovery = | ||
== Contacts == | |||
Coordinator: Stephen Burke/EGI.eu (EGI) | Coordinator: Stephen Burke/EGI.eu (EGI) | ||
Mailing list: eep-pilot4 at mailman.egi.eu | |||
* [https://www.egi.eu/sso/groupView/eep-pilot4 Members] | ([https://www.egi.eu/sso/group/eep-pilot4 manage membership]) | * [https://www.egi.eu/sso/groupView/eep-pilot4 Members] | ([https://www.egi.eu/sso/group/eep-pilot4 manage membership]) | ||
== Information == | |||
* Participants | * Participants | ||
** Infrastructures: EGI, PRACE | ** Infrastructures: EGI (S. Burke, T. Ferrari, G. Sipos), EUDAT (M. van de Sanden), PRACE (T. Eissler, I. Saverchenko) | ||
** Technology Providers: TBD | ** Technology Providers: TBD | ||
** Communities: MAPPER, VERCE | ** Communities: MAPPER (I. Saverchenko), VERCE (I. Klampanos) | ||
* Meeting and minutes | * [https://indico.egi.eu/indico/categoryDisplay.py?categId=84 Meeting and minutes] | ||
* [https://rt.egi.eu/rt/Search/Results.html?Query=Queue%20%3D%20%27eep-pilot4%27%20AND%20%28Status%20%3D%20%27new%27%20OR%20Status%20%3D%20%27open%27%20OR%20Status%20%3D%20%27accepted%27%20OR%20Status%20%3D%20%27developed%27%20OR%20Status%20%3D%20%27stalled%27%20OR%20Status%20%3D%20%27feedback%27%29 | * Actions | ||
** [https://rt.egi.eu/rt/Search/Results.html?Query=Queue%20%3D%20%27eep-pilot4%27%20AND%20%28Status%20%3D%20%27new%27%20OR%20Status%20%3D%20%27open%27%20OR%20Status%20%3D%20%27accepted%27%20OR%20Status%20%3D%20%27developed%27%20OR%20Status%20%3D%20%27stalled%27%20OR%20Status%20%3D%20%27feedback%27%29 View actions] | |||
**[https://rt.egi.eu/rt/index.html Add an action] | |||
= Mandate = | = Mandate = | ||
(define | * (1) demonstrate 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 | |||
*** which resources are accessible to my user community matching user requirements? | |||
*** which resources provide enough network capacity | |||
** PRACE | |||
*** which compute resources which are accessible to me, should be used at a given time? | |||
*** which resources provide the best network transfer performance | |||
* (2) definition of a profile of minimum set of information that should be available from different infrastructures | |||
* (3) definition of information schema supported by all infrastructures (or a subset of them) - e.g. GLUE2, GOCDB service repository, will publishing of GLUE 2 information be supported by PRACE/EUDAT? | |||
NEED: define a information discovery workflow for MAPPER | |||
= Milestones = | = Milestones = | ||
* MAPPER: 30-04-2013 definition of minimum information profile needed | |||
* MAPPER: 30-04-2013 draft workflow for information discovery EGI, PRACE, EUDAT | |||
* EGI/EUDAT/PRACE: 30-05-2013: feasibility study | |||
= References = | = References = |
Latest revision as of 17:38, 12 March 2013
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
- (1) demonstrate 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
- which resources are accessible to my user community matching user requirements?
- which resources provide enough network capacity
- PRACE
- which compute resources which are accessible to me, should be used at a given time?
- which resources provide the best network transfer performance
- EUDAT
- (2) definition of a profile of minimum set of information that should be available from different infrastructures
- (3) definition of information schema supported by all infrastructures (or a subset of them) - e.g. GLUE2, GOCDB service repository, will publishing of GLUE 2 information be supported by PRACE/EUDAT?
NEED: define a information discovery workflow for MAPPER
Milestones
- MAPPER: 30-04-2013 definition of minimum information profile needed
- MAPPER: 30-04-2013 draft workflow for information discovery EGI, PRACE, EUDAT
- EGI/EUDAT/PRACE: 30-05-2013: feasibility study