Cloud Infrastructure Management Interface

Last updated
Cloud Infrastructure Management Interface
AbbreviationCIMI
StatusPublished
Year started2010;12 years ago (2010)
Latest version1.1
October 2013;8 years ago (2013-10)
Organization Distributed Management Task Force
Related standards Open Virtualisation Format (OVF)
Domain Cloud computing
Website www.dmtf.org/standards/cmwg

Cloud Infrastructure Management Interface (CIMI) is an open standard API specification for managing cloud infrastructure.

Contents

CIMI's goal is to enable users to manage a cloud infrastructure in a simple way by standardizing interactions between cloud environments to achieve interoperable cloud infrastructure management between service providers and their consumers and developers.

CIMI 1.1 was registered as an International Standard in August 2014 by the Joint Technical Committee 1 (JTC 1) of the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC). [1]

Overview

The CIMI standard is defined and published by the Distributed Management Task Force (DMTF). It includes the Cloud Infrastructure Management Interface (CIMI) Model and RESTful HTTP-based Protocol specification, [2] the CIMI XML Schema, the CIMI Primer and the CIMI Uses Cases whitepaper: [3]

The Cloud Infrastructure Management Interface (CIMI) Model and RESTful HTTP-based Protocol Specification define the architecture and concepts of CIMI.
The CIMI XML Schema defines the XML representation of the CIMI model.
The CIMI Primer explains how clients can use the CIMI API for some common use cases, such as listing Machine Images and Configurations, creating a Machine from a Template and then retrieving details about it.
The CIMI Use Cases whitepaper collects a number of use cases that typify the next generation of issues facing IaaS providers and that are being considered to be addressed in the next version of the CIMI specification, such as Business Continuity/Disaster Recovery, Service Level Objective Management, Log / Metadata Management and Multicloud Management.

Goals

CIMI aims to provide a single set of interfaces that a cloud consumer can use to provision and manage their cloud infrastructure in multiple clouds, so client code does not need to be adapted to each of the proprietary interfaces from these multiple vendors. CIMI has been described as a de jure standard that is under change control of a standards body, contrasting it to a de facto standard where typically one vendor has change control over the interface, and everyone else has to reverse engineer the inner workings of it. [4] It is expecting vendors to embrace a dual strategy of delivering two offerings – one a CIMI compliant offering and the second a more proprietary offering that allows for more proprietary functionality. [5]

Scope

CIMI is scoped to the core IaaS functionality such as deploying and managing Machines, Volumes, Networks, Monitoring, and Systems that group them. It includes a feature discovery mechanism to find out what functions the cloud provider supports, including the metadata describing capabilities and resource constraints. [6]

Model and Features

Model

The CIMI model describes in detail all the resources that are accessible by the Cloud Consumer and that are maintained by the Cloud Provider, and their relationships.

The main entry point for the CIMI Consumer is the IaaS Provider's Cloud Entry Point. All other data is discovered, iteratively: [7]

The model is self-describing and allows for querying its own metadata, e.g., to discover which extensions have been implemented. The model is also extensible by the Consumer and the Provider. [3]

The model also defines serializations both in XML and JSON for each resource.

Features

CIMI addresses the management of the lifecycle of infrastructure provided by an IaaS Provider, such as the creation, deletion, viewing and alteration of virtual machines, networks and storage, and start and stop operations. It also defines resource operations such as creating machine images or snapshots of machines for backup & restore, or for the creation of additional identical virtual machines.

CIMI allows the import of an OVF package to create a System with Machines and other CIMI resources, as well as the export of a CIMI System of resources to an OVF package. [8] The actual import and export of OVF packages are handled by the underlying hypervisor under the management of the CIMI implementation.

Protocols

CIMI currently supports the REST architectural style using HTTP for all interactions between the Consumer and the Providers. Mappings to SOAP and WS-MAN are also considered. [3]

This protocol binding follows REST principles and describes the mapping of HTTP protocol verbs to operations on the model: Each request is sent by using an HTTP verb such as GET, POST, PUT and DELETE, and includes a message body in either JSON or XML format. Each response uses a standard HTTP status code, whose semantics are interpreted in the context of the particular request that was made.

