FAQ

Frequently asked questions

Quick answers to common questions, with links into the documentation for the full detail.

New to Ceph, or planning your first cluster? These are the questions we hear most often. Each answer links into the documentation, where the full detail lives.

Questions about the Ceph Foundation itself, such as membership and governance, are answered in the Foundation FAQ.

Where to get help

Getting started

What is Ceph?

Ceph is an open source distributed storage system that delivers object, block, and file storage in one unified platform. It runs on commodity hardware, replicates data across the cluster, and heals itself when disks or nodes fail. Start with the introduction in the documentation.

How do I try Ceph quickly?

The fastest path is cephadm: bootstrap a cluster on a single host, then expand it host by host. You need Python 3, systemd, a container runtime (Podman or Docker), time synchronization, and LVM2. Follow the cephadm installation guide or our getting started page.

Is Ceph production ready?

Yes. Ceph powers production storage for organizations worldwide, from research institutions to cloud providers. The project ships a new stable release every year, supports each series for approximately 24 months, and publishes point releases every 4 to 6 weeks. See the release cadence documentation and our case studies.

Does Ceph work with Kubernetes?

Yes. The documentation recommends Rook, a graduated CNCF project, as the way to run Ceph in Kubernetes or to connect an existing cluster to Kubernetes, and the Ceph CSI driver provisions block and file volumes for workloads. See our cloud native page.

Planning and hardware

What hardware do I need?

Ceph is designed for commodity hardware; there is no compatibility list to buy against. The documentation's guidance covers CPU, memory (plan for the OSD memory target, 4 GiB by default, per OSD), separate drives for the operating system and OSD data, and at least 10 Gb/s networking between hosts. Read the hardware recommendations.

What is the minimum cluster size?

For testing, a single monitor, manager, and OSD will run. For production, the documentation recommends at least three monitors for quorum and high availability, at least two managers, and at least three OSDs (or as many as there are copies of each object). See the getting started documentation.

Should I use replication or erasure coding?

Pools are replicated by default: simple, fast, and resilient. Erasure coding stores the same data with less raw capacity (profiles like 4+2 or 6+3 roughly double the usable space compared to three-way replication) at a performance cost that is most visible on hard drives and during recovery. The erasure coding documentation covers the tradeoffs.

The project and community

How does Ceph compare with proprietary or cloud storage?

Ceph delivers enterprise storage capabilities as free and open source software on hardware you choose, with no license fees and no lock-in, and it runs on premises, in private clouds, or alongside public cloud. See why Ceph for the full comparison.

Who uses Ceph?

Businesses, cloud providers, universities, and research institutions around the world. Browse the use cases and case studies, or explore the public telemetry dashboard for opt-in statistics from real clusters.

How do I contribute?

Code, documentation, testing, and bug reports are all welcome. The contribute page walks through the workflow, and the developer guide covers the details.

What license is Ceph released under?

Most of Ceph is dual licensed under the LGPL version 2.1 or 3.0, as stated in the project's COPYING file. Some bundled components carry other free software licenses, such as BSD 3-clause, Boost, and Apache 2.0, and the documentation is licensed under CC BY-SA 3.0.