WP3 – Representation of requirements Robert Jenkins CEO CloudSigma 1 This document produced by Members of the Helix Nebula consortium is licensed under a Creative Commons Attribution 3.0 Unported License. Permissions beyond the scope of this license may be available at The Helix Nebula project is co-funded by the European Community Seventh Framework Programme (FP7/ ) under Grant Agreement no Members of the Helix Nebula consortiumCreative Commons Attribution 3.0 Unported Licensehttp://helix-nebula.eu/

WP Objectives Establish standard structures, taxonomy, etc. for expressing functional and non-functional requirements of a federated cloud infrastructure. Specific goals Collaboration between all partners to build on flagship definitions and requirements analysis. Agree scope of operational policies within a federated environment. Provide structure for statements of requirements to be used in WP7. 2

Effort Contribution WP3: Representation of Requirements Lead Beneficiary: CloudSigma Person-Months per Participant ParticipantPerson- months CERN2.00 EMBL2.00 Atos2.00 CloudSigma9.00 Logica Germany 3.00 CNR2.00 CSA EMEA1.00 TOTAL21 PM23 PM12 PM1 WP3 3

Scientific/technical achievements and their impact Requirements definitions template used to build requirements framework for each proposed flagship Online tool developed to capture and store all info into a single spreadsheet, enabling a consolidated view of each flagship Requirements info circulated to drive planning of pilot phase deployments 4

Deliverables and Milestones – Period 1 TypeDel. no NameNatureDissemination level Date Delivered Deliverable3.1Requirements Definition TemplateReportPU11/10/2012 Deliverable3.2Consolidated User and Service Requirements Report ReportPU21/12/2012 Deliverable3.3Finalised User and Service Requirement Report ReportPU21/06/2013 Milestone7Requirement Analysis Findings (D3.1) presented at GA1 meeting ReportPU19/09/2012 5

Overall modifications, corrective actions, re-tuning of objectives Online tool designed to be easily updated to reflect current state 6

Overall modifications... Cont. Functionality of the online tool improved to support better overall results gathering Back-end repository improved to provide a more readable consolidated spreadsheet Ability to extract data in the form of graphical charts for comparative analysis which helps to identify developing trends Requirements framework expanded to include more detailed information in relation to service architecture, business and delivery models. 7

8

Key Proof of Concept Findings Server image conversion/different cloud stacks Networking aspects Legacy software requirements Automation and scaling 9

Exploitation and use of foreground Suppliers made their cloud services more flexible and accessible Compliant with the requirements gathering stage of the project Middleware adapters were developed to facilitate multi-cloud operation models and cloud-federation scenarios Further facilitation of the NO-vendor lock-in initiative Actively working to achieve seamless workload exchange between private and public cloud services 10

Contribution to the dissemination of project results HPC In the Cloud article – The Science Cloud Cometh by Robert Jenkins. Published 28 May, 2013 Cloud Expo Europe in London – January, 2013 CSA EMEA Congress in Amsterdam – September, 2012 GigaOM Structure Europe– October,