From Wikipedia, the free encyclopedia
Object storage (also known as object-based storage) is a computer data storage architecture that manages data as objects, as opposed to other storage architectures like file systems which manages data as a file hierarchy, and block storage which manages data as blocks within sectors and tracks. Each object typically includes the data itself, a variable amount of metadata, and a globally unique identifier. Object storage can be implemented at multiple levels, including the device level (object-storage device), the system level, and the interface level. In each case, object storage seeks to enable capabilities not addressed by other storage architectures, like interfaces that can be directly programmable by the application, a namespace that can span multiple instances of physical hardware, and data-management functions like data replication and data distribution at object-level granularity.
Object storage systems allow retention of massive amounts of unstructured data. Object storage is used for purposes such as storing photos on Facebook, songs on Spotify, or files in online collaboration services, such as Dropbox.
An object can be defined as a static element, for example:
What will not be a object? A dynamic element:
|Name:||CEPH: Architecture Overview|
|Description:||This document is the start line to understand this technology|
|Modification date :||11/02/2019|
|Notify changes to:||dodger|
What is NOT:
You can read/watch a basic introduction here: https://ceph.com/ceph-storage/
From a very simple point of view: Ceph acts as a disk.
With the correct OS library like can be the kernel module for “ext4”/“btrfs”, you'll be able to read/write directly.
This library is called
And interact with
RADOS the reliable autonomic distributed object store which is the Object storage itselv.
Continuing with this simple view, like ext4 for example, you'll have data blocks and journal blocks to maintain consistency; that are OSD (object store data) and MON (monitoring) nodes:
So you'll have something like this:
Going deeper, you'll find that the data placement over OSD nodes is calculated by an algorithm called CRUSH: Controlled Replication Under Scalable Hashing which is:
So when a client want to write data in the CEPH cluster though RADOS, librados in the client side invokes CRUSH to perform the calculation on where of the available OSD's write the data.
That result in a very strong architecture with no single point of failure, cause you'll not have a/many node/s taking care of metadata.
Its also really fast: you'll have n*osd servers to perform read/writes.
Its robust, if any of the OSD node fails, the data is replicated N times (where N is a config option) through other OSD's and will be accessible with the CRUSH calculation.
Also if any OSD fail, the MONitors will re-map the cluster and OSD's will re-replicate the data to have copied N times in the cluster.
The unique diference in this case is there's a new component involved, the gateway which translate HTTP/REST into librados.
You'll have a lot of overhead/performance gap using the gateway instead of using librados directly…
So if you take the previous graph, simplified, you'll have:
Official documentation: https://docs.ceph.com/docs/master/cephfs/
Again, the diference in using CEPH as “filesystem” is that there's another component: the “Metadata server”.
Metadata a role similar to Monitor:
When requesting access to any of our object storages or if you're a newcomer, you should know that:
Here you have a template to request a new user for the object storage:
Good morning #infrastructure, We're facing a new project that involves store tons of objects and We want to use our incredible Ceph installation. Please provide us a new User so we can store all the data from this project. Name of the project: "This_template_sucks" Environment: DEVELOPMENT Expected number of buckets: 666 Thanks for your effort, best regards!
Amazon Naming method consist on:
Using ACL's we can publish the object storage to internet (like amazon's S3) to avoid re-using IIS/dotnet/netcore apps only to serve files.