Alert.png 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.

Difference between revisions of "EGI-Engage:WP6-PY1-Roadmap"

From EGIWiki
Jump to navigation Jump to search
 
(42 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{Template:EGI-Engage menubar}} {{TOC_right}}
This page is providing yearly activity plan for WP6 in PY1:  


<br>
*TASK SA2.1 Training
 
*TASK SA2.2 Technical User Support
This page is providing yearly activity plan for WP6 in PY1<br>
*TASK SA2.3 ELIXIR (start in M6)
*TASK SA2.4 BBMRI (start in M7)
*TASK SA2.5 MoBrain
*TASK SA2.6 DARIAH
*TASK SA2.7 LifeWatch
*TASK SA2.8 EISCAT_3D
*TASK SA2.9 EPOS
*TASK SA2.10 Disaster Mitigation


<br>  
<br>  


<br>  
<br>  
== YIN  ==
{| class="wikitable"
|-
! Project month<br>
!
Project Tasks
!
Work to be done
!
Goal&nbsp;
(measurable)
!
Owner
(reponsible person)
! Comments
|-
! 1
| Task 6.8
|
1) Portal Design Specification
2) Portal prototype
|
1) Agreement on task responsibilities of participating parties by May 2015
2) First version of the portal specification to be drafted by the end of Summer 2015
3) First prototype of the portal aims to be delivered by Dec 2015
|
*Portal Design Specification: EISCAT (Ingemar Haggstrom)
*Portal prototype SNIC (Ake Sandgren)
*EGI contribution (Yin Chen)
| <br>
|-
! 1
| <br>
|
|
|
|
|-
! 2
| <br>
| <br>
| <br>
| <br>
| <br>
|-
! 3
|
| <br>
| <br>
| <br>
| <br>
|-
! 4
|
| <br>
| <br>
| <br>
| <br>
|-
! 5
|
| <br>
| <br>
| <br>
| <br>
|-
! 6
|
| <br>
| <br>
| <br>
| <br>
|-
! 7
|
| <br>
| <br>
| <br>
| <br>
|-
! 8
|
| <br>
| <br>
| <br>
| <br>
|-
! 9
|
| <br>
| <br>
| <br>
| <br>
|-
! 10
|
| <br>
| <br>
| <br>
| <br>
|-
! 11
|
| <br>
| <br>
| <br>
| <br>
|-
! 12
|
| <br>
| <br>
| <br>
| <br>
|}
<br>
== ENOL  ==
{| class="wikitable"
|-
! Project month<br>
!
Project Tasks
!
Work to be done
!
Goal&nbsp;
(measurable)
!
Owner
(reponsible person)
! Comments
|-
! 1
| Task 6.2
| Definition of the technical use cases support process
| Establishment of a procedure for handling use case support, RT queue for tracking use cases
| Gergely Sypos / Enol Fernandez
|
|-
! 9
| Task 6.2
| Pilot usage of EGI infrastructure by HBP
|
|
|
|-
! 9
| Task 6.7
| Assisted pattern recognition tools integrated with EGI for citizen science
| XXX
| Jesús Marco/Fernando Aguilar
|
|-
! 12
| Task 6.7
| Data flow handler and basic R tools to integrate and process data from Ecological Observatories on EGI
| XXX
| Jesús Marco/Fernando Aguilar)
|
|-
|}
<br>
== DIEGO  ==
{| class="wikitable"
|-
! Project month<br>
!
Project Tasks
!
Work to be done
!
Goal&nbsp;
(measurable)
!
Owner
(reponsible person)
! Comments
|-
! 1
| Task 6.1
| <br>
| <br>
| <br>
| <br>
|-
! 1
| Task 6.2
|
|
|
|
|-
! 2
|
| <br>
| <br>
| <br>
| <br>
|-
! 3
|
| <br>
| <br>
| <br>
| <br>
|-
! 4
|
| <br>
| <br>
| <br>
| <br>
|-
! 5
|
| <br>
| <br>
| <br>
| <br>
|-
! 6
|
| <br>
| <br>
| <br>
| <br>
|-
! 7
|
| <br>
| <br>
| <br>
| <br>
|-
! 8
|
| <br>
| <br>
| <br>
| <br>
|-
! 9
|
| <br>
| <br>
| <br>
| <br>
|-
! 10
|
| <br>
| <br>
| <br>
| <br>
|-
! 11
|
| <br>
| <br>
| <br>
| <br>
|-
! 12
|
| <br>
| <br>
| <br>
| <br>
|}


<br>  
<br>  


