Comparison and Runtime Adaptation of Cloud Application Topologies based on OCCI

Erbel, Johannes; Korte, Fabian; Grabowski, Jens

doi:10.5220/0006774405170525

Cited by 10 publications

(8 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…According to the OGF, "OCCI is a Protocol and API for all kinds of Management tasks. It was originally initiated to create a remote management API for IaaS model based services, allowing for the development of interoperable tools for common tasks including deployment, autonomic scaling and monitoring" 11 . The OCCI specification comprises several parts: OCCI Core model, OCCI Extensions, OCCI Renderings and OCCI Protocols.…”

Section: Occimentioning

confidence: 99%

“…Based on the modeled TOSCA topology, an OCCI Platform Independent Model (PIM) is generated, i.e., a (PIM) OC-CIware Configuration. The resulting configuration, containing the modeled TOSCA resources as OCCI elements, then serves as input for the OCCI Orchestration process initially described in [11]. In general, the concept resembles a models@run.time approach [5] which derives imperative steps from a declarative description in order to adapt the running system.…”

Section: Model-driven Cloud Orchestrationmentioning

confidence: 99%

“…Thereafter, the process extracts the current cloud deployment in form of an OCCI Runtime Configuration, and compares it to the desired cloud deployment. Based on this comparison a M2M is triggered generating a Provisioning and Deployment Plan (see e.g., [11], [6] or [20] for automatic deployment and provisioning workflow generation). Within this plan the OCCI requests required to manage cloud resources are sequenced in order to bring the cloud resources into the desired state.…”

Section: Model-driven Cloud Orchestrationmentioning

confidence: 99%

“…An implementation of the orchestration process is publicly available 25 . While the presented concept can be generally applied on any kind of OCCI API, such as the OpenStack OCCI Interface (OOI) used in [11], the implementation got enhanced to focus on the OCCI API provided by the OC-CIware Runtime 26 . The OCCIware Runtime is a server that maintains a runtime model of the currently deployed cloud system which is utilized by the orchestrator.…”

Section: Occi Orchestratormentioning

confidence: 99%

“…After the transformation, the current cloud deployment is extracted in form of an OCCI model from the OCCIware runtime. Based on the current and desired topology, a provisioning plan is generated [11] that sequences the OCCI requests required to provision and deploy the depicted model. Hereby, the requests are sequenced in such a manner that each Resource is provisioned first, i.e., Compute, Network, Application, and Component.…”

Section: Orchestrationmentioning

confidence: 99%

See 4 more Smart Citations

Model-Based Cloud Resource Management with TOSCA and OCCI

Challita¹,

Korte²,

Erbel³

et al. 2020

Preprint

Self Cite

View full text Add to dashboard Cite

With the advent of cloud computing, different cloud providers with heterogeneous cloud services (compute, storage, network, applications, etc.) and their related Application Programming Interfaces (APIs) have emerged. This heterogeneity complicates the implementation of an interoperable cloud system. Several standards have been proposed to address this challenge and provide a unified interface to cloud resources. The Open Cloud Computing Interface (OCCI) thereby focuses on the standardization of a common API for Infrastructureas-a-Service (IaaS) providers while the Topology and Orchestration Specification for Cloud Applications (TOSCA) focuses on the standardization of a template language to enable the proper definition of the topology of cloud applications and their orchestrations on top of a cloud system. TOSCA thereby does not define how the application topologies are created on the cloud. Therefore, we analyse the conceptual similarities between the two approaches and we study how we can integrate them to obtain a complete standard-based approach to manage both Cloud Infrastructure and Cloud application layers. We propose an automated extensive mapping between the concepts of the two standards and we provide TOSCA Studio, a model-driven tool chain for TOSCA that conforms to OCCI. TOSCA Studio allows to graphically design cloud applications as well as to deploy and manage them at runtime using a fully

show abstract

Section: Occimentioning

confidence: 99%

Section: Model-driven Cloud Orchestrationmentioning

confidence: 99%