====== @__START-HERE__@ CEPH Course overview ======


====== CEPH pre concepts ======

===== What is an Object Storage?? =====
Copy/paste \\
//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.//
\\
\\
blablabla, summary:\\
  * An Object Storage (like our ceph) is a set of services (and usually, servers) which provides a **easy** way to store tons of objects.\\
  * You don't have to mind about how/where to place them in one "filesystem".\\

===== What is an Object =====

An object can be defined as a static element, for example:
  * photo
  * video
  * js/javascript
  * css
  * pdf
  * TID :-)
\\
What will **not** be a object? A dynamic element:
  * asp
  * php
  * cgi
  * json (usually the information inside a json is dynamic)
  * xml (same as previous case)

===== Why do we need an Object Storage =====

  * Will be a cost-effective way to store tons of data (see "What is an object" and think about it)
  * Will scale forever, in the case we run out of space, is compatible with [[https://aws.amazon.com/s3/|Amazon S3]], [[https://cloud.google.com/storage/docs/json_api/v1/objects|Google Objects]] and maybe any other manufacturer which provides Object Storage services/appliances.
  * Have you think about TID's, we can have them out of oracle!


====== CEPH: course overview ======
{{page>linux:ceph:start_here}}


===== Appendix 1 : GUI's and clis (s3browser/rclone) =====
==== s3browser ====

{{page>linux:ceph:tools:gui_for_httpobjectstorage#the_gui}}

==== Rclone: rsync for object storage ====

{{page>linux:ceph:rclone_usage#usage}}

===== Appendix 2 : Use Amazon S3 naming method =====


Amazon Naming method consist on:
<graphviz>
digraph G {
    compound=true;
    node [shape=record];
    namin [label="http:// | { { clover.ciberterminal.net/|bucketname/}  | { bucketname.|clover.ciberterminal.net/} } | objectname"];
}
</graphviz>

See [[https://docs.ceph.com/docs/nautilus/radosgw/s3/commons/|official documentation]]


===== Appendix 3 : Using ACL's =====
{{page>linux:dba:ceph:howtos:using_acl}}


===== Appendix 4 : Bonus thoughts =====

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.