EGI-InSPIRE:EGI-InSPIRE-PY5

Workpackages and Tasks within EGI-InSPIRE in its extension of year PY5

NA1: Management

100% EC-cofunding

Task TNA1.1: Activity Management (Catherine Gater, Project Manager, EGI.eu)

Task TNA1.2: Project and Consortium Management (project office)

Task TNA1.3: Technical Management (EGI.eu)

Task TNA1.4: Quality Assurance (EGI.eu)

NA4-PY5: Community Engagement

50%EC co-funding. Overall activity management executed in NA1

Task TNA4.1: Human Networks (NGIs coordination, NILs, Operations coordination, Operations Managers) Executed at EGI.eu

Task TNA4.2: Marketing and Communication (EGI.eu) Executed at EGI.eu

Task TNA4.3: Distributed Competence Centre (NGI experts, Technical Champions - travel, Research Champions - travel) (see DCC)

NA5-PY5: Strategy, Policy and Business Development

NGI participation 50% EC co-funding. Overall activity management executed in NA1

Task TNA5.1: Strategy, policy and business development

Task TNA5.2: Business models and proof of concepts

SA6-PY5: Federated Cloud

50% co-funding. NGI participation only. Overall activity management executed in NA1

Task TSA6.1: Operating a reliable federated institutional IaaS Cloud service
Objective: Acknowledge, and contribute to (!), the operation of institutional IaaS Cloud resources embedded in EGI's Federated Cloud Infrastructure Platform. Small contributions per partner only, since it is one of the key benefit of Cloud computing to be efficient in provisioning and operating. NGIs may use part of their funding in this task to develop small-scale integration on the site level to provide functionality that raises the otherwise site/NGI-selected and deployed Cloud Management Framework up to supporting the compulsory interfaces mandated by the federation - provided that the results and outputs are provided to the community under the EGI-InSPIRE software license (Apache 2 license, approved open source license).
For example, the VOMS integration in OpenStack, or a module for OpenStack to extract accounting information, and deliver them to the generic SSM component deployed at each site would be eligible.

Task TSA6.2: Participation in Proofs of Concept elicited by EGI
Objective: To reckognise the additional effort of participating in Proofs of Concept with new user communities and customer segments. While EGI.eu's role can be largely described as the business development body, it must rely on its partners in EGI to conduct such Proofs of Concept (in DCH-RP, these are called experiments within a PoC phase). The explicit goal of these Proofs of Concept must be at least a white paper describing how EGI can offer a professional service based on the examined tools and components in the PoC. Usually, these Proofs of Concepts originate from other projects and project collaborations, such as DCH-RP, APARSEN, SCIDIP-ES or other, or through other potential collaboration channels that lay outside of EC funded project DoWs.

SA7-PY5: Mini Projects

75% EC co-funding

JRA2-PY5: Tool Development

NGI participation 50% EC co-funding.

Task JRA2.1: Activity management

Task JRA2.1: SAM (CNRS, GRNET, SRCE)

Task JRA2.2: Accounting (STFC, CESGA)

Task JRA2.3: AppDB (GRNET)

Task JRA2.4: TMP (STFC) (to be confirmed)