3    Terms

For the purposes of this document, the following terms and definitions apply.

3.1   

Access Control List

ACL

a persistent list, commonly composed of Access Control Entries (ACEs), that enumerates the rights of principals (users and groups) to access resources

3.2   

CDMI™

Cloud Data Management Interface

3.3   

CIFS

Common Internet File System

3.4   

cloud storage

see Data storage as a Service

3.5   

CRC

cyclic redundancy check

3.6   

CRUD

create, retrieve, update, delete

3.7   

Data storage as a Service

DaaS

delivery of virtualized storage and data services on demand over a network, based on a request for a given service level that hides limits to scalability, is either self-provisioned or provisionless, and is billed based on consumption

3.8   

domain

a shared user authorization database that contains users, groups, and their security policies and associated accounting information

Note:   Each CDMI object belongs to a single domain, and each domain provides user mapping and accounting information.

3.9   eventual consistency

a behavior of transactional systems that does not provide immediate consistency guarantees to provide enhanced system availability and tolerance to network partitioning

3.10   

HTTP

HyperText Transfer Protocol

3.11   

Infrastructure as a Service

IaaS

delivery over a network of an appropriately configured virtual computing environment, based on a request for a given service level

Note:   Typically, IaaS is either self-provisioned or provisionless and is billed based on consumption.

3.12   

iSCSI

Internet Small Computer Systems Interface (see RFC 3720)

3.13   

LUN

Logical Unit Number (see ISO/IEC 14776-414)

3.14   

MIME

Multipurpose Internet Mail Extensions (see RFC 2045)

3.15   

NFS

Network File System (see RFC 3530)

3.16   

object

an entity that has an object ID, a unique URI, and contains state

Note:   Types of CDMI objects include data objects, containers, capabilities, domains, and queues.

3.17   

object identifier

a globally-unique value assigned at creation time to identify an object

3.18   

OCCI

Open Cloud Computing Interface (see OCCI specification)

3.19   

Platform as a Service

PaaS

delivery over a network of a virtualized programming environment, consisting of an application deployment stack based on a virtual computing environment

Note:   Typically, PaaS is based on IaaS, is either self-provisioned or provisionless, and is billed based on consumption.

3.20   

POSIX

Portable Operating System Interface (see IEEE Std 1003.1)

3.21   

private cloud

delivery of SaaS, PaaS, IaaS, and/or DaaS to a restricted set of customers, usually within a single organization

Note:   Private clouds are created due to issues of trust.

3.22   

public cloud

delivery of SaaS, PaaS, IaaS, and/or DaaS to, in principle, a relatively unrestricted set of customers

3.23   

Representational State Transfer

REST

specific set of principles for defining, addressing, and interacting with resources addressable by URIs (see REST thesis)

3.24   

RPO

recovery point objective

3.25   

RTO

recovery time objective

3.26   

service level

performance targets for a service

3.27   

Software as a Service

SaaS

delivery over a network, on demand, of the use of an application

3.28   thin provisioning

technology that allocates the physical capacity of a volume or file system as applications write data, rather than pre-allocating all the physical capacity at the time of provisioning

3.29   

Uniform Resource Identifier

URI

compact sequence of characters that identifies an abstract or physical resource (see RFC 3986)

3.30   

virtualization

presentation of resources as if they are physical, when in fact, they are decoupled from the underlying physical resources

3.31   

WebDAV

Web Distributed Authoring and Versioning (see RFC 4918)

3.32   

XAM

eXtensible Access Method (see INCITS 464-2010)