Jump to content

Ceph (software)

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Anthonyeleven (talk | contribs) at 06:18, 9 May 2023 (Refresh the first 40% of this article, improving grammar and reducing ambiguity. Various references and facts are also updated to reflect modern releases and practices.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

This article is about the computer storage platform. For other uses, see Ceph (disambiguation).
Ceph Storage
Original author(s)Inktank Storage (Sage Weil, Yehuda Sadeh Weinraub, Gregory Farnum, Josh Durgin, Samuel Just, Wido den Hollander)
Developer(s)Red Hat, Intel, CERN, Cisco, Fujitsu, SanDisk, Canonical and SUSE[1]
Stable release
18.2.0[2] Edit this on Wikidata (Reef) / 3 August 2023
Repository
Written inC++, Python[3]
Operating systemLinux, FreeBSD[4]
TypDistributed object store
LicenseLGPLv2.1[5]
Websiteceph.io

Ceph (pronounced /ˈsɛf/) is an open-source software-defined storage platform that provides object storage[6], block storage, and file storage built on a common distributed cluster foundation. Ceph provides completely distributed operation without a single point of failure and scalability to the exabyte level, and is freely available. Since version 12 (Luminous), Ceph does not rely on any other, conventional filesystem and directly manages HDDs and SSDs with its own storage backend BlueStore and can expose a POSIX filesystem.

Ceph replicates data with fault tolerance,[7] using commodity hardware and Ethernet IP and requiring no specific hardware support. Ceph is highly available and ensures strong data durability through techniques including replication, [[Erasure_code|erasure coding], snapshots and clones. By design, the system is both self-healing and self-managing, minimizing administration time and other costs.

Large-scale production Ceph deployments include CERN,[8][9] OVH[10][11][12][13] and DigitalOcean.[14][15]

Design

A high-level overview of the Ceph's internal organization[16]: 4 

Ceph employs five distinct kinds of daemons:[16]

  • Cluster monitors (ceph-mon) that keep track of active and failed cluster nodes, cluster configuration, and information about data placement and global cluster state.
  • OSDs (ceph-osd) that manage bulk data storage devices directly via the BlueStore back end,[17] which since the v12.x release replaces the Filestore[18] back end, which was implemented on top of a traditional filesystem)
  • Metadata servers (ceph-mds) that maintain and broker access to inodes and directories inside a CephFS filesystem
  • HTTP gateways (ceph-rgw) that expose the object storage layer as an interface compatible with Amazon S3 oder OpenStack Swift APIs
  • Managers (ceph-mgr) that perform cluster monitoring, bookkeeping, and maintenance tasks, and interface to external monitoring systems and management (e.g. balancer, dashboard, Prometheus, Zabbix plugin)[19]

All of these are fully distributed, and may be deployed on disjoint, dedicated servers or in a converged topology. Clients with different needs directly interact with appropriate cluster components.[20]

Ceph distributes data across multiple storage devices and nodes to achieve higher throughput, in a fashion similar to [RAID]]. Adaptive load balancing is supported whereby frequently accessed services may be replicated over more nodes. [21]

As of September 2017, BlueStore is the default and recommended storage back end for production environments,[22] which provides better latency and configurability than the older Filestore back end, and avoiding the shortcomings of filesystem based storage involving additional processing and caching layers. The Filestore back end will be deprecated as of the Reef release in mid 2023. XFS was the recommended underlying filesystem for Filestore OSDs, and Btrfs could be used at one's own risk. ext4 filesystems were not recommended due to limited metadata capacity. [23] The BlueStore back end does still use XFS for used for a small metadata partition.[24]

Object storage S3

An architecture diagram showing the relations among components of the Ceph storage platform

Ceph implements distributed object storage via the RADOS GateWay (ceph-rgw), which exposes the underlying storage layer via an interface compatible with Amazon S3 oder OpenStack Swift.

