Английская Википедия:Ceph (software)

Материал из Онлайн справочника
Перейти к навигацииПерейти к поиску

Шаблон:Short description Шаблон:About

Шаблон:Infobox software

Ceph (pronounced Шаблон:IPAc-en) is a free and open-source software-defined storage platform that provides object storage,[1] 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,[2] 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 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,[3][4] OVH[5][6][7][8] and DigitalOcean.[9][10]

Design

Файл:Ceph components.svg
A high-level overview of the Ceph's internal organization[11]Шаблон:Rp

Ceph employs five distinct kinds of daemons:[11]

  • Cluster monitors (Шаблон:Mono) that keep track of active and failed cluster nodes, cluster configuration, and information about data placement and global cluster state.
  • OSDs (Шаблон:Mono) that manage bulk data storage devices directly via the BlueStore back end,[12] which since the v12.x release replaces the Filestore[13] back end, which was implemented on top of a traditional filesystem)
  • Metadata servers (Шаблон:Mono) that maintain and broker access to inodes and directories inside a CephFS filesystem
  • HTTP gateways (Шаблон:Mono) that expose the object storage layer as an interface compatible with Amazon S3 or OpenStack Swift APIs
  • Managers (Шаблон:Mono) that perform cluster monitoring, bookkeeping, and maintenance tasks, and interface to external monitoring systems and management (e.g. balancer, dashboard, Prometheus, Zabbix plugin)[14]

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.[15]

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.[16]

Шаблон:As of, BlueStore is the default and recommended storage back end for production environments,[17] 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.[18] The BlueStore back end does still use XFS for a small metadata partition.[19]

Шаблон:Anchor

Object storage S3

Файл:Ceph stack.png
An architecture diagram showing the relations among components of the Ceph storage platform

Ceph implements distributed object storage via the RADOS GateWay (Шаблон:Mono), which exposes the underlying storage layer via an interface compatible with Amazon S3 or 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 containers.[20]

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.

Шаблон:Anchor

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 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. 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.

Шаблон:Anchor

File storage

Ceph's file system (CephFS) runs on top of the same RADOS foundation as Ceph's object storage and block device services. The CephFS metadata server (MDS) 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 file system metadata ranks 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.webp
Ceph Dashboard landing page (2023)

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

Previous dashboards were developed but are closed now: Calamari (2013-2018), OpenAttic (2013-2019), VSM (2014-2016), Inkscope (2015-2016) and Ceph-Dash (2015-2017).[23]

Crimson

Beginning in 2019 the Crimson project has been reimplementing the OSD data path. The goal of Crimson is to minimize latency and CPU overhead. Modern storage devices and interfaces including NVMe and 3D XPoint have become much faster than HDD and even SAS/SATA SSDs, but CPU performance has not kept pace. Moreover Шаблон:Mono is meant to be a backward-compatible drop-in replacement for Шаблон:Mono. While Crimson can work with the BlueStore back end (via AlienStore), a new native ObjectStore implementation called SeaStore is also being developed along with CyanStore for testing purposes. One reason for creating SeaStore is that transaction support in the BlueStore back end is provided by RocksDB, which needs to be re-implemented to achieve better parallelism.[24][25][26]

History

Ceph was created by Sage Weil for his doctoral dissertation,[27] 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).[28] 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).[29] 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[30] and another at SC'06.[31]

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[32][33] which was released on May 16, 2010. In 2012, Weil created Inktank Storage for professional services and support for Ceph.[34][35]

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).[36]

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.[37]

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.[38]

In March 2021, SUSE discontinued its Enterprise Storage product incorporating Ceph in favor of Longhorn,[39] 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."[40]

Release history

Release history
Name Release First release End of
life 		Milestones
Argonaut Шаблон:Version July 3, 2012 First major "stable" release
Bobtail Шаблон:Version January 1, 2013
Cuttlefish Шаблон:Version May 7, 2013 ceph-deploy is stable
Dumpling Шаблон:Version August 14, 2013 May 2015 namespace, region, monitoring REST API
Emperor Шаблон:Version November 9, 2013 May 2014 multi-datacenter replication for RGW
Firefly Шаблон:Version May 7, 2014 April 2016 erasure coding, cache tiering, primary affinity, key/value OSD backend (experimental), standalone RGW (experimental)
Giant Шаблон:Version October 29, 2014 April 2015
Hammer Шаблон:Version April 7, 2015 August 2017
Infernalis Шаблон:Version November 6, 2015 April 2016
Jewel Шаблон:Version April 21, 2016 2018-06-01 Stable CephFS, experimental OSD back end named BlueStore, daemons no longer run as the root user
Kraken Шаблон:Version January 20, 2017 2017-08-01 BlueStore is stable, EC for RBD pools
Luminous Шаблон:Version August 29, 2017 2020-03-01 pg-upmap balancer
Mimic Шаблон:Version June 1, 2018 2020-07-22 snapshots are stable, Beast is stable, official GUI (Dashboard)
Nautilus Шаблон:Version March 19, 2019 2021-06-01 asynchronous replication, auto-retry of failed writes due to grown defect remapping
Octopus Шаблон:Version March 23, 2020 2022-06-01
Pacific Шаблон:Version March 31, 2021[41] 2023-06-01
Quincy Шаблон:Version April 19, 2022[42] 2024-06-01 auto-setting of min_alloc_size for novel media
Reef Шаблон:Version Aug 3, 2023[43]
Squid Шаблон:Version TBA