Implementations

Several adapters have been developed that expose a CIMI API endpoint for client applications to consume and translate API calls to the proprietary API calls of supported target cloud provider(s).

The following is a list of CIMI implementations:

The CIMI Working Group has announced plug-fests for improved interoperability between CIMI implementations. [11]

See also

Related Research Articles

A web service (WS) is either:

Distributed Management Task Force Organization

Distributed Management Task Force (DMTF) is a 501(c)(6) nonprofit industry standards organization that creates open manageability standards spanning diverse emerging and traditional IT infrastructures including cloud, virtualization, network, servers and storage. Member companies and alliance partners collaborate on standards to improve interoperable management of information technologies.

Message-oriented middleware (MOM) is software or hardware infrastructure supporting sending and receiving messages between distributed systems. MOM allows application modules to be distributed over heterogeneous platforms and reduces the complexity of developing applications that span multiple operating systems and network protocols. The middleware creates a distributed communications layer that insulates the application developer from the details of the various operating systems and network interfaces. APIs that extend across diverse platforms and networks are typically provided by MOM.

In software engineering, service-oriented architecture (SOA) is an architectural style that supports service orientation. By consequence, it is as well applied in the field of software design where services are provided to the other components by application components, through a communication protocol over a network. A service is a discrete unit of functionality that can be accessed remotely and acted upon and updated independently, such as retrieving a credit card statement online. SOA is also intended to be independent of vendors, products and technologies.

Representational state transfer (REST) is a software architectural style that describes a uniform interface between decoupled components in the Internet in a Client-Server architecture. REST defines four interface constraints:

Web Services Discovery provides access to software systems over the Internet using standard protocols. In the most basic scenario there is a Web Service Provider that publishes a service and a Web Service Consumer that uses this service. Web Service Discovery is the process of finding suitable web services for a given task.

In computing, Web-Based Enterprise Management (WBEM) comprises a set of systems-management technologies developed to unify the management of distributed computing environments. The WBEM initiative, initially sponsored in 1996 by BMC Software, Cisco Systems, Compaq Computer, Intel, and Microsoft, is now widely adopted. WBEM is based on Internet standards and Distributed Management Task Force (DMTF) open standards:

A web API is an application programming interface for either a web server or a web browser. It is a web development concept, usually limited to a web application's client-side, and thus usually does not include web server or browser implementation details such as SAPIs or APIs unless publicly accessible by a remote web application.

The Clinical Data Interchange Standards Consortium (CDISC) is a standards developing organization (SDO) dealing with medical research data linked with healthcare, to "enable information system interoperability to improve medical research and related areas of healthcare". The standards support medical research from protocol through analysis and reporting of results and have been shown to decrease resources needed by 60% overall and 70–90% in the start-up stages when they are implemented at the beginning of the research process.

The Common Information Model (CIM) is an open standard that defines how managed elements in an IT environment are represented as a common set of objects and relationships between them.

Open Cloud Computing Interface Open protocol for cloud computing

The Open Cloud Computing Interface (OCCI) is a set of specifications delivered through the Open Grid Forum, for cloud computing service providers. OCCI has a set of implementations that act as proofs of concept. It builds upon World Wide Web fundamentals by using the Representational State Transfer (REST) approach for interacting with services.

In computing, Open Data Protocol (OData) is an open protocol that allows the creation and consumption of queryable and interoperable REST APIs in a simple and standard way. Microsoft initiated OData in 2007. Versions 1.0, 2.0, and 3.0 are released under the Microsoft Open Specification Promise. Version 4.0 was standardized at OASIS, with a release in March 2014. In April 2015 OASIS submitted OData v4 and OData JSON Format v4 to ISO/IEC JTC 1 for approval as an international standard. In December 2016, ISO/IEC published OData 4.0 Core as ISO/IEC 20802-1:2016 and the OData JSON Format as ISO/IEC 20802-2:2016.

IBM cloud computing is a set of cloud computing services for business offered by the information technology company IBM. IBM Cloud includes infrastructure as a service (IaaS), software as a service (SaaS) and platform as a service (PaaS) offered through public, private and hybrid cloud delivery models, in addition to the components that make up those clouds.

