INDIGO – DataCloud WP5 introduction INFN-Bari CYFRONET RIA

WP5 session agenda  WP5 Highlights  Most critical issues  Timeline and Deadline  Partner experience and interest  Next steps and …  … how we can proceed 2 INDIGO-DataCloud RIA

WP5: PaaS Platform Development 3 INDIGO-DataCloud RIA

WP5: PaaS Platform Development 4  PaaS architecture and implementation  Design and implementation of a PaaS layer allowing scientific communities to exploit, in a powerful and high-level way, several heterogeneous computing and data e-infrastructure such as: IaaS Cloud, Helix Nebula, EGI Grid, EGI Federated Cloud, PRACE, HPC, EUDAT, etc. It will be possible to process large amounts of data and to exploit the efficient storage and preservation technologies and infrastructure already available in the European e-infrastructure, with the appropriate mechanisms to ensure security and privacy.  Implementation of an advanced PaaS Layer providing the following features:  Transparency  Error management  Elasticity/SLA management. Task: 5.1 Partner involved: Lead Partner: UPV [30 PMs] Contributors: INFN [25 PMs], CISC [15 PMs], CERN [10 PMs], STFC [15 PMs], T-System [20 PMs], ATOS [20 PMs], INDRA [15 PMs], Reply [35 PMs] Task Leader: Ignacio Blanquer INDIGO-DataCloud RIA

WP5: PaaS Platform Development 5  Security and Authorization  Will focus on authorization issues in distributed, multi-tenant cloud infrastructures, leveraging and integrating with standard and already available authentication technologies (e.g., X.509, SAML2, OpenID- Connect).  user identities, enrollment and attribute management (e.g., group membership management, role assignment);  access policy definition, distribution and composition;  controlled privilege delegation;  credential translation. Task: 5.2 Partner involved: Lead Partner: INFN [51 PMs]; deputy: CESNET [13 PMs] Contributors: CSIC [15 PMs], KIT [11 PMs], CERN [10 PMs] Task Leader: Andrea Ceccanti INDIGO-DataCloud RIA

WP5: PaaS Platform Development 6  High-level geographical application/service deployment  will implement a solution, Geo-deployment Service, to deploy in a transparent and powerful way both services and applications in a distributed and heterogeneous environment made by several different infrastructures (EGI Grid, EGI Fed Cloud, IaaS Cloud, Helix Nebula, PRACE, local HPC clusters, etc).  well beyond the simple scheduling of the application over grid or cloud environments because it will provide the capabilities to deploy a wide range of diverse applications and services with a powerful set of APIs that hide the complexity of the underlying infrastructures Task: 5.3 Partner involved: Lead Partner: INFN [35 PMs] Contributors: IBCH PAS [6 PMs], AGH/AGH-UST [30 PMs], UPV [15 PMs], T-Systems [10 PMs], ATOS [10 PMs], INDRA [15 PMs], Reply [10 PMs]. Task Leader: Giacinto Donvito INDIGO-DataCloud RIA

WP5: PaaS Platform Development 7  Unified Data Access  Unification  Federated data access  Interoperability and Open Data  Optimization and Data on the fly Task: 5.4 Partner involved: Lead Partner: AGH/AGH-UST [60PM]; deputy: DESY [30PM] Contributors: INFN [25PM], IBCH PAS [14PM], INAF [15PM] Task Leader: Lukasz Dutka INDIGO-DataCloud RIA

WP5: PaaS Platform Development criticalities 8  There are at least three “tasks” that has a quite big impact also on the others WPs  PaaS core  AAI  Storage access  For this reason we have separate session for them INDIGO-DataCloud RIA

