FaaS: Federation-as-a-Service

This document is the main high-level architecture specification of the SUNFISH cloud federation solution. Its main objective is to introduce the concept of Federation-as-a-Service (FaaS) and the SUNFISH platform. FaaS is the new and innovative cloud federation service proposed by the SUNFISH project. The document defines the functionalities of FaaS, its governance and precise objectives. With respect to these objectives, the document proposes the high-level architecture of the SUNFISH platform: the software architecture that permits realising a FaaS federation. More specifically, the document describes all the components forming the platform, the offered functionalities and their high-level interactions underlying the main FaaS functionalities. The document concludes by outlining the main implementation strategies towards the actual implementation of the proposed cloud federation solution.Comment: Technical Report Edited by Francesco Paolo Schiavo, Vladimiro Sassone, Luca Nicoletti and Andrea Margher

Security and VO management capabilities in a large-scale Grid operating system

This paper presents a number of security and VO management capabilities in a large-scale distributed Grid operating system. The capabilities formed the basis of the design and implementation of a number of security and VO management services in the system. The main aim of the paper is to provide some idea of the various functionality cases that need to be considered when designing similar large-scale systems in the future

Infrastructural Sovereignty over Agreement and Transaction Data (‘Metadata’) in an Open Network-Model for Multilateral Sharing of Sensitive Data

Organizations are becoming ever more aware that their data is a valuable asset requiring protection against mis-use. Therefore, being in control over the usage conditions (i.e. data sovereignty) is a prerequisite for sharing sensitive data in (increasingly complex) supply chains. Maintaining sovereignty applies to both the primary shared data and to the ‘metadata’ stemming from the data sharing support processes. However, maintaining sovereignty over this metadata creates an area of tension. Data providers must balance operational efficiency through outsourcing the data sharing support processes and the associated metadata to external, trusted, organizations against the added risk of transferring control over the metadata. At the same time, lock-in by community providers and major integration efforts due to multiple data sharing relationships need to be avoided. To address these issues, this paper elaborates an open network-model approach for maintaining sovereignty over metadata

Continuous QoS-compliant Orchestration in the Cloud-Edge Continuum

The problem of managing multi-service applications on top of Cloud-Edge networks in a QoS-aware manner has been thoroughly studied in recent years from a decision-making perspective. However, only a few studies addressed the problem of actively enforcing such decisions while orchestrating multi-service applications and considering infrastructure and application variations. In this article, we propose a next-gen orchestrator prototype based on Docker to achieve the continuous and QoS-compliant management of multiservice applications on top of geographically distributed Cloud-Edge resources, in continuity with CI/CD pipelines and infrastructure monitoring tools. Finally, we assess our proposal over a geographically distributed testbed across Italy.Comment: 25 pages, 8 figure

Towards an aspect weaving BPEL engine

This position paper proposes the use of dynamic aspects and the visitor design pattern to obtain a highly configurable and extensible BPEL engine. Using these two techniques, the core of this infrastructural software can be customised to meet new requirements and add features such as debugging, execution monitoring, or changing to another Web Service selection policy. Additionally, it can easily be extended to cope with customer-specific BPEL extensions. We propose the use of dynamic aspects not only on the engine itself but also on the workflow in order to tackle the problems of Web Service hot deployment and hot fixes to long running processes. In this way, composing aWeb Service "on-the-fly" means weaving its choreography interface into the workflow