Federation-Level Agreement and Integrity-Based Managed Cloud Federation Architecture

Federation-Level Agreement and Integrity-Based Managed Cloud Federation Architecture

Afifa Ghenai, Chems Eddine Nouioua
Copyright: © 2020 |Pages: 27
DOI: 10.4018/JITR.2020100107
OnDemand:
(Individual Articles)
Available
$37.50
No Current Special Offers
TOTAL SAVINGS: $37.50

Abstract

One of the biggest challenges in cloud federations is how to express the federation level agreement (FLA) and voluntary aspect of the federation members and maintain the integrity of the organization. However, existing works are not able to present the cloud federation management aspect or implement these properties that distinguish cloud federation from other inter-cloud organizations. This paper bridges this gap by proposing a managed cloud federation architecture based on this subset of properties. The key component of this architecture is the federation manager that controls, tracks, evaluates, and predicts the behavior of the federation. In order to ensure the effectiveness of the approach, the authors developed the Managed Federation Simulator to implement the proposed federation architecture on the SmartFed simulator and evaluate it through a set of scenarios on a real case study.
Article Preview
Top

1. Introduction

Cloud computing is a paradigm that has emerged and attracted particular attention in recent years. The National Institute of Standards and Technology (NIST) defines this paradigm as a model that allows access over a network in a simple way and on demand to a set of shared and configurable computer resources like networks, servers, storage, applications and services. In just over a decade, the cloud has become one of the fastest-growing IT markets with the best margins. Since it is more flexible and less expensive than traditional computing, more and more companies are using the cloud to run their applications, use online software, store or analyze their data. Customers who use “public clouds” like Amazon, Google, or Microsoft pay according to the amount of storage or power used. If the company wants to keep control of its entire system, it can create a “private cloud”, entirely customized, which will be dedicated to it alone, but will be more expensive. Indeed, Cloud improves the flexibility and agility of a company. IT resources are flexible and can be defined precisely according to the fluctuation of needs related to the activity. The implementation of new applications is fast and cheap. Several companies are outsourcing more and more parts of their global IT infrastructure to a private or public cloud. Using a cloud service is associated with a multitude of benefits; a particularly high computing power is offered by allowing delocalization of data processing and thus takes advantage of all the possibilities and performances made available to them by the cloud server. Constant monitoring of the development of resources allocated to the Cloud service and real-time information on the use of the Cloud platform are allowed. Furthermore, Cloud computing represents a very significant cost saving, it allows companies to reduce their heavy investments in hardware and software solutions especially small companies who pay only the storage space they need. As a result, cloud computing will become ubiquitous in the lives of most companies. Since Cloud usage is growing rapidly and users are becoming more demanding in terms of Quality of Service (QoS), data storage capacity on the cloud has grown exponentially. Cloud storage providers are starting to deploy more data centers with greater storage capacity and must be able to dynamically adjust their hosting capabilities in response to changing workload and QoS requirements. Cisco (Bernstein et al, 2009) proposed a solution to overcome the limitation of resources and satisfy user requirements and defined a new cloud vision called “Cloud of Clouds” by introducing the concept of “Inter-Clouds”. Cloud actors can benefit from different Inter-Cloud models that differ in initiator and degree of collaboration, among these models: Hybrid Clouds, Multi-Clouds and Cloud Federations. Many companies in fact need a “hybrid” system, combining the cost, power and flexibility of the public “cloud” and the security of the private “cloud”. Some draw from different public cloud providers: for example, Amazon for infrastructure or Google for data analysis. Several recent works (Rebai, 2017; Ferrer 2012) have suggested different inter-cloud architectures for interoperability and cooperation between clouds, providers can freely allocate their charges between separate clouds to meet requirements, while users can easily migrate their services to appropriate providers whenever needed. According to the initiator of the inter-Clouds, two use scenarios can be distinguished, Cloud federation and Multi-Cloud (Grozev et al, 2012). While resource aggregation is initiated and managed by end users in multi-cloud scenarios, Cloud federation is a heterogeneous set of interconnected clouds (Assis et al, 2016), it is referred to as provider-centric interoperability (Rebai, 2017) and the cooperation between providers is voluntary and based on previous trade agreements. Till now, the number of properties that must be present in a cloud federation is not determined. The authors in (Assis et al, 2016) consider the integrity of the environment, the Federation Level Agreement (FLA), and the voluntary aspect of federation members as the minimal subset of properties that distinguishes cloud federation from other inter-cloud organizations. However, in the literature, no cloud federation architecture presents the cloud federation management aspect or implements this minimal subset of properties.

Complete Article List

Search this Journal:
Reset
Volume 16: 1 Issue (2024): Forthcoming, Available for Pre-Order
Volume 15: 6 Issues (2022): 1 Released, 5 Forthcoming
Volume 14: 4 Issues (2021)
Volume 13: 4 Issues (2020)
Volume 12: 4 Issues (2019)
Volume 11: 4 Issues (2018)
Volume 10: 4 Issues (2017)
Volume 9: 4 Issues (2016)
Volume 8: 4 Issues (2015)
Volume 7: 4 Issues (2014)
Volume 6: 4 Issues (2013)
Volume 5: 4 Issues (2012)
Volume 4: 4 Issues (2011)
Volume 3: 4 Issues (2010)
Volume 2: 4 Issues (2009)
Volume 1: 4 Issues (2008)
View Complete Journal Contents Listing