Book Image

Ceph: Designing and Implementing Scalable Storage Systems

By : Michael Hackett, Vikhyat Umrao, Karan Singh, Nick Fisk, Anthony D'Atri, Vaibhav Bhembre
Book Image

Ceph: Designing and Implementing Scalable Storage Systems

By: Michael Hackett, Vikhyat Umrao, Karan Singh, Nick Fisk, Anthony D'Atri, Vaibhav Bhembre

Overview of this book

This Learning Path takes you through the basics of Ceph all the way to gaining in-depth understanding of its advanced features. You’ll gather skills to plan, deploy, and manage your Ceph cluster. After an introduction to the Ceph architecture and its core projects, you’ll be able to set up a Ceph cluster and learn how to monitor its health, improve its performance, and troubleshoot any issues. By following the step-by-step approach of this Learning Path, you’ll learn how Ceph integrates with OpenStack, Glance, Manila, Swift, and Cinder. With knowledge of federated architecture and CephFS, you’ll use Calamari and VSM to monitor the Ceph environment. In the upcoming chapters, you’ll study the key areas of Ceph, including BlueStore, erasure coding, and cache tiering. More specifically, you’ll discover what they can do for your storage system. In the concluding chapters, you will develop applications that use Librados and distributed computations with shared object classes, and see how Ceph and its supporting infrastructure can be optimized. By the end of this Learning Path, you'll have the practical knowledge of operating Ceph in a production environment. This Learning Path includes content from the following Packt products: • Ceph Cookbook by Michael Hackett, Vikhyat Umrao and Karan Singh • Mastering Ceph by Nick Fisk • Learning Ceph, Second Edition by Anthony D'Atri, Vaibhav Bhembre and Karan Singh
Table of Contents (27 chapters)
Title Page
About Packt
Contributors
Preface
Index

What is BlueStore?


BlueStore is a Ceph object store that is primarily designed to address the limitations of filestore, which, as of the Kraken release, is the current object store. Initially, a new object store was being developed to replace filestore, with a highly original name of NewStore. NewStore was a combination of RocksDB, a key value store to store metadata and a standard portable operating system interface (POSIX) filesystem for the actual objects. However, it quickly became apparent that using a POSIX filesystem still introduced high overheads, which was one of the key reasons from trying to move away from filestore.

Thus, BlueStore was born; using raw block devices in combination with RocksDB, a number of problems were solved that had stunted NewStore. The name BlueStore was a reflection of the combination of the words Block and NewStore:

Block+NewStore=BlewStore=BlueStore

BlueStore is designed to remove the double write penalty associated with filestore and improve performance...