Book Image

Ceph Cookbook - Second Edition

By : Vikhyat Umrao, Karan Singh, Michael Hackett
Book Image

Ceph Cookbook - Second Edition

By: Vikhyat Umrao, Karan Singh, Michael Hackett

Overview of this book

Ceph is a unified distributed storage system designed for reliability and scalability. This technology has been transforming the software-defined storage industry and is evolving rapidly as a leader with its wide range of support for popular cloud platforms such as OpenStack, and CloudStack, and also for virtualized platforms. Ceph is backed by Red Hat and has been developed by community of developers which has gained immense traction in recent years. This book will guide you right from the basics of Ceph , such as creating blocks, object storage, and filesystem access, to advanced concepts such as cloud integration solutions. The book will also cover practical and easy to implement recipes on CephFS, RGW, and RBD with respect to the major stable release of Ceph Jewel. Towards the end of the book, recipes based on troubleshooting and best practices will help you get to grips with managing Ceph storage in a production environment. By the end of this book, you will have practical, hands-on experience of using Ceph efficiently for your storage requirements.
Table of Contents (15 chapters)

Initial troubleshooting and logging

When you start troubleshooting issues with Ceph, you will first need to determine which Ceph component is causing the issue. This component can sometimes be clearly labeled in a ceph health detail output or a status command, but other times, it will require some further investigation to discover the actual issue. Verifying a high-level cluster's status can also help you determine whether there is just a single failure or an entire node failure. It's also wise to validate that something in your configuration could possibly be attributed to the issue, such as a configuration that is not recommended or a piece of hardware in the environment that is misconfigured. Various recipes in this chapter will help narrow these issues down, but let's begin by looking at a high-level overview of our cluster and what these commands can tell us...