Difference between revisions of "EGI-Engage:WP4-PY1-Roadmap"
(One intermediate revision by one other user not shown) | |||
Line 85: | Line 85: | ||
| G. Taffoni <br> S. Gaudet<br> | | G. Taffoni <br> S. Gaudet<br> | ||
| <br> | | <br> | ||
|- | |||
! 4 | |||
| Task 4.2 | |||
| | |||
OCCI 1.1 Feature freeze | |||
| N/A | |||
| | |||
| | |||
|- | |- | ||
! 4 | ! 4 | ||
Line 104: | Line 113: | ||
! 6 | ! 6 | ||
| Task 4.1 <br> | | Task 4.1 <br> | ||
| End of technical design Open Data Platform for EGI-Engage. | | End of technical design Open Data Platform for EGI-Engage. | ||
| It should be clear how to integrate Open Data Platform with the existing EGI security model and what interfaces should be available. | | It should be clear how to integrate Open Data Platform with the existing EGI security model and what interfaces should be available. | ||
| Lukasz Dutka | | Lukasz Dutka | ||
| <br> | | <br> | ||
|- | |- | ||
Line 181: | Line 190: | ||
|- | |- | ||
! 8 | ! 8 | ||
| Task 4.1 | | Task 4.1 | ||
| First pilot version available for public tests | | First pilot version available for public tests | ||
| Provisioning software for tests and getting first feedback from the potential users. | | Provisioning software for tests and getting first feedback from the potential users. | ||
| Lukasz Dutka | | Lukasz Dutka | ||
| <br> | | <br> | ||
|- | |- | ||
Line 194: | Line 203: | ||
M. Chatziangelou | M. Chatziangelou | ||
A. Lopez | A. Lopez | ||
| <br> | | <br> | ||
Line 216: | Line 225: | ||
| A. Lopez<br> | | A. Lopez<br> | ||
| <br> | | <br> | ||
|- | |||
! 10 | |||
| Task 4.2 | |||
| OCCI support for Azure backend | |||
| New rOCCI release, supporting MS Azure. | |||
| A. Lopez | |||
| | |||
|- | |- | ||
! 10 | ! 10 | ||
Line 226: | Line 242: | ||
| M.Verlato<br> | | M.Verlato<br> | ||
| <br> | |||
|- | |||
! 10 | |||
| Task 4.1 | |||
| First Open Data Pilot Deployment | |||
| The software realizing minimal valuable use case should be deployed as a pilot. | |||
| Lukasz Dutka | |||
| <br> | | <br> | ||
|- | |- | ||
Line 233: | Line 256: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
|- | |- | ||
Line 248: | Line 264: | ||
Final design of interactions to relocate running VMs within sites. | Final design of interactions to relocate running VMs within sites. | ||
OCCI 1.2 preview release | |||
| | | | ||
OCCI support for resizing and/or snapshots | OCCI support for resizing and/or snapshots | ||
Deliverable 4.4 | Deliverable 4.4 (relocation) | ||
Initial OCCI support for OCCI 1.2 | |||
| A. Lopez<br> | | A. Lopez<br> |
Latest revision as of 10:44, 3 June 2015
This page is providing yearly activity plan for WP4 in PY1
Project month |
Project Tasks |
Work to be done |
Goal (measurable) |
Owner (reponsible person) |
Comments |
---|---|---|---|---|---|
1 | All WP4 tasks | Collection of people names and population of mailing lists | Communications in place | T. Ferrari | COMPLETE |
2 | Task 4.2 | Survey on OCCI suport request for other CMFs | Definition of OCCI support roadmap | A. Lopez | Survey created sent to involved parties |
2 | Task 4.4 | Review of available technologies for using GPUs in grid and cloud
Resume of EGI-Inspire GPGPU VT |
Kick-off and GPGPU VT handover meeting |
M.Verlato |
|
3 |
Task 4.2 |
JRA activities presentation and collection of requirements. Review of OCCI 1.1 status and plans for OCCI 1.2. Setup communication channel for requirements |
Discussion at IaaS session at EGI Conference Workplan and ETA for complete OCCI 1.1 support RT requirements queue set up |
A. Lopez |
OCCI Implementation status: https://wiki.egi.eu/wiki/Fedcloud-tf:WorkGroups:Scenario1#Servers |
3 | Task 4.4 |
Review of available technologies for using GPUs in grid and cloud
Analysis of requirements from user communities |
Discussion at GPGPU session at EGI Conference |
M.Verlato |
|
3 | Task 4.3 |
Preliminary Discussion about requirements and integration EGI-CANFAR |
Presentation about CANFAR at EGI conference |
G. Taffoni S. Gaudet |
|
4 | Task 4.2 |
OCCI 1.1 Feature freeze |
N/A | ||
4 | Task 4.4 |
End of review of available technologies for using GPUs in grid and cloud
End of analysis of requirements from user communities |
Technical report (to be included in Milestone 1.2 First intermediate report) and wiki pages |
M.Verlato |
|
4 | Task 4.3 |
Discussion about requirements and integration EGI-CANFAR Preliminary Integration Road map |
discuss at IVOA interoperability meeting |
G. Taffoni S. Gaudet |
|
6 | Task 4.1 |
End of technical design Open Data Platform for EGI-Engage. | It should be clear how to integrate Open Data Platform with the existing EGI security model and what interfaces should be available. | Lukasz Dutka | |
6 |
|||||
6 | Task 4.2 |
Draft design of OCCI extension for creating snapshots Draft design of OCCI extension for resizing running VMs |
Internal drafts of OCCI extension |
A. Lopez |
|
6 | Task 4.3 |
Collection of technical requirements for the integration of the D4SCIENCE and CANFAR cloud infrastructures Definition of "user stories" for interoperation with EUDAT, revision of AAI roadmaps and discussion of their interoperability |
Cookbooks for EGI-EUDAT service interoperation D4SCIENCE and CANFAR integration roadmap |
E. Fernandez | |
6 | Task 4.3 |
CANFAR EGI Integration Roadmap | Deliverable 4.1 |
E. Fernandez G. Taffoni S. Gaudet |
|
7 | |||||
7 |
Task 4.2 |
Draft of the design for VM relocation within sites. |
Internal draft for discussion.
|
A. Lopez | |
7 | Task 4.4 |
Modification/configuration at site level (OS driver, hypervisor, CMF, VM images) for supporting GPUs in cloud
Definition of abstract GPU-related CREAM JDL attributes to be mapped in the supported batch systems |
Cloud site with working GPU and installation manual
Update of the CREAM JDL specification document |
M.Verlato |
|
8 | Task 4.1 | First pilot version available for public tests | Provisioning software for tests and getting first feedback from the potential users. | Lukasz Dutka | |
9 |
Task 4.2 | AppDB: design phase of the VM/brokering functionality. |
A design document describing the solution that will be followed for offering brokering functions to the users through the AppDB. |
M. Chatziangelou A. Lopez |
|
9 | Task 4.2 |
Final design of OCCI extension for creating snapshots. Final design of OCCI extension for resizing running VMs. Candidate version of the design for VM relocation within sites. |
Deliverable 4.2 (snapshots) Deliverable 4.3 (resize) Candidate document for final review (relocation) |
A. Lopez |
|
10 | Task 4.2 | OCCI support for Azure backend | New rOCCI release, supporting MS Azure. | A. Lopez | |
10 | Task 4.4 |
First step of integration with FedCloud (AppDB, accounting, brokering, ...)
First implementation of GPU support in CREAM |
Tools and configuration manual, possible some demonstration
GPU-enabled CREAM prototype released for testing |
M.Verlato |
|
10 | Task 4.1 | First Open Data Pilot Deployment | The software realizing minimal valuable use case should be deployed as a pilot. | Lukasz Dutka | |
11 | |||||
12 |
Task 4.2 |
Initial implementation of OCCI extensions. Final design of interactions to relocate running VMs within sites. OCCI 1.2 preview release |
OCCI support for resizing and/or snapshots Deliverable 4.4 (relocation) Initial OCCI support for OCCI 1.2 |
A. Lopez |
|
12 | Task 4.3 |
First step of integration with FedCloud | Initial tests on SSO and VOSpace
|
G. Taffoni S. Gaudet |
|
12 | Task 4.4 |
Revision of available technologies, further improvement and extension of supporting GPUs in FedCloud
End of testing of GPU-enabled CREAM prototype and feedback collection |
Technical report contributing to Project Periodic Report (first period)
Official final CREAM release with full GPU support |
M.Verlato |