== GERGELY  ==
{| class="wikitable sortable"
 
{| class="wikitable"
|-
|-
! Project month<br>  
! Project month<br>  
Line 351: Line 55:


|  
|  
Document was delivered at the end of May: http://go.egi.eu/trainingplan  
ACHIEVED. Document was delivered at the end of May: http://go.egi.eu/trainingplan  


|-
|-
Line 375: Line 79:
Gergely Sipos  
Gergely Sipos  


|  
| ACHIEVED.
|-
|-
!  
!  
Line 384: Line 88:


|  
|  
<span style="font-family: Calibri, sans-serif; font-size: 11pt; letter-spacing: 0.1pt; line-height: 115%;">Work with Resource providers of the training VO</span><span style="font-family: Calibri, sans-serif; font-size: 11pt; letter-spacing: 0.1pt; line-height: 115%;">&nbsp;to identify
Work with Resource providers of the training VO to identify suitable business model for continued provisioning of thevirtualised training e-infrastructure that can operate 24/7 to serve EGI-related courses and self-paced training needs.  
suitable business model for continued provisioning of thevirtualised training
e-infrastructure that can operate 24/7 to serve EGI-related courses and
self-paced training needs.</span>


|  
|  
Line 396: Line 97:


|  
|  
<br>
Capacity is secured at least until the end of EGI-Engage.


|-
|-
Line 406: Line 107:


|  
|  
<span style="font-family: Calibri, sans-serif; font-size: 14.6666669845581px; letter-spacing: 0.133333340287209px; line-height: 16.8666667938232px;">Prepare module based on the joint use case that has been identified and documented during the EGI-EUDAT meeting at the EGI Conference in Lisbon. (FedCloud, B2Find, B2Drop, B2Safe)</span>
Prepare module based on the joint use case that has been identified and documented during the EGI-EUDAT meeting at the EGI Conference in Lisbon. (FedCloud, B2Find, B2Drop, B2Safe)  


|  
|  
Joint training module with EUDAT&nbsp;
Joint training module with EUDAT  


|  
|  
Line 415: Line 116:


|  
|  
<span style="font-size: 13.2799997329712px;">F2F delivery at the EGI Community Forum?</span><span style="font-size: 13.2799997329712px; line-height: 1.5em;">&nbsp;</span>  
<span style="font-size: 13.2799997329712px;">Ongoing, aiming at F2F delivery at the EGI Community Forum</span>  


|-
|-
Line 428: Line 129:


|  
|  
Training module on the 'EGI&nbsp;long tail of science' platform  
Training module on the 'EGI long tail of science' platform  


|  
|  
Line 434: Line 135:


|  
|  
F2F delivery at the EGI Community Forum?
Ongoing, aiming at F2F delivery at the EGI Community Forum  


|-
|-
Line 449: Line 150:
of EUDAT. The content will be developed for a joint event that will be held in
of EUDAT. The content will be developed for a joint event that will be held in
the autumn, then will be shared as a training module in the marketplace.
the autumn, then will be shared as a training module in the marketplace.
</span>
</span>  


<br>  
<br>  
Line 460: Line 161:


|  
|  
Event approx in October (date, venue TBD)
Topics to be identified at WISE workshop in Oct.


|-
|-
Line 474: Line 175:
endorse VM images for scientific/training purposes. The module will define the
endorse VM images for scientific/training purposes. The module will define the
characteristics of ‘secure’ VM images, will teach how to prepare such images,
characteristics of ‘secure’ VM images, will teach how to prepare such images,
and will demonstrate how to assess the security characteristics of such images.&nbsp;
and will demonstrate how to assess the security characteristics of such images.
</span>
</span>  


<br>  
<br>  
Line 483: Line 184:
</span> <span>
</span> <span>
EGI Federated Cloud.
EGI Federated Cloud.
</span>
</span>  


<br>  
<br>  


|  
|  
Vincenzo<span class="Apple-tab-span" style="white-space:pre"> </span> Spinoso  
Vincenzo Spinoso  


|  
|  
<span>To be developed by security experts funded in T6.1:</span>&nbsp;<span style="font-family: Calibri, sans-serif; font-size: 11pt; letter-spacing: 0.1pt; line-height: 115%;">CERN, CESNET, LIP, NIKHEF</span>  
<span>TOPIC</span><span style="font-size: 13.28px; line-height: 1.5em;">&nbsp;development is ongoing.&nbsp;</span><span style="line-height: 1.5em; font-size: 13.28px;">To be developed by security experts funded in T6.1: CERN, CESNET, LIP, NIKHEF</span>  


|-
|-
Line 500: Line 201:
Task 6.1  
Task 6.1  


| Define incident handling process - by CSIRT
|  
|  
|
Training module on Incident handling in the EGI Federated Cloud.  
<span style="line-height: 19.9200000762939px; font-size: 13.2799997329712px;">Training module on&nbsp;</span><span style="font-family: Calibri, sans-serif; font-size: 11pt; letter-spacing: 0.1pt; line-height: 115%;">Incident handling in the EGI Federated Cloud.&nbsp;</span>


|  
|  
Line 508: Line 209:


|  
|  
<span style="font-size: 11pt; line-height: 16.8666667938232px; font-family: Calibri, sans-serif; letter-spacing: 0.1pt;">To be developed by security experts funded in T6.1:</span><span style="font-size: 13.2799997329712px;">&nbsp;</span><span style="font-family: Calibri, sans-serif; font-size: 11pt; letter-spacing: 0.1pt; line-height: 16.8666667938232px;">CERN, CESNET, LIP, NIKHEF</span>  
Topic development ongoing. Training in Bari. To be developed by security experts funded in T6.1: CERN, CESNET, LIP, NIKHEF<br>  
 
F2F delivery at EGI Community Forum?


|-
|-
Line 520: Line 219:


|  
|  
<span style="line-height: 1.5em; text-indent: -18pt; font-size: 13.2799997329712px;">Exploring possibility of training module developments with other tasks on the following topics:</span>
Exploring possibility of training module developments with other tasks on the following topics:  


<span style="line-height: 1.5em; text-indent: -18pt; font-size: 13.2799997329712px;">1. Open Data Processing solution from EGI (by
#. Open Data Processing solution from EGI (by members of task JRA2.1).  
members of task JRA2.1).</span>
#. GPGPU-computing in EGI (by members of task JRA2.4 and NGI-BG).  
 
#. Deploying clouds and federated clouds for scientific and educational purposes (by members of the Federated Cloud collaboration).  
<span style="line-height: 1.5em; text-indent: -18pt; font-size: 13.2799997329712px;">2. GPGPU-computing in EGI (by members of task
#. iRODS training (in collaboration with NGI-FR and the DIRAC team).
JRA2.4 and NGI-BG).</span>
 
3.&nbsp;<span style="line-height: 1.5em; text-indent: -18pt; font-size: 13.2799997329712px;">Deploying clouds and federated clouds for
scientific and educational purposes (by members of the Federated Cloud
collaboration).</span>
 
4.&nbsp;<span style="line-height: 1.5em; text-indent: -18pt; font-size: 13.2799997329712px;">iRODS training (in collaboration with NGI-FR and
the DIRAC team).</span>
 
<br>


|  
|  
Line 544: Line 233:


|  
|  
F2F delivery at EGI Community Forum?
Waiting for developments to finish.&nbsp;


|-
|-
! 4
! 4  
| Task 6.1
| Task 6.1  
|  
|  
Ensure that the Training Marketplace is used accross EGI, and that it can collect and provide the relevant details about events, content, etc and the impact.  
Ensure that the Training Marketplace is used accross EGI, and that it can collect and provide the relevant details about events, content, etc and the impact.  


Provide templates and surveys for EGI trainers to be able to collect relevant metrics.&nbsp;
Provide templates and surveys for EGI trainers to be able to collect relevant metrics.&nbsp;  


| Mechanisms and tools to assess impact of training activities.
| Mechanisms and tools to assess impact of training activities.  
| Gergely Sipos
| Gergely Sipos  
| '''<u>TMP seems to be going down. We need to find an alternative.</u>'''
|-
! 1
| Task 6.2
| Definition of the technical use cases support process
| Establishment of a procedure for handling use case support, RT queue for tracking use cases
| Gergely Sypos / Enol Fernandez
| ACHIEVED.
|-
! 12 (15)
| Task 6.2
| Finalise use case and requirements document (M6); Selection of technologies potentially matching requirements (M9); Basic tests and feedback (M12); Final tests and feedback (M15)
| Pilot usage of EGI infrastructure by HBP
| Lukasz Dutka / Enol Fernandez
| Ongoing (in JRA2)
|-
! 12
| Task 6.2
| Arrange collaboration agreement with LOFAR/SKA and possibly other projects from the ASTERICS cluster project; Collect and document e-infrastructure use cases and requirements from the communities; Analyse requirements, propose implementation plan and roadmap
| Implementation roadmap for LOFAR/SKA
| Tiziana Ferrari / Enol Fernandez
|  
|  
|-
|-
!  
! 12
| Task 6.3 (ELIXIR)
|  
|  
<span style="font-size: 13.2799997329712px;">Collect use cases from ELIXIR-EXCELERATE, CC members, EGI</span><span style="font-size: 13.2799997329712px; line-height: 1.5em;">&nbsp;members (e.g. GAPF</span><span style="font-size: 13.2799997329712px; line-height: 1.5em;">&nbsp;VT),&nbsp;</span><span style="font-size: 13.2799997329712px; line-height: 1.5em;">then select the most relevant ones for the CC to work with. Analyse use cases from the technical perspective to capture requirements for e-infra and ELXIR</span><span style="font-size: 13.2799997329712px; line-height: 1.5em;">&nbsp;RI</span><span style="font-size: 13.2799997329712px; line-height: 1.5em;">&nbsp;services.&nbsp;</span>
<span style="font-size: 12.8000001907349px; line-height: 19.2000007629395px; background-color: rgb(249, 249, 249);">Life science requirements analysis and driver use case(s) with implementation roadmap are agreed</span>
| <span style="font-size: 12.8000001907349px; line-height: 19.2000007629395px; background-color: rgb(249, 249, 249);">M6.3:</span>&nbsp;<span style="font-size: 12.8000001907349px; line-height: 19.2000007629395px; background-color: rgb(249, 249, 249);">Life science requirements analysis and driver use case(s) with implementation roadmap are agreed</span><span style="font-size: 13.2799997329712px; line-height: 1.5em;">.&nbsp;</span>
| <span style="font-size: 13.2799997329712px;">Tommi Nyronen</span>
| Started in October
|-
! 12
| Task 6.4 (BBMRI)
|  
|  
<span style="font-size: 13.2799997329712px; line-height: 19.9200000762939px;">Collect use cases from the BBMRI</span>&nbsp;community and <span style="font-size: 13.2799997329712px; line-height: 19.9200000762939px;">from CC members</span><span style="font-size: 13.2799997329712px; line-height: 1.5em;">&nbsp;</span><span style="font-size: 13.2799997329712px; line-height: 1.5em;">then select the most relevant ones for the CC to work with. Analyse use cases from the technical perspective to capture requirements for e-infra and BBMRI</span>&nbsp;<span style="font-size: 13.2799997329712px; line-height: 1.5em;">RI</span><span style="font-size: 13.2799997329712px; line-height: 1.5em;">&nbsp;services. Design suitable technical architecture to address the requirements.&nbsp;</span><br>
| <span style="font-size: 12.8000001907349px; line-height: 19.2000007629395px; background-color: rgb(249, 249, 249);">M6.2:</span>&nbsp;<span style="font-size: 12.8000001907349px; line-height: 19.2000007629395px; background-color: rgb(249, 249, 249);">Security and privacy requirements and secure storage architectural design are agreed</span>
| Petr Holub
| To start in October
|-
! 7
| Task 6.5 (MoBrain)
| Discuss options for the implementation of a fully integrated MoBrain portal (built on N4U and WeNMR technologies, considering work in WestLife VRE project). Reach agreement on the concept of the integrated portal and on CC partners' responsibilty for developing it.
| <span style="font-size: 13.2799997329712px;">Agreement on the concept of the integrated portal and on CC partners' responsibilty for developing it.</span>
| Alexander Bonvin
| Discussions took place. Suggestion is to postpone D6.4 to see clearer the WestLife plans.
|-
! 12
| Task 6.5 (MoBrain)
|  
|  
| <span style="font-size: 12.8000001907349px; line-height: 19.2000007629395px; background-color: rgb(249, 249, 249);">D6.4:</span>&nbsp;<span style="font-size: 12.8000001907349px; line-height: 19.2000007629395px; background-color: rgb(249, 249, 249);">Fully integrated MoBrain web portal (OTHER)</span>
| Alexander Bonvin
| <u>'''DELAY&nbsp;DELIVERY DATE?'''</u>
|-
! 11
| Task 6.5 (MoBrain)
| Learn about the 'Accelerated Computing platform' of EGI&nbsp;(GPGPU facility) at the EGI Community Forum; Perform initial tests on it with GROMACS and AMBER.
| Initial tests on the 'Accelerated Computing platform' of&nbsp;EGI
| Alexandre Bonvin, Peter Solagna
| Depends on progress of Task JRA2.4
|-
! 4
| Task 6.6 (DARIAH)
|  
|  
Prepare user survey to be used by the CC to collect needs and requirements from digital humanities communities and users.&nbsp;Interview leaders of relevant DARIAH WGs, run the survey in relevant groups
| User survey and interviews conducted
| Karolj Skala, Davor Davidovic
| Ongoing. Presentation in Bari.
|-
! 9
| Task 6.6 (DARIAH)&nbsp;
| Collect and analyse the outcome of the user survey and interviews, feed findings into CC activities (both technical and community related)&nbsp;
| Analysis of user interview and survey outcome
| Karolj Skala, Davor Davidovic
| <span style="font-size: 13.28px;">Ongoing. Presentation in Bari.</span>
|-
! 11
| Task 6.6 (DARIAH)
| Integrate gLibrary into the DARIAH gateway, Perform tests, Import dataset from the Austrian Academy of Sciences, Provide materials for digital humanities researchers on how to use the data reportisoty.&nbsp;
| <span style="font-size: 12.8000001907349px; line-height: 19.2000007629395px; background-color: rgb(249, 249, 249);">D6.2 Data repository for DARIAH (OTHER)</span>
| Roberto Barbera
| Ongoing.
|-
! 12
| Task 6.6 (DARIAH)
| Decide about the best approach to integrate the application with EGI platforms and with the DARIAH gateway services. Implement the integration.&nbsp;
| <span style="font-size: 12.8000001907349px; line-height: 19.2000007629395px; background-color: rgb(249, 249, 249);">D6.5 Final version of Multi-Source Distributed Real-Time Search and Information Retrieval application (OTHER)</span>
| Tibor Kalman
| Ongoing. '''<u>Status to check</u>'''
|-
! 9
| Task 6.7 (LifeWatch)
| Develop tools for analysing input from citizens (e.g. pictures)
| <span style="font-size: 12.8000001907349px; line-height: 19.2000007629395px; background-color: rgb(249, 249, 249);"> D6.1 Assisted pattern recognition tools integrated with EGI for citizen science (OTHER)</span>
| Jesús Marco
| Ongoing.
|-
! 12
| Task 6.7 (LifeWatch)
| Provide access to R and related analysis tools in Virtual Machines for the processing of data from Ecological Observatories
| <span style="font-size: 12.8000001907349px; line-height: 19.2000007629395px; background-color: rgb(249, 249, 249);"> Data flow handler and basic R tools to integrate and process data from Ecological Observatories on EGI (DEM)</span>
| Jesús Marco
| Ongoing.
|-
! 2
| Task 6.8 (EISCAT)
| Scope the investigation plan, and get each party agree on the task force. Set up weekly meeting for discussion and progress monitoring.
| Reach agreement on task responsibilities of participating parties
| Yin Chen (EGI)
| Agreement was achieved by May
|-
! 6
| Task 6.8 (EISCAT)
| Identify priority development components, draft the first version of Portal Design Specification<br>
| First version of the portal design specification to be delivered <br>
| Ingemar Haggstrom(EISCAT)/Yin Chen(EGI) <br>
| '''<u style="font-weight: bold;">SLOW. WIL</u>L <u>RESULT&nbsp;<span style="font-size: 13.28px; line-height: 1.5em;">LATE D6.3.</span></u>'''
|-
! 6
| Task 6.8 (EISCAT)
| Present the first version of design specification to EISCAT community and get feedback and approval<br>
| Present the first version of the design specification to EISCAT community, and get feedback and approval.<br>
| Ingemar Haggstrom(EISCAT)/Yin Chen(EGI) <br>
| Achieved.<br>
|-
! 10
| Task 6.8 (EISCAT)
| Develop the portal prototype based on the first version of the design specification.<br>
| Portal prototype to be delivered<br>
| Ake Sandgren(SNIC)<br>
| Depends on specification
|-
! 12
| Task 6.8 (EISCAT)
| Based on the feedback from EISCAT community, identify priority development areas. Refine the first version of the design specification, adding new functional elements and to draft the second version of the design specification. Present the second version of design specification to EISCAT community and get feedback<br>
| Second version of the portal design specification to be delivered, feedback to be obtained from EISCAT community<br>
| Ingemar Haggstrom(EISCAT)/Yin Chen(EGI) <br>
| <span style="font-size: 13.28px;">Depends on specification</span>
|-
! 12
| Task 6.8 (EISCAT)
| Deliver the Portal prototype, and identify a few EISCAT users to test it. <br>
| Present the protal EISCAT community, and get feedback.<br>
| Ake Sandgren(SNIC)<br>
| <span style="font-size: 13.28px;">Depends on specification</span>
|-
! 12
| Task 6.9 (EPOS)
| EPOS requirements analysis and outline of pilot use cases are agreed<br>
|  
|  
*AAI requirements analysed and the EPOS AAI architecture envisaged.
*Basic multidisciplinary AAI use case defined: it deals with the discovery of heterogeneous data from the ICS-C portal
*An extended, single discipline, computational oriented use case defined<br>
| Daniele Balio (EPOS/INGV), Diego Scardaci (EGI.eu/INFN)<br>
| Achieved.
|-
|-
!  
! 6
|  
| Task 6.10 (DM CC)
|  
| Collect details about the use cases from each CC member. This should cover: Details of the disaster event(s) to be simulated/predicted; details on required data; details on simulation applications, tool and gateways to interact with the data; necessary visualisation tools; implementation roadmap and timeline
|  
| Integrated information about the use cases that the CC members will work with
|  
| Simon Lin, Eric Yen
|  
| <u>'''SLOW.'''</u>
|-
! 6
| Task 6.10 (DM CC)
| Planning participation and contributions to the 40th APAN meeting
| <span style="font-size: 13.2799997329712px; line-height: 19.9200000762939px;">Contributions and meeting at the 40th APAN meeting (</span><span>&lt;a href="http://www.apan.net/meetings/KualaLumpur2015/"&gt;http://www.apan.net/meetings/KualaLumpur2015/&lt;/a&gt;)</span>
| <span style="font-size: 13.2799997329712px;">Simon Lin, Eric Yen</span>
| Achieved.
|-
|-
!  
! 8
|  
| Task 6.10 (DM CC)
|  
| <br>
|  
| <span style="font-size: 12.8000001907349px; line-height: 19.2000007629395px; background-color: rgb(249, 249, 249);">Specification of the web portals for tsunami wave propagation simulations and for WRF-based weather simulation</span>
|  
| <span style="font-size: 13.2799997329712px;">Simon Lin, Eric Yen</span>
|  
| <u>'''???&nbsp;'''</u>The portals will be implemented and delivered as D6.9 in M14.
|}
|}


[[Category:EGI-Engage]]
<br>

Latest revision as of 10:52, 14 October 2015

This page is providing yearly activity plan for WP6 in PY1:

  • TASK SA2.1 Training
  • TASK SA2.2 Technical User Support
  • TASK SA2.3 ELIXIR (start in M6)
  • TASK SA2.4 BBMRI (start in M7)
  • TASK SA2.5 MoBrain
  • TASK SA2.6 DARIAH
  • TASK SA2.7 LifeWatch
  • TASK SA2.8 EISCAT_3D
  • TASK SA2.9 EPOS
  • TASK SA2.10 Disaster Mitigation




Project month

Project Tasks

Work to be done

Goal 

(measurable)

Owner

(reponsible person)

Comments

3

Task 6.1

Define EGI's training plan for the 1st year of EGI-Engage

M6.1 Joint training programme for the first project year (With EUDAT, PRACE, CCs, NGIs, UCB)

Gergely Sipos

ACHIEVED. Document was delivered at the end of May: http://go.egi.eu/trainingplan

5

Task 6.1

Setup training VO on the Federated Cloud

Register training robot certificate, generate proxies for students and trainers

Prepare training materials for 3.5 course (slides + hands-on exercises incl. VM images and datasets) 

Test training material and setup by July 15, deliver courses in second part of July

Deliver two courses on EGI Federated Cloud at 'Software Carpentry workshop' (SAP, UK) and HPCS (Amsterdam)

Gergely Sipos

ACHIEVED.

10

Task 6.1

Work with Resource providers of the training VO to identify suitable business model for continued provisioning of thevirtualised training e-infrastructure that can operate 24/7 to serve EGI-related courses and self-paced training needs.

Suitable business model for continued operation of the training VO in EGI

Gergely Sipos

Capacity is secured at least until the end of EGI-Engage.

10

Task 6.1

Prepare module based on the joint use case that has been identified and documented during the EGI-EUDAT meeting at the EGI Conference in Lisbon. (FedCloud, B2Find, B2Drop, B2Safe)

Joint training module with EUDAT

Diego Scardaci

Ongoing, aiming at F2F delivery at the EGI Community Forum

8

Task 6.1

After the platform components are integrated and tested develop training for the NGI user support teams and EGI.eu staff on how to support long-tail users with the platform. 

Training module on the 'EGI long tail of science' platform

Diego Scardaci, Peter Solagna

Ongoing, aiming at F2F delivery at the EGI Community Forum

8

Task 6.1

A module about security policy, procedures and interoperability solutions in the various e-infrastructures, with possible involvement of EUDAT. The content will be developed for a joint event that will be held in the autumn, then will be shared as a training module in the marketplace.


Joint event and training module with PRACE

Dave Kelsey

Topics to be identified at WISE workshop in Oct.

5

Task 6.1

The module will target those who prepare and those who endorse VM images for scientific/training purposes. The module will define the characteristics of ‘secure’ VM images, will teach how to prepare such images, and will demonstrate how to assess the security characteristics of such images.


Training module on Virtual Machine preparation and certification in the EGI Federated Cloud.


Vincenzo Spinoso

TOPIC development is ongoing. To be developed by security experts funded in T6.1: CERN, CESNET, LIP, NIKHEF

10

Task 6.1

Define incident handling process - by CSIRT

Training module on Incident handling in the EGI Federated Cloud.

Dave Kelsey

Topic development ongoing. Training in Bari. To be developed by security experts funded in T6.1: CERN, CESNET, LIP, NIKHEF

12

Task 6.1

Exploring possibility of training module developments with other tasks on the following topics:

  1. . Open Data Processing solution from EGI (by members of task JRA2.1).
  2. . GPGPU-computing in EGI (by members of task JRA2.4 and NGI-BG).
  3. . Deploying clouds and federated clouds for scientific and educational purposes (by members of the Federated Cloud collaboration).
  4. . iRODS training (in collaboration with NGI-FR and the DIRAC team).

Additional training modules

Gergely Sipos

Waiting for developments to finish. 

4 Task 6.1

Ensure that the Training Marketplace is used accross EGI, and that it can collect and provide the relevant details about events, content, etc and the impact.

Provide templates and surveys for EGI trainers to be able to collect relevant metrics. 

Mechanisms and tools to assess impact of training activities. Gergely Sipos TMP seems to be going down. We need to find an alternative.
1 Task 6.2 Definition of the technical use cases support process Establishment of a procedure for handling use case support, RT queue for tracking use cases Gergely Sypos / Enol Fernandez ACHIEVED.
12 (15) Task 6.2 Finalise use case and requirements document (M6); Selection of technologies potentially matching requirements (M9); Basic tests and feedback (M12); Final tests and feedback (M15) Pilot usage of EGI infrastructure by HBP Lukasz Dutka / Enol Fernandez Ongoing (in JRA2)
12 Task 6.2 Arrange collaboration agreement with LOFAR/SKA and possibly other projects from the ASTERICS cluster project; Collect and document e-infrastructure use cases and requirements from the communities; Analyse requirements, propose implementation plan and roadmap Implementation roadmap for LOFAR/SKA Tiziana Ferrari / Enol Fernandez
12 Task 6.3 (ELIXIR)

Collect use cases from ELIXIR-EXCELERATE, CC members, EGI members (e.g. GAPF VT), then select the most relevant ones for the CC to work with. Analyse use cases from the technical perspective to capture requirements for e-infra and ELXIR RI services. 

Life science requirements analysis and driver use case(s) with implementation roadmap are agreed

M6.3: Life science requirements analysis and driver use case(s) with implementation roadmap are agreed Tommi Nyronen Started in October
12 Task 6.4 (BBMRI)

Collect use cases from the BBMRI community and from CC members then select the most relevant ones for the CC to work with. Analyse use cases from the technical perspective to capture requirements for e-infra and BBMRI RI services. Design suitable technical architecture to address the requirements. 

M6.2: Security and privacy requirements and secure storage architectural design are agreed Petr Holub To start in October
7 Task 6.5 (MoBrain) Discuss options for the implementation of a fully integrated MoBrain portal (built on N4U and WeNMR technologies, considering work in WestLife VRE project). Reach agreement on the concept of the integrated portal and on CC partners' responsibilty for developing it. Agreement on the concept of the integrated portal and on CC partners' responsibilty for developing it. Alexander Bonvin Discussions took place. Suggestion is to postpone D6.4 to see clearer the WestLife plans.
12 Task 6.5 (MoBrain) D6.4: Fully integrated MoBrain web portal (OTHER) Alexander Bonvin DELAY DELIVERY DATE?
11 Task 6.5 (MoBrain) Learn about the 'Accelerated Computing platform' of EGI (GPGPU facility) at the EGI Community Forum; Perform initial tests on it with GROMACS and AMBER. Initial tests on the 'Accelerated Computing platform' of EGI Alexandre Bonvin, Peter Solagna Depends on progress of Task JRA2.4
4 Task 6.6 (DARIAH)

Prepare user survey to be used by the CC to collect needs and requirements from digital humanities communities and users. Interview leaders of relevant DARIAH WGs, run the survey in relevant groups

User survey and interviews conducted Karolj Skala, Davor Davidovic Ongoing. Presentation in Bari.
9 Task 6.6 (DARIAH)  Collect and analyse the outcome of the user survey and interviews, feed findings into CC activities (both technical and community related)  Analysis of user interview and survey outcome Karolj Skala, Davor Davidovic Ongoing. Presentation in Bari.
11 Task 6.6 (DARIAH) Integrate gLibrary into the DARIAH gateway, Perform tests, Import dataset from the Austrian Academy of Sciences, Provide materials for digital humanities researchers on how to use the data reportisoty.  D6.2 Data repository for DARIAH (OTHER) Roberto Barbera Ongoing.
12 Task 6.6 (DARIAH) Decide about the best approach to integrate the application with EGI platforms and with the DARIAH gateway services. Implement the integration.  D6.5 Final version of Multi-Source Distributed Real-Time Search and Information Retrieval application (OTHER) Tibor Kalman Ongoing. Status to check
9 Task 6.7 (LifeWatch) Develop tools for analysing input from citizens (e.g. pictures) D6.1 Assisted pattern recognition tools integrated with EGI for citizen science (OTHER) Jesús Marco Ongoing.
12 Task 6.7 (LifeWatch) Provide access to R and related analysis tools in Virtual Machines for the processing of data from Ecological Observatories Data flow handler and basic R tools to integrate and process data from Ecological Observatories on EGI (DEM) Jesús Marco Ongoing.
2 Task 6.8 (EISCAT) Scope the investigation plan, and get each party agree on the task force. Set up weekly meeting for discussion and progress monitoring. Reach agreement on task responsibilities of participating parties Yin Chen (EGI) Agreement was achieved by May
6 Task 6.8 (EISCAT) Identify priority development components, draft the first version of Portal Design Specification
First version of the portal design specification to be delivered
Ingemar Haggstrom(EISCAT)/Yin Chen(EGI)
SLOW. WILL RESULT LATE D6.3.
6 Task 6.8 (EISCAT) Present the first version of design specification to EISCAT community and get feedback and approval
Present the first version of the design specification to EISCAT community, and get feedback and approval.
Ingemar Haggstrom(EISCAT)/Yin Chen(EGI)
Achieved.
10 Task 6.8 (EISCAT) Develop the portal prototype based on the first version of the design specification.
Portal prototype to be delivered
Ake Sandgren(SNIC)
Depends on specification
12 Task 6.8 (EISCAT) Based on the feedback from EISCAT community, identify priority development areas. Refine the first version of the design specification, adding new functional elements and to draft the second version of the design specification. Present the second version of design specification to EISCAT community and get feedback
Second version of the portal design specification to be delivered, feedback to be obtained from EISCAT community
Ingemar Haggstrom(EISCAT)/Yin Chen(EGI)
Depends on specification
12 Task 6.8 (EISCAT) Deliver the Portal prototype, and identify a few EISCAT users to test it.
Present the protal EISCAT community, and get feedback.
Ake Sandgren(SNIC)
Depends on specification
12 Task 6.9 (EPOS) EPOS requirements analysis and outline of pilot use cases are agreed
  • AAI requirements analysed and the EPOS AAI architecture envisaged.
  • Basic multidisciplinary AAI use case defined: it deals with the discovery of heterogeneous data from the ICS-C portal
  • An extended, single discipline, computational oriented use case defined
Daniele Balio (EPOS/INGV), Diego Scardaci (EGI.eu/INFN)
Achieved.
6 Task 6.10 (DM CC) Collect details about the use cases from each CC member. This should cover: Details of the disaster event(s) to be simulated/predicted; details on required data; details on simulation applications, tool and gateways to interact with the data; necessary visualisation tools; implementation roadmap and timeline Integrated information about the use cases that the CC members will work with Simon Lin, Eric Yen SLOW.
6 Task 6.10 (DM CC) Planning participation and contributions to the 40th APAN meeting Contributions and meeting at the 40th APAN meeting (<a href="http://www.apan.net/meetings/KualaLumpur2015/">http://www.apan.net/meetings/KualaLumpur2015/</a>) Simon Lin, Eric Yen Achieved.
8 Task 6.10 (DM CC)
Specification of the web portals for tsunami wave propagation simulations and for WRF-based weather simulation Simon Lin, Eric Yen ??? The portals will be implemented and delivered as D6.9 in M14.