FUJITSU Cloud IaaS Trusted Public S5 Cloud computing platform

FUJITSU Cloud IaaS Trusted Public S5 is a Fujitsu cloud computing platform that aims to deliver standardized enterprise-class public cloud services globally. It offers Infrastructure-as-a-Service (IaaS) from Fujitsu's data centres to provide computing resources that can be employed on-demand and suited to customers' needs. The service ensures a high level of reliability that is sufficient for deployment in mission-critical systems.

The Sensor Observation Service (SOS) is a web service to query real-time sensor data and sensor data time series and is part of the Sensor Web. The offered sensor data consists of data directly from the sensors, which are encoded in the Sensor Model Language (SensorML), and the measured values in the Observations and Measurements encoding format. The web service as well as both file formats are open standards and specifications of the same name defined by the Open Geospatial Consortium (OGC).

The Physical Security Interoperability Alliance (PSIA) is a global consortium of more than 65 physical security manufacturers and systems integrators focused on promoting interoperability of IP-enabled security devices and systems across the physical security ecosystem as well as enterprise and building automation systems.

Cloud Application Management for Platforms

Cloud Application Management for Platforms (CAMP) is a specification for managing applications in the context of a platform as a service (PaaS) system. CAMP is designed to address the needs of a high-level PaaS system; one in which the consumer provides application artifacts and specifies which provider-supplied services are required to realize these artifacts as an application. The details of the infrastructure used to support these services are hidden from the consumer by the provider of the PaaS system.

The SAML metadata standard belongs to the family of XML-based standards known as the Security Assertion Markup Language (SAML) published by OASIS in 2005. A SAML metadata document describes a SAML deployment such as a SAML identity provider or a SAML service provider. Deployments share metadata to establish a baseline of trust and interoperability.

The Redfish standard is a suite of specifications that deliver an industry standard protocol providing a RESTful interface for the management of servers, storage, networking, and converged infrastructure.

References

  1. ↑ "ISO/IEC 19831 - Cloud Infrastructure Management Interface (CIMI) Model and RESTful HTTP-based Protocol". ISO Standards Catalogue. Retrieved 2015-01-06.
  2. ↑ Yasin, Rutrell (2012-08-29). "DMTF spec simplifies cloud management". GCN. Retrieved 2014-11-02.
  3. 1 2 3 Waschke, Marvin (2013-10-17). Cloud Standards: Agreements That Hold Together Clouds. Apress. pp. 291–303. ISBN   9781430241102.
  4. ↑ Carlson, Mark (2012-08-29). "Cloud Infrastructure has a new standard". Archived from the original on 2013-12-11. Retrieved 2014-10-30.
  5. ↑ Kepes, Ben (2012-09-07). "DMTF's Cloud Infrastructure Standard" . Retrieved 2014-10-30.
  6. ↑ Norfolk, David (2012-09-20). "The DMTF's Cloud Infrastructure Management Interface (CIMI), a new cloud infrastructure management standard". Bloor. Retrieved 2014-10-30.
  7. ↑ "Cloud Infrastructure Management Interface (CIMI) and Open Cloud Computing Interface (OCCI)". The Cloud Standards Observatory. 2013. Archived from the original on 2014-05-18. Retrieved 2014-11-02.
  8. ↑ Bumpus, Winston (2013-02-01). "The Open Cloud: Management Standards Achieve Interoperability". HPC Wire. Retrieved 2014-11-07.
  9. ↑ Bist, M.; Wariya, M.; Agarwal, A. (2013). Comparing delta, open stack and Xen Cloud Platforms: A survey on open source IaaS. Advance Computing Conference (IACC), 2013 IEEE 3rd International. Ghaziabad: IEEE. pp. 96–100. doi:10.1109/IAdCC.2013.6514201. ISBN   978-1-4673-4527-9.
  10. ↑ "Infrastructure as a service cloud development". IBM . 2013-01-30. Retrieved 2014-10-30.
  11. ↑ Chawki, Jamil (2012-11-05). "la nouvelle norme de gestion IaaS : CIMI" [the new IaaS management standard: CIMI] (in French). Retrieved 2014-10-30.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.