From EGIWiki
(Redirected from EGI-InSPIRE-PY5)
Jump to: navigation, search
EGI Inspire Main page

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

NA1: Management

WP Manager: Y. Legre

100% EC-cofunding

Task TNA1.1: Activity Management (Y. Legre, Project Manager,

Task TNA1.2: Project and Consortium Management (Celine Bitoune,

Task TNA1.3: Technical Management (Tiziana Ferrari,

Task TNA1.4: Quality Assurance (J. Jimenez,

NA4-PY5: Community Engagement

WP manager: G. Sipos,

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

Task TNA4.1: Human Networks coordination (NILs, Operations Managers, Distributed Competence Centre coordination, VT coordination) G. Sipos,

Task TNA4.2: Communication Task leader: Sara Coelho, Executed at

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

NA5-PY5: Strategy, Policy and Business Development

WP manager: Sergio Andreozzi,

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

Task TNA5.1: Strategy, policy and business development
Task leader: S. Andreozzi,

The goal of this task is to support EGI to transform and grow its service offering and related business development activities in line with the customers needs and stakeholders shared vision. This task will work in collaboration with other tasks and work packages to understand the evolving needs of the user communities, to define and improve the business processes around the product lifecycle and service management, to outline the value proposition and ensure that effective messages are delivered to the current/potential user communities and to the funding agencies. EGI’s ecosystem comprises many stakeholders including funders, resource providers, technology providers, users of the infrastructure, related projects that needed to be integrated together through defined policies and collaborations. Many requirements coming from user communities are also pushing an increasing reliance on other infrastructures and organisations in order to meet user satisfaction, therefore a focus will also be on solidifying business and collaborative relationships with other projects and organisations, including industry and international policy bodies to support EGI’s sustainability efforts. Innovative business models will be explored to ensure a sustainable future for both EGI and This activity will be supported by running proof of concepts in collaboration with NGIs as described in TNA5.2.

Task TNA5.2: Business models and proof of concepts
Task leader: Sy Holsinger,

In early 2013, the EGI Council approved a policy to explore business models for pay-for-use service delivery to couple together with the traditional method of free-at-point-of-use. The goal of this task is to support the implementation of this policy in collaboration with NGIs through the definition and execution of proof of concepts. Activities will include: articulation of appropriate business and responsibility models, definition of prices for services from the participating sites, definition of agreements and service management processes and procedures, introduction of a billing function, analysis of the changes needed to support services and roll out the new functionalities in the production environment, and evaluation of legal, policy, and organisational issues around the full implementation of the pay-for-use model. The output of this task will be documented in the final periodic report. This activity will be closely linked to TNA5.1 Strategy, Policy and Business Development; SA5.2: Federated Cloud and JRA1 Accounting (including billing).

SA5-PY5: Federated Cloud

WP Manager: D. Wallom, Uni Oxford

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

Task TSA5.1: Operating a reliable federated institutional IaaS Cloud service
Task leader: M. Krakowian,

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 TSA5.2: Participation in Proofs of Concept elicited by EGI
Task leader: G. Sipos,

Objective: To reckognise the additional effort of participating in Proofs of Concept with new user communities and customer segments. While'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.

JRA2-PY5: Tool Development

WP Manager: Diego Scardaci, INFN

NGI participation 50% EC co-funding.

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

Task JRA2.2: Accounting (STFC, CESGA) S. Pullinger/STFC

Task JRA2.3: AppDB M. Chatziangelou/IASA

Task JRA2.4: e-GRANT T. Szepieniec/CYFRONET

  • integration with cloud resources
  • SLA follow-up (reports, connection with open-science records, acknowledgments in publications).
  • support of integration with other e-infrastructures (if needed..)