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
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This page is providing yearly activity plan for WP6 in PY1:
This page is providing yearly activity plan for WP6 in PY1:  
* TASK SA2.1 Training
 
* TASK SA2.2 Technical User Support
*TASK SA2.1 Training  
* TASK SA2.3 ELIXIR (start in M6)
*TASK SA2.2 Technical User Support  
* TASK SA2.4 BBMRI (start in M7)
*TASK SA2.3 ELIXIR (start in M6)  
* TASK SA2.5 MoBrain
*TASK SA2.4 BBMRI (start in M7)  
* TASK SA2.6 DARIAH
*TASK SA2.5 MoBrain  
* TASK SA2.7 LifeWatch
*TASK SA2.6 DARIAH  
* TASK SA2.8 EISCAT_3D
*TASK SA2.7 LifeWatch  
* TASK SA2.9 EPOS (start in M7)
*TASK SA2.8 EISCAT_3D  
* TASK SA2.10 Disaster Mitigation
*TASK SA2.9 EPOS  
*TASK SA2.10 Disaster Mitigation


<br>  
<br>  
Line 15: Line 16:
<br>  
<br>  


<br>


{| class="wikitable"
{| class="wikitable sortable"
|-
|-
! Project month<br>  
! Project month<br>  
Line 53: 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 77: Line 79:
Gergely Sipos  
Gergely Sipos  


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


|  
|  
Work with Resource providers of the training VO 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.


|  
|  
Line 98: Line 97:


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


|-
|-
Line 117: 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 136: Line 135:


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


|-
|-
Line 162: Line 161:


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


|-
|-
Line 193: Line 192:


|  
|  
<span>To be developed by security experts funded in T6.1: CERN, CESNET, LIP, NIKHEF
<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 210: Line 209:


|  
|  
To be developed by security experts funded in T6.1: CERN, CESNET, LIP, NIKHEF  
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 222: Line 219:


|  
|  
Exploring possibility of training module developments with other tasks on the following topics:
Exploring possibility of training module developments with other tasks on the following topics:  
 
#. Open Data Processing solution from EGI (by members of task JRA2.1).  
#. Open Data Processing solution from EGI (by members of task JRA2.1).  
#. GPGPU-computing in EGI (by members of task JRA2.4 and NGI-BG).  
#. 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).  
#. Deploying clouds and federated clouds for scientific and educational purposes (by members of the Federated Cloud collaboration).  
#. iRODS training (in collaboration with NGI-FR and the DIRAC team).
#. iRODS training (in collaboration with NGI-FR and the DIRAC team).
|  
|  
Additional training modules  
Additional training modules  
Line 234: Line 233:


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


|-
|-
Line 246: Line 245:
| 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  
! 1  
Line 253: Line 252:
| Establishment of a procedure for handling use case support, RT queue for tracking use cases  
| Establishment of a procedure for handling use case support, RT queue for tracking use cases  
| Gergely Sypos / Enol Fernandez  
| Gergely Sypos / Enol Fernandez  
|  
| ACHIEVED.
|-
|-
! 12 (15)
! 12 (15)  
| Task 6.2  
| 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)  
| 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  
| Pilot usage of EGI infrastructure by HBP  
| Lukasz Dutka / Enol Fernandez  
| Lukasz Dutka / Enol Fernandez  
|  
| Ongoing (in JRA2)
|-
|-
! 12  
! 12  
| Task 6.2  
| 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
| 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
| Implementation roadmap for LOFAR/SKA  
| Tiziana Ferrari / Enol Fernandez  
| Tiziana Ferrari / Enol Fernandez  
|  
|  
Line 278: Line 277:
| <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: 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>  
| <span style="font-size: 13.2799997329712px;">Tommi Nyronen</span>  
|  
| Started in October
|-
|-
! 12  
! 12  
Line 287: Line 286:
| <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>  
| <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  
| Petr Holub  
|  
| To start in October
|-
|-
! 7  
! 7  
Line 294: Line 293:
| <span style="font-size: 13.2799997329712px;">Agreement on the concept of the integrated portal and on CC partners' responsibilty for developing it.</span>  
| <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  
| Alexander Bonvin  
|  
| Discussions took place. Suggestion is to postpone D6.4 to see clearer the WestLife plans.
|-
|-
! 12  
! 12  
Line 301: Line 300:
| <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>  
| <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  
| Alexander Bonvin  
|  
| <u>'''DELAY&nbsp;DELIVERY DATE?'''</u>
|-
|-
! 11  
! 11  
Line 317: Line 316:
| User survey and interviews conducted  
| User survey and interviews conducted  
| Karolj Skala, Davor Davidovic  
| Karolj Skala, Davor Davidovic  
|  
| Ongoing. Presentation in Bari.
|-
|-
! 9  
! 9  
Line 324: Line 323:
| Analysis of user interview and survey outcome  
| Analysis of user interview and survey outcome  
| Karolj Skala, Davor Davidovic  
| Karolj Skala, Davor Davidovic  
|  
| <span style="font-size: 13.28px;">Ongoing. Presentation in Bari.</span>
|-
|-
! 11  
! 11  
Line 331: Line 330:
| <span style="font-size: 12.8000001907349px; line-height: 19.2000007629395px; background-color: rgb(249, 249, 249);">D6.2 Data repository for DARIAH (OTHER)</span>  
| <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  
| Roberto Barbera  
|  
| Ongoing.
|-
|-
! 12  
! 12  
Line 338: Line 337:
| <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>  
| <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  
| 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  
! 2  
| Task 6.8  
| 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.  
| 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  
| Reach agreement on task responsibilities of participating parties  
Line 348: Line 361:
|-
|-
! 6  
! 6  
| Task 6.8  
| Task 6.8 (EISCAT)
| Identify priority development components, draft the first version of Portal Design Specification<br>  
| Identify priority development components, draft the first version of Portal Design Specification<br>  
| First version of the portal design specification to be delivered <br>  
| First version of the portal design specification to be delivered <br>  
| Ingemar Haggstrom(EISCAT)/Yin Chen(EGI) <br>  
| Ingemar Haggstrom(EISCAT)/Yin Chen(EGI) <br>  
| <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  
! 6  
| Task 6.8  
| 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 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>  
| Present the first version of the design specification to EISCAT community, and get feedback and approval.<br>  
| Ingemar Haggstrom(EISCAT)/Yin Chen(EGI) <br>  
| Ingemar Haggstrom(EISCAT)/Yin Chen(EGI) <br>  
| A presentation can be given at the EISCAT annual conference in Sep, to get feedback inputs from EISCAT scientific community <br>
| Achieved.<br>
|-
|-
! 10  
! 10  
| Task 6.8  
| Task 6.8 (EISCAT)
| Develop the portal prototype based on the first version of the design specification.<br>  
| Develop the portal prototype based on the first version of the design specification.<br>  
| Portal prototype to be delivered<br>  
| Portal prototype to be delivered<br>  
| Ake Sandgren(SNIC)<br>  
| Ake Sandgren(SNIC)<br>  
| <br>
| Depends on specification
|-
|-
! 12  
! 12  
| Task 6.8  
| 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>  
| 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>  
| 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>  
| Ingemar Haggstrom(EISCAT)/Yin Chen(EGI) <br>  
| <br>
| <span style="font-size: 13.28px;">Depends on specification</span>
|-
|-
! 12  
! 12  
| Task 6.8  
| Task 6.8 (EISCAT)
| Deliver the Portal prototype, and identify a few EISCAT users to test it. <br>  
| Deliver the Portal prototype, and identify a few EISCAT users to test it. <br>  
| Present the protal EISCAT community, and get feedback.<br>  
| Present the protal EISCAT community, and get feedback.<br>  
| Ake Sandgren(SNIC)<br>  
| Ake Sandgren(SNIC)<br>  
| <br>
| <span style="font-size: 13.28px;">Depends on specification</span>
|-
|-
! 12  
! 12  
| Task 6.9  
| Task 6.9 (EPOS)
| EPOS requirements analysis and outline of pilot use cases are agreed<br>  
| EPOS requirements analysis and outline of pilot use cases are agreed<br>  
|  
|  
Line 391: Line 404:


| Daniele Balio (EPOS/INGV), Diego Scardaci (EGI.eu/INFN)<br>  
| Daniele Balio (EPOS/INGV), Diego Scardaci (EGI.eu/INFN)<br>  
| <br>
| Achieved.
|-
|-
! 6  
! 6  
Line 398: Line 411:
| Integrated information about the use cases that the CC members will work with  
| Integrated information about the use cases that the CC members will work with  
| Simon Lin, Eric Yen  
| Simon Lin, Eric Yen  
|  
| <u>'''SLOW.'''</u>
|-
|-
! 6  
! 6  
Line 405: Line 418:
| <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; 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>  
| <span style="font-size: 13.2799997329712px;">Simon Lin, Eric Yen</span>  
|  
| Achieved.
|-
|-
! 8  
! 8  
Line 412: Line 425:
| <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: 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>  
| <span style="font-size: 13.2799997329712px;">Simon Lin, Eric Yen</span>  
| The portals will be implemented and delivered as D6.9 in M14.
| <u>'''???&nbsp;'''</u>The portals will be implemented and delivered as D6.9 in M14.
|}
|}


<br>
<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.