The Ceph Community: A Driving Force for Project Evolution
summary
University project migrates 7,550 TB across 56 labs from SAN/NAS to Ceph because it never loses data (accessibility outages only) and reduces TCO versus Scality, despite early limits (CephFS recovery, RBD client restrictions). Community-driven work delivers BlueStore, Beast, Rook and cephadm, ongoing features like NVMe-oF and Crimson, and Bloomberg-led fixes for RGW multi-site consistency. Help flows through the mailing list, Slack, tracker and ambassador program; many documented PRs and release notes show which bugs were fixed and when.
AI-written summary · about
chapters (6)
- 0:00Introduction to Ceph community
- 1:06Why choose Ceph in 2015
- 6:49Ceph pioneers and contributors
- 15:09Community-driven improvements
- 16:16Getting help in the community
- 19:49How to contribute to Ceph
related talks
13mKeynote: Getting to Know Ceph
29mCeph's journey at SUSE
29mCeph and the future of Open Source Storage
01h 02mIntroduction to Ceph and Architectural Overview
08mKeynote: A Wonderful Journey On Ceph
36mTesting Ceph: Status, Development, & Opportunities
18mKeynote: Open Source Community Engagement: We’re in. Are you?
29mCeph, Xen, and CloudStack: Semper Melior