Difference between revisions of "EGI-Engage:PY2 review"
Jump to navigation
Jump to search
(→WP4) |
(→WP4) |
||
Line 22: | Line 22: | ||
* (JRA2.3) CANFAR integration ready to accept credentials from Europe and Canada, VOSpace prototype available. | * (JRA2.3) CANFAR integration ready to accept credentials from Europe and Canada, VOSpace prototype available. | ||
* (JRA2.3) EGI/EUDAT use cases showing the combined use of both infrastructures started and first pilots deployed. | * (JRA2.3) EGI/EUDAT use cases showing the combined use of both infrastructures started and first pilots deployed. | ||
* (JRA2.4) Establish GPGPU specific VO acc-comp.egi.eu for accelerated computing, create VO-specific image list with pre-installed GPGPU software | |||
* (JRA2.4) Support for GPGPU on OpenNebula (site deployment and certification, upgrade of rOCCI server to support GPGPU in resource template) | |||
* (JRA2.4) Deployment and experimentation with support GPGPU via nova-lxd (LXC container instead of KVM hypervisor) | |||
= WP5 = | = WP5 = |
Revision as of 13:14, 23 February 2017
WP1
WP2
WP3
WP4
- (JRA2.2) OCCI 1.2 released for OpenStack and OpenNebula, including support for snapshots and resizing of images.
- (JRA2.2) Design and first implementation of new image distribution method, providing better integration with CMFs.
- (JRA2.3) gCube/D4Science integrated into the EGI Federated Cloud, enabling the use of EGI resources for users of the VREs
- (JRA2.3) CANFAR integration ready to accept credentials from Europe and Canada, VOSpace prototype available.
- (JRA2.3) EGI/EUDAT use cases showing the combined use of both infrastructures started and first pilots deployed.
- (JRA2.4) Establish GPGPU specific VO acc-comp.egi.eu for accelerated computing, create VO-specific image list with pre-installed GPGPU software
- (JRA2.4) Support for GPGPU on OpenNebula (site deployment and certification, upgrade of rOCCI server to support GPGPU in resource template)
- (JRA2.4) Deployment and experimentation with support GPGPU via nova-lxd (LXC container instead of KVM hypervisor)
WP5
WP6