Ceph (software)

Ceph (pronounced /ˈsɛf/) is an open-source software storage platform, implements object storage on a single distributed computer cluster, and provides 3in1 interfaces for : object-, block- and file-level storage. Ceph aims primarily for completely distributed operation without a single point of failure, scalable to the exabyte level, and freely available.

Ceph
Original author(s)Inktank Storage (Sage Weil, Yehuda Sadeh Weinraub, Gregory Farnum, Josh Durgin, Samuel Just, Wido den Hollander)
Developer(s)Canonical, CERN, Cisco, Fujitsu, Intel, Red Hat, SanDisk, and SUSE[1]
Stable release
15.2.3 "Octopus"[2] / 29 May 2020 (2020-05-29)
Preview release
15.1.1 "Octopus"[3] / March 13, 2020 (2020-03-13)
Repository
Written inC++, Python[4]
Operating systemLinux, FreeBSD[5]
TypeDistributed object store
LicenseLGPLv2.1[6]
Websiteceph.io

Ceph replicates data and makes it fault-tolerant,[7] using commodity hardware and requiring no specific hardware support. As a result of its design, the system is both self-healing and self-managing, aiming to minimize administration time and other costs.

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

Ceph employs five distinct kinds of daemons:[8]

  • Cluster monitors (ceph-mon) that keep track of active and failed cluster nodes, cluster configuration, and information about data placement and global cluster state.
  • Object storage devices (ceph-osd) that use a direct, journaled disk storage (named BlueStore,[9] which since the v12.x release replaces the FileStore[10] which would use a filesystem)
  • Metadata servers (ceph-mds) that cache 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 or 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)[11]

All of these are fully distributed, and may run on the same set of servers. Clients with different needs can directly interact with different subsets of them.[12]

Ceph does striping of individual files across multiple nodes to achieve higher throughput, similar to how RAID0 stripes partitions across multiple hard drives. Adaptive load balancing is supported whereby frequently accessed objects are replicated over more nodes. As of September 2017, BlueStore is the default and recommended storage type for production environments,[13] which is Ceph's own storage implementation providing better latency and configurability than the filestore backend, and avoiding the shortcomings of the filesystem based storage involving additional processing and caching layers. The Filestore backend is still considered useful and very stable; XFS used to be the recommended underlying filesystem type for production environments, while Btrfs was recommended for non-production environments. ext4 filesystems were not recommended because of resulting limitations on the maximum RADOS objects length.[14] Even using BlueStore, XFS is used for a small partition of metadata.[15]

Object storage
An architecture diagram showing the relations between components of the Ceph storage platform

Ceph implements distributed object storage - BlueStore. Ceph's software libraries provide client applications with direct access to the reliable autonomic distributed object store (RADOS) object-based storage system, and also provide a foundation for some of Ceph's features, including RADOS Block Device (RBD), RADOS Gateway, and the Ceph File System.

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's object storage system allows users to mount Ceph as a thin-provisioned block device. 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 RBD interfaces with the same Ceph object storage system that provides the librados interface and the CephFS file system, and it stores block device images as objects. Since RBD is built on librados, RBD inherits librados's abilities, including read-only snapshots and revert to snapshot. By striping images across the cluster, Ceph improves read access performance for large block device images.

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

File system

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.

History

Ceph was initially created by Sage Weil for his doctoral dissertation,[16] 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).[17] 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).[18] 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[19] and another at SC'06.[20]

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[21][22] which was released on May 16, 2010. In 2012, Weil created Inktank Storage for professional services and support for Ceph.[23][24]

In April 2014, Red Hat purchased Inktank, bringing the majority of Ceph development in-house.[25]

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 Canonical, CERN, Cisco, Fujitsu, Intel, Red Hat, SanDisk, and SUSE.[26]

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 Older version, yet still maintained: 12.2.0 August 29, 2017
Mimic Older version, yet still maintained: 13.2.0 June 1, 2018 snapshots are stable ,Beast is stable
Nautilus Older version, yet still maintained: 14.2.0 March 19, 2019
Octopus Current stable version: 15.2.0 March 23, 2020
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.[8] Both cephalopods and banana slugs are molluscs.

See also

References
  1. "Ceph Community Forms Advisory Board". 2015-10-28. Retrieved 2016-01-20.
  2. "v15.2.3 Octopus released".
  3. "Index of /tarballs/".
  4. "GitHub Repository".
  5. "FreeBSD Quarterly Status Report".
  6. "LGPL2.1 license file in the Ceph sources". 2014-10-24. Retrieved 2014-10-24.
  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. M. Tim Jones (2010-06-04). "Ceph: A Linux petabyte-scale distributed file system" (PDF). IBM. Retrieved 2014-12-03.
  9. "BlueStore". Ceph. Retrieved 2017-09-29.
  10. "BlueStore Migration". Retrieved 2020-04-12.
  11. "Ceph Manager Daemon — Ceph Documentation". docs.ceph.com. Retrieved 2019-01-31.
  12. Jake Edge (2007-11-14). "The Ceph filesystem". LWN.net.
  13. Sage Weil (2017-08-29). "v12.2.0 Luminous Released". Ceph Blog.
  14. "Hard Disk and File System Recommendations". ceph.com. Archived from the original on 2017-07-14. Retrieved 2017-06-26.
  15. "BlueStore Config Reference". Retrieved April 12, 2020.
  16. Sage Weil (2007-12-01). "Ceph: Reliable, Scalable, and High-Performance Distributed Storage" (PDF). University of California, Santa Cruz.
  17. Gary Grider (2004-05-01). "The ASCI/DOD Scalable I/O History and Strategy" (PDF). University of Minnesota. Retrieved 2019-07-17.
  18. Dynamic Metadata Management for Petabyte-Scale File Systems, SA Weil, KT Pollack, SA Brandt, EL Miller, Proc. SC'04, Pittsburgh, PA, November, 2004
  19. "Ceph: A scalable, high-performance distributed file system," SA Weil, SA Brandt, EL Miller, DDE Long, C Maltzahn, Proc. OSDI, Seattle, WA, November, 2006
  20. "CRUSH: Controlled, scalable, decentralized placement of replicated data," SA Weil, SA Brandt, EL Miller, DDE Long, C Maltzahn, SC'06, Tampa, FL, November, 2006
  21. Sage Weil (2010-02-19). "Client merged for 2.6.34". ceph.newdream.net.
  22. Tim Stephens (2010-05-20). "New version of Linux OS includes Ceph file system developed at UCSC". news.ucsc.edu.
  23. Bryan Bogensberger (2012-05-03). "And It All Comes Together". Inktank Blog. Archived from the original on 2012-07-19. Retrieved 2012-07-10.
  24. Joseph F. Kovar (July 10, 2012). "The 10 Coolest Storage Startups Of 2012 (So Far)". CRN. Retrieved July 19, 2013.
  25. Red Hat Inc (2014-04-30). "Red Hat to Acquire Inktank, Provider of Ceph". Red Hat. Retrieved 2014-08-19.
  26. "Ceph Community Forms Advisory Board". 2015-10-28. Retrieved 2016-01-20.

Further reading
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.