Difference between revisions of "EGI-Engage:WP5-PY1-Roadmap"
Jump to navigation
Jump to search
m |
|||
(4 intermediate revisions by 2 users not shown) | |||
Line 30: | Line 30: | ||
! 1 | ! 1 | ||
| Task 5.1 | | Task 5.1 | ||
| * Core activities bidding process, including the extension of the service portfolio | | | ||
* Core activities bidding process, including the extension of the service portfolio | |||
* UMD, definition of the processes to improve the service and include new technologies such as the fedcloud software | * UMD, definition of the processes to improve the service and include new technologies such as the fedcloud software | ||
* Implement an SLA framework with the EGI's stakeholders | * Implement an SLA framework with the EGI's stakeholders | ||
* Procedure for the VMI endorsement definition and implementation | * Procedure for the VMI endorsement definition and implementation | ||
| * Core activities are bid and the new consortia are ready to start delivering the services in May 2016 | | | ||
* Core activities are bid and the new consortia are ready to start delivering the services in May 2016 | |||
* UMD releases the JRA2.2 outputs and makes available the releases for the production infrastructure. | * UMD releases the JRA2.2 outputs and makes available the releases for the production infrastructure. | ||
* The VMI endorsement procedure is approved by OMB, and it is implemented in the ops tools where necessary | * The VMI endorsement procedure is approved by OMB, and it is implemented in the ops tools where necessary | ||
Line 43: | Line 45: | ||
| Task 5.2 | | Task 5.2 | ||
| | | | ||
* Document the security requirements for the EGI Federated Cloud Service and perform a security risk analysis. | |||
* Develop new and revise old security policies to meet the needs of the EGI Federated Cloud Service and the Long Tail of Science Service. | |||
* Technical changes to the trust fabric management will be introduced for new usage scenarios and to support evolving access control mechanisms. | |||
* Develop new operational security procedures for the EGI Federated Cloud Service for incident response and vulnerability handling. | |||
| | | | ||
| | * The security requirements and security risk analysis for FedCloud will be produced and agreed/approved by the EGI FedCloud team, the OMB and the security team. | ||
| | * Policy documents will be produced, consulted on and passed all the way through to formal adoption. This will include at least a revised AUP, a revised VM Endorsement and the new LToS service policy. | ||
* The new trust fabric management will be evaluated on the new usage scenarios and access control mechanisms. | |||
* New procedures for FedCloud will be developed, approved and adopted for Incident Response and Vulnerability Handling. | |||
| David Kelsey - STFC | |||
| <br> | |||
|- | |- | ||
! 2 | ! 2 | ||
| Task 5.3 | |||
| | | | ||
| | * Enable ESA exploitation platform tasks to run on EGI Fedcloud | ||
* Enable iMarine platform to use EGI resources | |||
| | * Enable Long tail of science platform | ||
| | |||
* EGI accounting shows resource utilization by the ESA VOs | |||
* EGI accounting shows resource utilization by the iMarine VOs | |||
* EGI accounting shows resource utilization by long tail of science VO (beside testing) | |||
| Peter Solagna - EGI.eu | |||
| <br> | | <br> | ||
|- | |- |
Latest revision as of 11:34, 24 June 2015
This page is providing yearly activity plan for WP5 in PY1
Project month |
Project Tasks |
Work to be done |
Goal (measurable) |
Owner (reponsible person) |
Comments |
---|---|---|---|---|---|
1 | Task 5.1 |
|
|
Peter Solagna - EGI.eu | |
1 | Task 5.2 |
|
|
David Kelsey - STFC | |
2 | Task 5.3 |
|
|
Peter Solagna - EGI.eu | |
3 | |||||
4 | |||||
5 | |||||
6 | |||||
7 | |||||
8 | |||||
9 | |||||
10 | |||||
11 | |||||
12 |