Content deleted Content added
Rescuing 1 sources and tagging 0 as dead. #IABot (v2.0beta15) |
m v2.05b - Bot T20 CW#61 - Fix errors for CW project (Reference before punctuation) |
||
| (9 intermediate revisions by 7 users not shown) | |||
Line 1:
{{Short description|Cloud storage standard}}
{{Single source|date=May 2019}}
{{Infobox standardref
Line 4 ⟶ 5:
| status = Published
| year_started = 2009
| version =
| organization = [[
| base_standards = [[Hypertext Transfer Protocol]]
| related_standards = [[Network File System]]
Line 11 ⟶ 12:
| ___domain = [[Cloud computing]]
| license =
| website = {{url|https://www.
}}
CDMI defines new resource representations<ref>{{cite web|title=Cloud Data Management Interface (CDMI) Media Types|url=https://datatracker.ietf.org/doc/html/rfc6208|publisher=IETF|accessdate=17 September 2024}}</ref> to enable standardized management of any [[URI]]-accessible data, and defines [[REST]]ful [[HTTP]] operations using these representations to discover the capabilities of the storage system, discover stored data, access and update management metadata, specify data storage protocols (such as [[iSCSI]] and [[Network File System (protocol)|NFS]]) through which the stored data is accessed, and provide cross-system and cross-cloud import and export in order to enable [[data portability]].
Management functions enabled by CDMI include managing data ownership, identity mapping, access controls, user-specified metadata, and to declaratively specify desired data protection, [[data retention]], constraints on geographic placement, desired [[quality of service]], data versioning and security requirements.
CDMI also defines utility services to facilitate data management, such the ability to query data matching specific criteria, and includes extensions<ref>{{cite web|title=Draft CDMI Extensions and Profiles|url=https://www.snia.org/tech_activities/publicreview/cdmi|publisher=SNIA|accessdate=17 September 2024}}</ref> to perform bulk updates using CDMI Jobs.<ref>{{cite web|title=CDMI Jobs Extension Version 2.0|url=https://www.snia.org/sites/default/files/technical-work/cdmi/draft/SNIA-CDMI-Jobs-Extension-2.0-DRAFT.pdf|publisher=SNIA|accessdate=17 September 2024}}</ref>
==Capabilities==
Compliant implementations must provide access to a set of configuration parameters known as ''capabilities''.
These are either boolean values that represent whether or not a system supports things such as queues, export via other protocols, path-based storage and so on, or numeric values expressing system limits, such as how much metadata may be placed on an object. As a minimal compliant implementation can be quite small, with few features, clients need to check the cloud storage system for a capability before attempting to use the functionality it represents. Resource allocation assignments limited to the data management interface protocols must possess access bypass capabilities which extend beyond the layered framework.<ref>{{cite book |last1=Metheny |first1=M |title=Federal Cloud Computing: The Definitive Guide for Cloud Service Providers |date=2017 |publisher=Syngress |pages=202–245}}</ref> This integral function is vital to the prevention of transport layer session hijacking by unauthorized entities which may circumvent standard interfacing security parameters.<ref>{{cite book |last1=da Fonseca |first1=N |title=Cloud Services, Networking, and Management |date=2015 |publisher=John Wiley & Sons |pages=70–98}}</ref>
==Containers==
Line 49 ⟶ 54:
==Compliance==
Both retention intervals and retention holds are supported by CDMI. A retention interval consists of a start time and a retention period. During this time interval, objects are preserved as immutable and may not be deleted. A retention hold is usually placed on an object because of judicial action and has the same effect: objects may not be changed nor deleted until all holds placed on them are removed.
==Billing==
Line 77 ⟶ 79:
{{reflist}}
[[Category:Cloud storage]]
| |||