Difference between revisions of "EGI-Engage:WP6-PY2-Roadmap"
Jump to navigation
Jump to search
(4 intermediate revisions by the same user not shown) | |||
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> | ||
** 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> | ** 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> | ||
*ICOS (ENVRIplus) (Diego): | *ICOS (ENVRIplus) (Diego): | ||
** | **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. | ||
*EuroBioImaging (INDIGO) (Yin): | *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) | ** 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 | **Sign SLA with the community about the services that would underpin the setup on EGI | ||
*ENES (INDIGO) (Yin): | *ENES (INDIGO) (Yin): | ||
**Similar to EuroBioImaging, but with using the Ophidia data analytics framework instead of the UPV system. | **Similar to EuroBioImaging, but with using the Ophidia data analytics framework instead of the UPV system. | ||
*EMSO (Diego): | *EMSO (Diego): | ||
** Signed collaboration agreement after the establishement of the EMSO ERIC (maybe after the EMSO assembly, Sept 2016) | ** Signed collaboration agreement after the establishement of the EMSO ERIC (maybe after the EMSO assembly, Sept 2016) | ||
Line 65: | Line 65: | ||
**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.) | **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. | **SLA agreed for the EGI services that will underpin the EMSO platform. | ||
<span style="line-height: 1.5em; font-size: 13.28px;">Other communities:</span> <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) | *Assess RIs from the recent ESFRI roadmap, identify 'low hanging fruits' suggest actions for engagement (Gergely) | ||
Line 176: | Line 182: | ||
| | | | ||
| | | | ||
*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 | | Daniele Bailo | ||
Line 186: | Line 191: | ||
| 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> See in previous column |
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 |