WP5: Tasks 9  Task T5.1: PaaS architecture and implementation  Subtask T5.1.1 [M1-M4] (July 2015): Analysis and state of the art of PaaS technologies  This task will perform the analysis of the technologies, standards and requirements from the community to implement the PaaS layer. This task will end up with deliverable D5.1 (M5.1) comprising the analysis of the available technologies, focusing on the features needed by the INDIGO community, finally enabling to select them in the design of the PaaS architecture.  Subtask T5.1.2 [M3-M6] (Sept 2015): Design of the PaaS Architecture  This task has to define the components to be used, the global PaaS architecture, the interface with the upper (WP6) and lower (WP4) layers, the unit tests, and the evaluation metrics. This task will end up with the deliverable D5.2 (M5.2) comprising the first comprehensive design of the PaaS layer and the concrete metrics to evaluate it. INDIGO-DataCloud RIA

WP5: Tasks 10  Task T5.2: Security and Authorization  Subtask T5.2.1 [M1-M6] (Sept 2015): Requirements analysis and IAM services design  This task will focus on groundwork activities, such as the definition of supported federated authentication mechanisms, the definition of the privilege delegation mechanism and the structure of the security token (working in close collaboration with WP4 and WP6).  The IAM service functionalities and APIs will also be defined (user and attribute management, policy authoring and distribution functionalities, attribute authority and credential translation services). This task will also perform an evaluation of existing technologies to use as the basis of the IAM services implementation. The results of this task will be the design of the IAM services which will be described in deliverable D5.1 and D5.2. (M5.1, M5.2). INDIGO-DataCloud RIA

WP5: Tasks 11  Task T5.3: High-level geographical application/service deployment  Subtask T5.3.1 [M1-M5] (Aug 2015): Requirements of application scheduling algorithms  This subtask will provide a report of current technologies with their application areas, functionalities, supported protocols and so on. Thanks to this scouting activity, we will be able to define the solutions to be adopted, the strategy to integrate them and the novel features to develop according to project requirements. The results of this task will be part of the Milestone M5.1.  Subtask T5.3.2 [M1-M6] (Sept 2015): Definition of the Geo-deployment Service architecture  Geographical scheduling, deployment and execution of Service/Application represent the main functionalities of the service proposed in T5.3, since they have to ensure the optimized execution of all the tasks required by an INDIGO-DataCloud RIA

WP5: Tasks 12  Task T5.4: Unified Data Access  Subtask T5.4.1 [M1-M5] (Aug 2015): Requirements and Plans for Unified Data Access  This task will overview the state of the art of technologies used for unification of data access. The available technology will be evaluated on the basis of the requirements coming from user-communities. As a result, a selection of technology used for development UDA will be made as input to deliverable D5.1 (M5.1).  Subtask T5.4.2 [M3-M6] (Sept 2015): Initial design and provisioning of Unified Data Access  This task will be involved in preparation of the initial architecture of Unified Data Access subsystem. As a result, a design of the set of components and their architecture, initial set of interfaces, set of dependencies to components developed by other work packages will be provided. It will make input to deliverable D5.2 (M5.2). INDIGO-DataCloud RIA

WP5: Milestones and Deliverable 13  D5.1, Month 5 (R, PU) (Aug 2015): State of the art for the technologies at the base of PaaS architecture [UPV]  Provide an overview of the state of the art technologies used as base for the PaaS architecture. The technologies will be evaluated on the bases of the requirements coming from user-communities and on the requirement analysis from WP2 and WP6.  D5.2, Month 6 (R, PU) (Sept 2015): Design Document and work plan for the PaaS architecture [Cyfronet|INFN]  This deliverable contains the detailed design document and the resulting work plan of the technical area, compliant with the overall Technical Development Plan including WP4 and WP6. INDIGO-DataCloud RIA

WP5: Task, milestones and Deliverable 14  M5.1 [Month 5] (Aug 2015): PaaS layer available-technology evaluated and building blocks selected.  M5.2 [Month 6] (Sept 2015): Architecture of the PaaS layer designed and documented.  D1.6 Month 6 (R, PU) (Sept 2015): General Architecture [INFN]  This deliverable will describe the general architecture of INDIGO produced by the collaborative work of WP4, WP5 and WP6. WP1 oversees the Technical Board of the project (see governance section) and therefore takes the responsibility of delivering the General Architecture deliverable on behalf of all the JRA work packages. INDIGO-DataCloud RIA