This document outlines the current knowledge of the Helix Nebula Supply-side regarding the need for a structured Service Architecture. It introduces why such an architecture is needed. Within the Helix Nebula consortium, there are further supporting documents: The equivalent to this Introduction, but with much more detailed content; A document describing the Service catalogue structure for HN; A document describing the operational organisation of HN.
Helix Nebula – the Science Cloud ‐ is the catalyst for major changes in the way the European research community uses IT services, including a self‐financing Public‐Private Partnership (PPP) for cloud services. It addresses a key strategic interest for the European economy; to ensure accessible, sustainable, competitive and secure infrastructure, not only for the scientific community but throughout industry and society.
This document captures the current knowledge of the Helix Nebula Supply-side regarding the need of a federated framework to simplify discovery, access, usage and management of a federated cloud system. Alongside this objective, we aim at providing an integration framework, where current and future suppliers (i.e. cloud service providers) can easily interface their system in order to attract and receive cloud workload.
INFOaaS is subject to network effects as its value increases for each user as the number of users grows. The more data providers share data, the more complete the services will become. INFOaaS is a multisided platform ecosystem. This kind of ecosystems faces the lifecy-cle challenge of (1) fast implementation, (2) adoption, (3) scaling, and (4) competition. Those steps are applied to INFOaaS to provide a roadmap for lifecycle management.
This document captures the current knowledge of the Helix Nebula Technology and Architecture Group regarding the need of a federated framework to simplify discovery, access, usage and management of a federated cloud system. Alongside this objective, we aim at providing an integration framework, where current and future suppliers (i.e. cloud service providers) can easily interface their system in order to attract and receive cloud workload.
This deliverable specifically aims to compare the TCO of current on premise deployments at CERN with potentially outsourced on demand instances offered by the participating suppliers. Originally, the use cases of the flagships were supposed to be taken as reference to perform this exercise. Because of divergent specifications compared to the HN Market Place, which was set up in January 2014, it would not have been very beneficial. Therefore, we reached out for alternatives and identified CERN, an initial member of HN, as reference case.
This document provides a synthesis and analysis of business models for the further development of the Helix Nebula initiative resulting in seven potential business models with and without specific broker roles. Overarching and specific broker roles are required to manage the Helix Nebula ecosystem more effectively as bilateral communications cause higher risks and costs. The description of the roles and the business models follow a defined qualitative framework incorporating amongst others abstract costs, margins and risk assessment criteria.
This report will focus on the activities and outcomes of work package 3 with regard to the gathering of infrastructure and service requirements. We aim to document the learning process and summarise our findings and improvements to the process. The objective was to use the knowledge and experience of both the participating research organisations and commercial cloud service providers to develop a requirements framework that would address the technical and non-technical expectations of the demand-side and the capabilities of the supply-side.