Шаблон:Version

Available platforms

While basically built for Linux, Ceph has been also partially ported to Windows platform. It is production-ready for Windows Server 2016 (some commands might be unavailable due to lack of UNIX socket implementation), Windows Server 2019 and Windows Server 2022, but testing/development can be done also on Windows 10 and Windows 11. One can use Ceph RBD and CephFS on Windows, but OSD is not supported on this platform.[44][45][46]

There is also FreeBSD implementation of Ceph.[47]

Etymology

The name "Ceph" is a shortened form of "cephalopod", a class of molluscs that includes squids, cuttlefish, nautiloids, and octopuses. 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.[11] Both cephalopods and banana slugs are molluscs.

See also

Шаблон:Portal Шаблон:Div col

Шаблон:Div col end

References

Шаблон:Reflist

Further reading

External links

Шаблон:Wiktionary Шаблон:Commons category

Шаблон:File systems Шаблон:Red Hat

Партнерские ресурсы
Криптовалюты
Магазины
Хостинг
Разное

  1. ↑ Шаблон:Cite news
  2. ↑ Шаблон:Cite web
  3. ↑ Шаблон:Cite web
  4. ↑ Шаблон:Cite web
  5. ↑ Шаблон:Cite web
  6. ↑ Шаблон:Cite web
  7. ↑ Шаблон:Cite web
  8. ↑ Шаблон:Cite web
  9. ↑ Шаблон:Cite web
  10. ↑ Шаблон:Cite web
  11. ↑ 11,0 11,1 11,2 Шаблон:Cite web
  12. ↑ Шаблон:Cite web
  13. ↑ Шаблон:Cite web
  14. ↑ Шаблон:Cite web archive link Шаблон:Webarchive
  15. ↑ Шаблон:Cite web
  16. ↑ Шаблон:Cite web
  17. ↑ Шаблон:Cite web
  18. ↑ Шаблон:Cite web
  19. ↑ Шаблон:Cite web
  20. ↑ Шаблон:Cite web
  21. ↑ Шаблон:Cite web
  22. ↑ Шаблон:Cite news
  23. ↑ Шаблон:Cite web
  24. ↑ Шаблон:Cite web
  25. ↑ Шаблон:Cite web
  26. ↑ Шаблон:Cite web
  27. ↑ Шаблон:Cite web
  28. ↑ Шаблон:Cite web
  29. ↑ Dynamic Metadata Management for Petabyte-Scale File Systems, SA Weil, KT Pollack, SA Brandt, EL Miller, Proc. SC'04, Pittsburgh, PA, November, 2004
  30. ↑ "Ceph: A scalable, high-performance distributed file system," SA Weil, SA Brandt, EL Miller, DDE Long, C Maltzahn, Proc. OSDI, Seattle, WA, November, 2006
  31. ↑ "CRUSH: Controlled, scalable, decentralized placement of replicated data," SA Weil, SA Brandt, EL Miller, DDE Long, C Maltzahn, SC'06, Tampa, FL, November, 2006
  32. ↑ Шаблон:Cite web
  33. ↑ Шаблон:Cite web
  34. ↑ Шаблон:Cite web
  35. ↑ Шаблон:Cite news
  36. ↑ Шаблон:Cite web
  37. ↑ Шаблон:Cite web
  38. ↑ Шаблон:Cite webШаблон:Dead link
  39. ↑ Шаблон:Cite web
  40. ↑ Шаблон:Cite web
  41. ↑ Ceph.io — v16.2.0 Pacific released
  42. ↑ Ceph.io — v17.2.0 Quincy released
  43. ↑ Шаблон:Cite web
  44. ↑ Шаблон:Cite web
  45. ↑ Шаблон:Cite web
  46. ↑ Шаблон:Cite web
  47. ↑ Ошибка цитирования Неверный тег <ref>; для сносок freebsd не указан текст
Источник — http://wikihandbk.com/ruwiki/index.php?title=Английская_Википедия:Ceph_(software)&oldid=13834354