Hitachi Content Platform (HCP) je softwarové řešení objektového úložiště nasazené jako fyzické nebo virtuální (VMware ESXi a KVM) zařízení.
Fyzický systém HCP se skládá z rozsáhlého hardwaru, který podporuje více úrovní ukládání, zabezpečení, cloudové funkce, širokou škálu protokolů a multitenanci. Nativní REST- a Amazon Simple Storage
Service (S3) umožňují bezproblémový přístup k síti WAN nebo LAN pro aplikace Web 2.0 a mobilní aplikace.
Hitachi Content Platform (HCP) is a robust storage system designed to support large, growing repositories of fixed-content data. HCP stores objects that include both data and metadata that describes that data. Objects exist in containers, which are logical partitions of the repository.
Hitachi Content Platform is a distributed storage system designed to support large, growing repositories of fixed-content data. HCP provides a cost-effective, scalable, easy-to-use repository that can accommodate all types of data, from simple text files to medical images to multigigabyte database images.
Hitachi Content Platform is a combination of hardware and software that provides an object-based data storage environment. An HCP repository stores all types of data, from simple text files to medical images to multigigabyte database images.
HCP provides easy access to the repository for adding, retrieving, and deleting data. HCP uses write-once, read-many (WORM) storage technology and a variety of policies and internal processes to ensure the integrity of the stored data and the efficient use of storage capacity
HCP stores objects in a repository. Each object permanently associates data HCP receives (for example, a document, an image, or a movie) with information about that data, called metadata.
An object encapsulates:
An exact digital reproduction of data as it existed before it was stored in HCP. Once it’s in the repository, this fixed-content data cannot be modified.
System-managed properties that describe the fixed-content data (for example, its size and creation date). System metadata includes policies, such as retention and data protection level, that influence how transactions and internal processes affect the object.
Optional metadata that a user or application provides to further describe the object. Custom metadata is specified as one or more annotations, where each annotation is a discrete unit of information about the object. Annotations are typically specified in XML format. You can use custom metadata to create self-describing objects. Users and applications can use this metadata to understand and repurpose object content.
HCP can store multiple versions of an object, thus providing a history of how the data has changed over time. Each version is a separate object, with its own system metadata and, optionally, its own custom metadata and ACL.
HCP supports multipart uploads with the Hitachi API for Amazon S3. With a multipart upload, the data for an object is broken into multiple parts that are written to HCP independently of each other. Even though the data is written in multiple parts, the result of a multipart upload is a single object. An object for which the data is stored in multiple parts is called a multipart object.
Containers and accounts
An HCP repository is partitioned into namespaces which are called containers in the context of the HSwift API. A container is a logical grouping of objects such that the objects in one container are not visible in any other container. Containers are also called namespaces.
The core hardware for an HCP system consists of servers that are networked together. These servers are called nodes.
When you access an HCP system, your point of access is an individual node. To identify the system, however, you can use either the domain name of the system or the IP address of an individual node. When you use the domain name, HCP selects the access node for you. This helps ensure an even distribution of the processing load.
A fixed-content storage system is one in which the data cannot be modified. HCP uses write-once, read-many (WORM) storage technology and a variety of policies and services to ensure the integrity of the stored data and the efficient use of storage capacity.
HCP can run as a SAN-attached array of independent nodes or as a networked redundant array of independent nodes.
HCP with SAN-attached storage includes both internal storage in each node and Fibre-Channel SAN arrays.
HCP with internal storage have only internal storage in each node.
HCP VM systems (called VM systems) run on virtual machines in a VMware® environment or KVM environment. An HCP VM system functions mostly as a system that has a networked redundant array of independent nodes, with the virtual storage emulating internal storage.
Object based storage
HCP stores objects in a repository. Each object permanently associates data HCP receives with information about that data; that is, each object encapsulates both object data and metadata.
HCP distributes objects across its storage space but still presents them as files in a standard directory structure.
Namespace access protocols
HCP supports access to namespaces through a variety of industry-standard protocols. For actions such as adding objects to a namespace, viewing and retrieving objects, changing object metadata, and deleting objects, HCP supports:
A RESTful HTTP API, Hitachi API for Amazon S3, WebDAV, CIFS, NFS, SMTP, NDMP, ...
HCP hardware consists of:
Internal (G11, S31) and/or SAN storage
Networking components such as cables and switches
Additional infrastructure items such as racks and Power Distribution Units (PDUs)
For VM systems, this hardware configuration applies to the physical environment in which HCP -VM runs.
Content Platform S31 Series Node
An HCP S Series Node is a highly efficient, highly available, cost-effective storage device that supports very large amounts of data. HCP systems and HCP for cloud scale systems can use HCP S Series Nodes for direct-write storage and tiering storage. A single HCP system or HCP for cloud scale system can distribute data across multiple HCP S Series Nodes.