Difference between revisions of "EGI-Engage:WP6-PY2-Roadmap"
Jump to navigation
Jump to search
(15 intermediate revisions by the same user not shown) | |||
Line 45: | Line 45: | ||
| <br> | | <br> | ||
|- | |- | ||
! | ! Feb 2017 | ||
| Task 6.2, Tech. User Support | | Task 6.2, Tech. User Support | ||
| | | | ||
Line 52: | Line 52: | ||
*<span style="line-height: 1.5em; font-size: 13.28px;">Euro-Argo (ENVRIplus) (Yin)</span> | *<span style="line-height: 1.5em; font-size: 13.28px;">Euro-Argo (ENVRIplus) (Yin)</span> | ||
*ICOS (ENVRIplus) (Diego) | ** Prototype of the data cloud with data subscription and delivery capability for users. The prototype is expected to be based on the following technologies: <span style="line-height: 1.5em; font-size: 13.28px;">Hadoop, SWIFT, WS-PGRAD, and HIVE</span> | ||
*EuroBioImaging (INDIGO) (Yin) | *ICOS (ENVRIplus) (Diego): | ||
*ENES (INDIGO) ( | **Two use cases are under impementation, using similar technical setup: Integration of a community portal with the EGI cloud, with scalable back-end based on docker, and with data stage-in/out capabilities towards EUDAT. Integration of station data into data products. | ||
*EMSO (Diego) | *EuroBioImaging (INDIGO) (Yin): | ||
** UPV in INDIGO has designed and now developing a 'VRE as a service' architecture that can support this INDIGO use case. EGI needs to integrate the standard INDIGO components with EGI FedCloud. We will evaluate this after the INDIGO components are released (after July 2016) | |||
**Sign SLA with the community about the services that would underpin the setup on EGI | |||
*ENES (INDIGO) (Yin): | |||
**Similar to EuroBioImaging, but with using the Ophidia data analytics framework instead of the UPV system. | |||
*EMSO (Diego): | |||
** Signed collaboration agreement after the establishement of the EMSO ERIC (maybe after the EMSO assembly, Sept 2016) | |||
**<span style="line-height: 1.5em; font-size: 13.28px;">EMSODEV Data Management Platform prototype deployed in the EGI Federated Cloud</span> | |||
**Established 'Competence Centre' with countries/NGIs common to EMSO and EGI (IT, FR, UK, GR, PT, IE. DE and NL are initially observers, the inclusion of Turkey is under discussion.) | |||
**SLA agreed for the EGI services that will underpin the EMSO platform. | |||
Other communities:<br> | <span style="line-height: 1.5em; font-size: 13.28px;">Other communities:</span> <br> | ||
*Long-tail of science: | |||
**Help SA1 finalise and release the EGI pltaform | |||
**Support NGI user support teams in uptake of the platform | |||
**Support the communication team promote the platform directly to the long-tail | |||
*BigDataEurope H2020 project (Enol) | *BigDataEurope H2020 project (Enol) | ||
* | *Assess VRE projects (Gergely) | ||
* | *Assess RIs from the recent ESFRI roadmap, identify 'low hanging fruits' suggest actions for engagement (Gergely) | ||
| See in previous column | | See in previous column | ||
| | | | ||
|- | |- | ||
! | ! | ||
*Feb 2017 | |||
| Task 6.3, ELIXIR | | Task 6.3, ELIXIR | ||
| | | | ||
| | | | ||
*5 scientific use case (from M6.3) are running on the EGI FedCloud & Conculsions are drawn on the use of cloud federation for ELIXIR applications (D6.15) | *5 scientific use case (from M6.3) are running on the EGI FedCloud & Conculsions are drawn on the use of cloud federation for ELIXIR applications (D6.15) | ||
*The ELIXIR Compute Platform is operated as a service for ELIXIR users, integrating cloud, AAI, monitoring, GOCDB services from EGI (underpinned by an SLA) | *The ELIXIR Compute Platform is operated as a service for ELIXIR users, integrating cloud, AAI, monitoring, GOCDB services from EGI (underpinned by an SLA) | ||
| | | | ||
Kimmo Mattila | Kimmo Mattila | ||
Gergely | |||
Gergely | |||
| | | | ||
Line 87: | Line 100: | ||
| Task 6.4, BBMRI | | Task 6.4, BBMRI | ||
| | | | ||
| TBD during next telco (week of 18th) | | TBD during next telco (week of 18th) | ||
| <span style="font-size: 13.28px;">CC leader</span> | | <span style="font-size: 13.28px;">CC leader</span> | ||
| | | | ||
|- | |- | ||
! | ! | ||
July 2016 | |||
Dec 2016 | |||
| Task 6.5, MoBrain | | Task 6.5, MoBrain | ||
| | | | ||
| | | | ||
*GPGPU portals (with GROMACS and AMBER) are offered as production service (D6.12) | *GPGPU portals (with GROMACS and AMBER) are offered as production service (D6.12) | ||
*Scipion (Cryo-EM) is available for cloud deployment in EGI clouds via AppDB (D6.14) | *Scipion (Cryo-EM) is available for cloud deployment in EGI clouds via AppDB (D6.14) | ||
| Alexandre Bonvin | | Alexandre Bonvin | ||
| | | | ||
|- | |- | ||
! | ! | ||
* | *Sept 2016 | ||
*Oct 2016 | |||
*Feb 2017 | |||
| Task 6.6, DARIAH | | Task 6.6, DARIAH | ||
| | | | ||
| | | | ||
*E-infra service portfolio for A&H established (gLibrary, SEE, CDSTAR, WS-PGRADE) (D6.17 and previous deliverables) | *User involvement and sustainability plan | ||
*Active user base - They are engaged with at community events, Webinars, pro-active outreach | *E-infra service portfolio for A&H established (gLibrary, SEE, CDSTAR, WS-PGRADE) (D6.17 and previous deliverables) | ||
*<span style="line-height: 1.5em; font-size: 13.28px;">Active user base - They are engaged with at community events, Webinars, pro-active outreach</span> | |||
| | | | ||
Davor, <br>Zoltan (for D6.17) | <span style="font-size: 13.28px; line-height: 19.92px;">DANS (who exactly?)</span> | ||
Davor Davidovic, <br>Zoltan Farkas (for D6.17) | |||
All members | |||
| | | | ||
Line 130: | Line 152: | ||
**Citizen Science | **Citizen Science | ||
| Jesus | | Jesus Marco | ||
| | | | ||
|- | |- | ||
! | ! | ||
*Continuous | |||
*Cont. refinement | |||
*Feb-June 2017 | |||
| Task 6.8, EISCAT_3D | | Task 6.8, EISCAT_3D | ||
| | | | ||
Line 142: | Line 168: | ||
| | | | ||
Ingemar | Ingemar | ||
<br> | <br> | ||
Victor Mendez | Victor Mendez | ||
| | | | ||
|- | |- | ||
! | ! | ||
Feb 2017 | |||
| Task 6.9, EPOS | | Task 6.9, EPOS | ||
| | | | ||
| | | | ||
*3 community pilots are implemented: AAI, Computing, Data management ( | *3 community pilots are implemented: AAI, Computing, Data management (New deliverable in project month 24) | ||
*Initial conclusions are drawn from the setup | *Initial conclusions are drawn from the setup (These conclusions will drive work in PY3, turning the pilots into production services.) | ||
| | | Daniele Bailo | ||
| | | | ||
|- | |- | ||
! | ! Feb 2017 | ||
| Task 6.10, Disaster Mitigation | | Task 6.10, Disaster Mitigation | ||
| | | | ||
| | | | ||
*Typhoon Haiyan (PH, TW) | *Implementation of the following case studies (with the use of grid services): | ||
*Tsunami cave in Lhong-Aceh Besar (ID, TW) | **Typhoon Haiyan (PH, TW) | ||
*Flooding 2014-15 (MY, TW) | **Tsunami cave in Lhong-Aceh Besar (ID, TW) | ||
*Flooding 2008 (Nepal, TW) | **Flooding 2014-15 (MY, TW) | ||
*Tsunami impact analysis in South China Sea (TW, PH) | **Flooding 2008 (Nepal, TW) | ||
**Tsunami impact analysis in South China Sea (TW, PH) | |||
*TBC: Setup of a federated cloud infrastructure in the Asia-Pacific region | |||
| | | <br> See in previous column | ||
| <br> | | <br> | ||
|} | |} | ||
[[Category:EGI-Engage]] | [[Category:EGI-Engage]] |
Latest revision as of 10:38, 18 July 2016
This page is providing yearly activity plan for WP6 in PY2
Project month |
Project Tasks |
Work to be done |
Goal (measurable) |
Owner (responsible person) |
Comments |
---|---|---|---|---|---|
x | Task 6.1, Training |
|
See in previous column | ||
Feb 2017 | Task 6.2, Tech. User Support |
Priority communities:
Other communities:
|
See in previous column | ||
|
Task 6.3, ELIXIR |
|
Kimmo Mattila Gergely |
||
|
Task 6.4, BBMRI | TBD during next telco (week of 18th) | CC leader | ||
July 2016 Dec 2016 |
Task 6.5, MoBrain |
|
Alexandre Bonvin | ||
|
Task 6.6, DARIAH |
|
DANS (who exactly?) Davor Davidovic, All members |
||
x | Task 6.7, LifeWatch |
|
Jesus Marco | ||
|
Task 6.8, EISCAT_3D |
|
Ingemar
Victor Mendez |
||
Feb 2017 |
Task 6.9, EPOS |
|
Daniele Bailo | ||
Feb 2017 | Task 6.10, Disaster Mitigation |
|
See in previous column |