Specifying Semantic Interoperability between Heterogeneous Cloud Resources with the FCLOUDS Formal Language

Challita, Stéphanie; Zalila, Faiez; Merle, Philippe

doi:10.1109/cloud.2018.00053

Cited by 11 publications

(8 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To achieve this interoperability, the authors proposed approaches to leverage the span of IaaS solutions and approaches based on model‐driven techniques as well as vendor‐agnostic APIs . SaaS/PaaS/IaaS interoperability . This interoperability gives the clients a full control over the cloud stack from the underlying infrastructure to the platform and the deployed software.…”

Section: Research Findings and Discussionmentioning

confidence: 99%

“…We found that some of works were not implemented, others were implemented partially, other works were only simulated and their efficiency was not proven, whereas some works are specific to one delivery model and they do not consider the other models. Another category of the works is limited to the proposed technology and it does not take into consideration the heterogeneity of the cloud resources, which causes vendor lock‐in .…”

Section: Research Findings and Discussionmentioning

confidence: 99%

“…Semantic technologies facilitate the exchange and interpretation of data between services. Thus, they were widely used to achieve multicloud interoperability …”

Section: Classification Of the Cloud Service Interoperability Approachesmentioning

confidence: 99%

“…The proposed framework has a catalogue of formal models to align and formalize APIs concepts in two steps (modeling and reasoning). In addition, Challita et al defined FCLOUDS language in Reference . They formalized thirteen OCCI APIs and made them semantically interoperable using transformation rules.…”

Section: Classification Of the Cloud Service Interoperability Approachesmentioning

confidence: 99%

See 3 more Smart Citations

A survey on the service interoperability in cloud computing: Client‐centric and provider‐centric perspectives

2020

View full text Add to dashboard Cite

The vendor lock-in is a prominent issue in cloud computing. It is caused by cloud providers who offer proprietary services, which hinders the cloud interoperability. Client-centric interoperability enables the migration of the data and applications across clouds; it gives the clients control over their workloads and a wider range of service choices. Whereas, provider-centric interoperability allows the providers to collaborate. Thus, providers, who have spare resources, can lend them to other providers who lack computational or storage capabilities to overcome the limitations of their local resources. In this article, we conduct a survey to differentiate between client-and provider-centric interoperability solutions. We aim to provide an up-to-date analysis of the current tendencies and the neglected areas of the cloud interoperability field. Thus, we study the cloud service interoperability evolution through the years. Furthermore, we propose definitions for the intra-cloud and inter-cloud interoperability. Moreover, we propose a taxonomy to classify the cloud interoperability approaches into client-centric and provider-centric categories. Then, for each category, we classify the approaches based on their interoperability environment into single cloud or interconnected clouds. Finally, we analyze and compare the approaches based on multiple criteria. The study reveals the focus on the client-centric solutions and the interoperability in interconnected clouds. We notice more interest in the data and application levels interoperability, mainly, in infrastructure as a service model. We also find that client-centric solutions are, mostly, semantic technologies and brokers. However, provider-centric solutions are middleware, protocols, and standards. We conclude that a generic cloud service interoperability model is needed.

show abstract

Section: Research Findings and Discussionmentioning

confidence: 99%

Section: Research Findings and Discussionmentioning

confidence: 99%

“…Semantic technologies facilitate the exchange and interpretation of data between services. Thus, they were widely used to achieve multicloud interoperability …”

Section: Classification Of the Cloud Service Interoperability Approachesmentioning

confidence: 99%

Section: Classification Of the Cloud Service Interoperability Approachesmentioning

confidence: 99%

See 2 more Smart Citations

A survey on the service interoperability in cloud computing: Client‐centric and provider‐centric perspectives

2020

View full text Add to dashboard Cite

show abstract

“…To achieve that, we have chosen Alloy, which is a Figure 11: Projection of OCCI to EMF lightweight formal specification language based on the firstorder relational logic [43]. In a previous work, we have used Alloy to precisely define the OCCI concepts and their properties [44]. In addition, we were also able to formally analyze OCCI extensions with Alloy Analyzer, which is a solver that takes the constraints of a model and finds instances that satisfy them.…”

Section: Occiware Extension-specific Toolsmentioning

confidence: 99%

Model-driven cloud resource management with OCCIware

Zalila

Challita

Merle

2019

Future Generation Computer Systems

Self Cite

View full text Add to dashboard Cite

Cloud computing has emerged as the main paradigm for hosting and delivering computing resources as services over Internet. It provides a delivery model for computing resources at infrastructure, platform, and software levels. However, there is a plethora of cloud providers offering different resource management interfaces. Due to this diversity, the consumption, provisioning, management, and supervision of cloud resources are subjected to four key issues, i.e., heterogeneity, interoperability, integration, and portability. To cope with these issues, Open Cloud Computing Interface (OCCI) is proposed as a community-based and open recommendation standard for managing any kind of cloud resources. Currently, only runtime implementations exist for OCCI, and each one targets a specific cloud service model such as Infrastructure as a Service (IaaS), Platform as a Service (PaaS), or Software as a Service (SaaS). Thus, OCCI lacks an approach to model and execute different OCCI artifacts. Our approach provides a generic modeling framework coupled with a generic runtime implementation. In this article, we propose the OCCIware approach, which represents the first approach to design, validate, generate, implement, deploy, execute, and supervise everything as a service with OCCI. This approach provides OCCIware Studio, the first model-driven tool chain for OCCI. It is built around OCCIware Metamodel, which defines the static semantics for the OCCI standard in Ecore and OCL. In addition, it proposes OCCIware Runtime, the first generic OCCI runtime implementation targeting all the cloud service models (IaaS, PaaS, and SaaS). OCCIware provides a unique and unified framework to manage OCCI artifacts and, at the same time, it represents a factory to build cloud domain-specific modeling frameworks where each framework targets a specific cloud domain. OCCIware has been applied in various cloud domains and use-cases, which validate its applicability.• Model-Driven Managing Everything as a Service with OC-CIware. OCCIware is a model-driven vision to manage XaaS.It allows one to model any type of resources. It provides OCCI users with facilities for designing, editing, validating, generating, implementing, deploying, executing, managing, and supervising XaaS with OCCI.• Generating Cloud Domain-Specific Modeling Frameworks with OCCIware. OCCIware is a factory of cloud domainspecific modeling frameworks. Each generated Cloud Domain-Specific Modeling Studio (CDSMS) is dedicated for a particular cloud domain. Each CDSMS can be used to design configurations which conform to its related domain and hides the generic concepts of OCCI.The OCCIware approach is composed of two main components: OCCIware Studio and OCCIware Runtime. OCCIware Studio is the first model-driven tool chain for OCCI [9]. OC-CIware Studio has been built around OCCIware Metamodel. This metamodel represents a precise definition for OCCI [10]. It defines rigourously the static semantics of the OCCI Core Model [7], the core specification of OCCI, by resolving several identified...

show abstract

An Extended Framework for Semantic Interoperability in PaaS and IaaS Multi-cloud

Benhssayen,

Ettalbi

2022

Lecture Notes in Networks and Systems

View full text Add to dashboard Cite

Specifying Semantic Interoperability between Heterogeneous Cloud Resources with the FCLOUDS Formal Language

Cited by 11 publications

References 18 publications

A survey on the service interoperability in cloud computing: Client‐centric and provider‐centric perspectives

A survey on the service interoperability in cloud computing: Client‐centric and provider‐centric perspectives

Model-driven cloud resource management with OCCIware

An Extended Framework for Semantic Interoperability in PaaS and IaaS Multi-cloud

Contact Info

Product

Resources

About