Ceph RGW deployments scale readily and often utilize large and dense storage media for bulk use cases that include Big Data (datalake), backups & archives, IOT, media, video recording, and deployment images for virtual machines and [[Containerization_(computing)\containers].

Ceph's software libraries provide client applications with direct access to the reliable autonomic distributed object store (RADOS) object-based storage system. More frequently used are libraries for Ceph's RADOS Block Device (RBD), RADOS Gateway, and Ceph File System services. In this way, administrators can maintain their storage devices within a unified system, which makes it easier to replicate and protect the data.

The "librados" software libraries provide access in C, C++, Java, PHP, and Python. The RADOS Gateway also exposes the object store as a RESTful interface which can present as both native Amazon S3 and OpenStack Swift APIs.

Block storage

Ceph can provide clients with thin-provisioned block devices. When an application writes data to Ceph using a block device, Ceph automatically stripes and replicates the data across the cluster. Ceph's RADOS Block Device (RBD) also integrates with Kernel-based Virtual Machines (KVMs).

Ceph block storage may be deployed on traditional HDDs and/or SSDs which are associated with Ceph's block storage for use cases, including databases, virtual machines, data analytics, artificial intelligence, and machine learning. Block storage clients often require high [[Hard_disk_drive_performance_characteristics#Data_transfer_rate|throughput] and IOPS, thus Ceph RBD deployments increasingly utilize SSDs with NVMe interfaces.

"RBD" is built on with Ceph's foundational RADOS object storage system that provides the librados interface and the CephFS file system. Since RBD is built on librados, RBD inherits librados's abilities, including clones and snapshots and clones. By striping volumes across the cluster, Ceph improves performance for large block device images.

"Ceph-iSCSI" is a gateway which enables access to distributed, highly available block storage from Microsoft Windows and VMware vSphere servers or clients capable of speaking the iSCSI protocol. By using ceph-iscsi on one or more iSCSI gateway hosts, Ceph RBD images become available as Logical Units (LUs) associated with iSCSI targets, which can be accessed in an optionally load-balanced, highly available fashion.

Since ceph-iscsi configuration is stored in the Ceph RADOS object store, ceph-iscsi gateway hosts are inherently without persistent state and thus can be replaced, augmented, or reduced at will. As a result, Ceph Storage enables customers to run a truly distributed, highly-available, resilient, and self-healing enterprise storage technology on commodity hardware and an entirely open source platform.

The block device can be virtualized, providing block storage to virtual machines, in virtualization platforms such as Openshift, OpenStack, Kubernetes, OpenNebula, Ganeti, Apache CloudStack and Proxmox Virtual Environment.

File system storage

Ceph's file system (CephFS) runs on top of the same object storage system that provides object storage and block device interfaces. The Ceph metadata server cluster provides a service that maps the directories and file names of the file system to objects stored within RADOS clusters. The metadata server cluster can expand or contract, and it can rebalance the file system dynamically to distribute data evenly among cluster hosts. This ensures high performance and prevents heavy loads on specific hosts within the cluster.

Clients mount the POSIX-compatible file system using a Linux kernel client. An older FUSE-based client is also available. The servers run as regular Unix daemons.

Ceph's file storage is often associated with log collection, messaging, and file storage.

Dashboard

Ceph Dashboard landing page (2023)

From 2018 there is also a Dashboard UI project, which helps to manage the cluster. It's beeing developed by Ceph community on LGPL-3 and uses Ceph-mgr, Python, Angular framework and Grafana.[25] Landing page has been refreshed in the beginning of 2023.[26]

Some previous attempts to create similar tools were made, but are closed now: Calamari (2013-2018), OpenAttic (2013-2019), VSM (2014-2016), Inkscope (2015-2016) and Ceph-adm (2015-2017).[27]

Crimson

From 2019 there is ongoing project to reimplement OSD in Ceph, called Crimson. Main goal of Crimson is minimizing CPU overhead and latency, because modern storage devices like NVMe got much faster than HDD and even SSD, but CPUs do not catch up with that change. Moreover crimson-osd is meant to be backward compatible drop-in replacement for ceph-osd. While Crimson can work with BlueStore (via AlienStore), a new native ObjectStore implementation called SeaStore is also being developed and CyanStore for testing purposes. There are few reasons for creating SeaStore, one of them is the fact, that transaction support in the BlueStore are provided by RocksDB, which would mean re-implementing this to achieve better parallelism.[28][29][30]

History

Ceph was initially created by Sage Weil for his doctoral dissertation,[31] which was advised by Professor Scott A. Brandt at the Jack Baskin School of Engineering, University of California, Santa Cruz (UCSC), and sponsored by the Advanced Simulation and Computing Program (ASC), including Los Alamos National Laboratory (LANL), Sandia National Laboratories (SNL), and Lawrence Livermore National Laboratory (LLNL).[32] The first line of code that ended up being part of Ceph was written by Sage Weil in 2004 while at a summer internship at LLNL, working on scalable filesystem metadata management (known today as Ceph's MDS).[33] In 2005, as part of a summer project initiated by Scott A. Brandt and led by Carlos Maltzahn, Sage Weil created a fully functional file system prototype which adopted the name Ceph. Ceph made its debut with Sage Weil giving two presentations in November 2006, one at USENIX OSDI 2006[34] and another at SC'06.[35]

After his graduation in autumn 2007, Weil continued to work on Ceph full-time, and the core development team expanded to include Yehuda Sadeh Weinraub and Gregory Farnum. On March 19, 2010, Linus Torvalds merged the Ceph client into Linux kernel version 2.6.34[36][37] which was released on May 16, 2010. In 2012, Weil created Inktank Storage for professional services and support for Ceph.[38][39]

In April 2014, Red Hat purchased Inktank, bringing the majority of Ceph development in-house to make it a production version for enterprises with support (hotline) and continuous maintenance (new versions).[40]

In October 2015, the Ceph Community Advisory Board was formed to assist the community in driving the direction of open source software-defined storage technology. The charter advisory board includes Ceph community members from global IT organizations that are committed to the Ceph project, including individuals from Red Hat, Intel, Canonical, CERN, Cisco, Fujitsu, SanDisk, and SUSE.[41]

In November 2018, the Linux Foundation launched the Ceph Foundation as a successor to the Ceph Community Advisory Board. Founding members of the Ceph Foundation included Amihan, Canonical, China Mobile, DigitalOcean, Intel, OVH, ProphetStor Data Services, Red Hat, SoftIron, SUSE, Western Digital, XSKY Data Technology, and ZTE.[42]

In March 2021, SUSE discontinued its Enterprise Storage product incorporating Ceph in favor of Longhorn.[43] and the former Enterprise Storage website was updated stating "SUSE has refocused the storage efforts around serving our strategic SUSE Enterprise Storage Customers and are no longer actively selling SUSE Enterprise Storage."[44]

Release history

Release history
Name Release First release End of
life 		Milestones
Argonaut Old version, no longer maintained: 0.48 July 3, 2012 First major "stable" release
Bobtail Old version, no longer maintained: 0.56 January 1, 2013
Cuttlefish Old version, no longer maintained: 0.61 May 7, 2013 ceph-deploy is stable
Dumpling Old version, no longer maintained: 0.67 August 14, 2013 May 2015 namespace, region, monitoring REST API
Emperor Old version, no longer maintained: 0.72 November 9, 2013 May 2014 multi-datacenter replication for the radosgw
Firefly Old version, no longer maintained: 0.80 May 7, 2014 April 2016 erasure coding, cache tiering, primary affinity, key/value OSD backend (experimental), standalone radosgw (experimental)
Giant Old version, no longer maintained: 0.87 October 29, 2014 April 2015
Hammer Old version, no longer maintained: 0.94 April 7, 2015 August 2017
Infernalis Old version, no longer maintained: 9.2.0 November 6, 2015 April 2016
Jewel Old version, no longer maintained: 10.2.0 April 21, 2016 2018-06-01 Stable CephFS, experimental RADOS backend named BlueStore
Kraken Old version, no longer maintained: 11.2.0 January 20, 2017 2017-08-01 BlueStore is stable
Luminous Old version, no longer maintained: 12.2.0 August 29, 2017 2020-03-01
Mimic Old version, no longer maintained: 13.2.0 June 1, 2018 2020-07-22 snapshots are stable, Beast is stable
Nautilus Old version, no longer maintained: 14.2.0 March 19, 2019 2021-06-01
Octopus Old version, no longer maintained: 15.2.0 March 23, 2020 2022-06-01
Pacific Older version, yet still maintained: 16.2.0 March 31, 2021[45] 2023-06-01
Quincy Current stable version: 17.2.0 April 19, 2022[46] 2024-06-01
Reef[47] Future release: TBA TBA
Legend:
Old version
Older version, still maintained
Latest version
Latest preview version
Future release

Etymology

The name "Ceph" is an abbreviation of "cephalopod", a class of molluscs that includes the octopus. The name (emphasized by the logo) suggests the highly parallel behavior of an octopus and was chosen to associate the file system with "Sammy", the banana slug mascot of UCSC.[16] Both cephalopods and banana slugs are molluscs.

See also

References

  1. ^ "Ceph Community Forms Advisory Board". 2015-10-28. Archived from the original on 2019-01-29. Retrieved 2016-01-20.
  2. ^ https://github.com/ceph/ceph/releases/tag/v18.2.0. Retrieved 26 August 2023. {{cite web}}: Missing or empty |title= (help)
  3. ^ "GitHub Repository". GitHub.
  4. ^ "FreeBSD Quarterly Status Report".
  5. ^ "LGPL2.1 license file in the Ceph sources". GitHub. 2014-10-24. Retrieved 2014-10-24.
  6. ^ Nicolas, Philippe (2016-07-15). "The History Boys: Object storage ... from the beginning". The Register.
  7. ^ Jeremy Andrews (2007-11-15). "Ceph Distributed Network File System". KernelTrap. Archived from the original on 2007-11-17. Retrieved 2007-11-15.
  8. ^ "Ceph Clusters". CERN. Retrieved 12 November 2022.
  9. ^ "Ceph Operations at CERN: Where Do We Go From Here? - Dan van der Ster & Teo Mouratidis, CERN". YouTube. 24 May 2019. Retrieved 12 November 2022.
  10. ^ Dorosz, Filip (15 June 2020). "Journey to next-gen Ceph storage at OVHcloud with LXD". OVHcloud. Retrieved 12 November 2022.
  11. ^ "CephFS distributed filesystem". OVHcloud. Retrieved 12 November 2022.
  12. ^ "Ceph - Distributed Storage System in OVH [en] - Bartłomiej Święcki". YouTube. 7 April 2016. Retrieved 12 November 2022.
  13. ^ "200 Clusters vs 1 Admin - Bartosz Rabiega, OVH". YouTube. 24 May 2019. Retrieved 15 November 2022.
  14. ^ D'Atri, Anthony (31 May 2018). "Why We Chose Ceph to Build Block Storage". DigitalOcean. Retrieved 12 November 2022.
  15. ^ "Ceph Tech Talk: Ceph at DigitalOcean". YouTube. 7 October 2021. Retrieved 12 November 2022.
  16. ^ a b c M. Tim Jones (2010-06-04). "Ceph: A Linux petabyte-scale distributed file system" (PDF). IBM. Retrieved 2014-12-03.
  17. ^ "BlueStore". Ceph. Retrieved 2017-09-29.
  18. ^ "BlueStore Migration". Retrieved 2020-04-12.
  19. ^ "Ceph Manager Daemon — Ceph Documentation". docs.ceph.com. Archived from the original on June 6, 2018. Retrieved 2019-01-31. archive link Archived June 19, 2020, at the Wayback Machine
  20. ^ Jake Edge (2007-11-14). "The Ceph filesystem". LWN.net.
  21. ^ Anthony D'Atri, Vaibhav Bhembre (2017-10-01). "Learning Ceph, Second Edition". Packt.
  22. ^ Sage Weil (2017-08-29). "v12.2.0 Luminous Released". Ceph Blog.
  23. ^ "Hard Disk and File System Recommendations". ceph.com. Archived from the original on 2017-07-14. Retrieved 2017-06-26.
  24. ^ "BlueStore Config Reference". Retrieved April 12, 2020.
  25. ^ "Ceph Dashboard". Ceph documentation. Retrieved 11 April 2023.
  26. ^ Gomez, Pedro Gonzalez (23 February 2023). "Introducing the new Dashboard Landing Page". Retrieved 11 April 2023.
  27. ^ "Operating Ceph from the Ceph Dashboard: past, present and future". YouTube. 22 November 2022. Retrieved 11 April 2023.
  28. ^ Just, Sam (18 January 2021). "Crimson: evolving Ceph for high performance NVMe". Red Hat Emerging Technologies. Retrieved 12 November 2022.
  29. ^ Just, Samuel (10 November 2022). "What's new with Crimson and Seastore?". YouTube. Retrieved 12 November 2022.
  30. ^ "Crimson: Next-generation Ceph OSD for Multi-core Scalability". Ceph blog. Ceph. 7 February 2023. Retrieved 11 April 2023.
  31. ^ Sage Weil (2007-12-01). "Ceph: Reliable, Scalable, and High-Performance Distributed Storage" (PDF). University of California, Santa Cruz. Archived from the original (PDF) on 2017-07-06. Retrieved 2017-03-11.
  32. ^ Gary Grider (2004-05-01). "The ASCI/DOD Scalable I/O History and Strategy" (PDF). University of Minnesota. Retrieved 2019-07-17.
  33. ^ Dynamic Metadata Management for Petabyte-Scale File Systems, SA Weil, KT Pollack, SA Brandt, EL Miller, Proc. SC'04, Pittsburgh, PA, November, 2004
  34. ^ "Ceph: A scalable, high-performance distributed file system," SA Weil, SA Brandt, EL Miller, DDE Long, C Maltzahn, Proc. OSDI, Seattle, WA, November, 2006
  35. ^ "CRUSH: Controlled, scalable, decentralized placement of replicated data," SA Weil, SA Brandt, EL Miller, DDE Long, C Maltzahn, SC'06, Tampa, FL, November, 2006
  36. ^ Sage Weil (2010-02-19). "Client merged for 2.6.34". ceph.newdream.net. Archived from the original on 2010-03-23. Retrieved 2010-03-21.
  37. ^ Tim Stephens (2010-05-20). "New version of Linux OS includes Ceph file system developed at UCSC". news.ucsc.edu.
  38. ^ Bryan Bogensberger (2012-05-03). "And It All Comes Together". Inktank Blog. Archived from the original on 2012-07-19. Retrieved 2012-07-10.
  39. ^ Joseph F. Kovar (July 10, 2012). "The 10 Coolest Storage Startups Of 2012 (So Far)". CRN. Retrieved July 19, 2013.
  40. ^ Red Hat Inc (2014-04-30). "Red Hat to Acquire Inktank, Provider of Ceph". Red Hat. Retrieved 2014-08-19.
  41. ^ "Ceph Community Forms Advisory Board". 2015-10-28. Archived from the original on 2019-01-29. Retrieved 2016-01-20.
  42. ^ "The Linux Foundation Launches Ceph Foundation To Advance Open Source Storage". 2018-11-12.
  43. ^ "SUSE says tschüss to Ceph-based enterprise storage product – it's Rancher's Longhorn from here on out".
  44. ^ "SUSE Enterprise Software-Defined Storage".
  45. ^ Ceph.io — v16.2.0 Pacific released
  46. ^ Ceph.io — v17.2.0 Quincy released
  47. ^ Perez, Mike (8 April 2022). "Ceph Developer Summit - Reef". Ceph. Retrieved 12 November 2022.

Further reading

Look up κεφαλή in Wiktionary, the free dictionary.
Wikimedia Commons has media related to Ceph.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Ceph_(software)&oldid=1153931604"