Book Image

Learning Ceph - Second Edition

By : Karan Singh, Vaibhav Bhembre, Anthony D'Atri
Book Image

Learning Ceph - Second Edition

By: Karan Singh, Vaibhav Bhembre, Anthony D'Atri

Overview of this book

Learning Ceph, Second Edition will give you all the skills you need to plan, deploy, and effectively manage your Ceph cluster. You will begin with the first module, where you will be introduced to Ceph use cases, its architecture, and core projects. In the next module, you will learn to set up a test cluster, using Ceph clusters and hardware selection. After you have learned to use Ceph clusters, the next module will teach you how to monitor cluster health, improve performance, and troubleshoot any issues that arise. In the last module, you will learn to integrate Ceph with other tools such as OpenStack, Glance, Manila, Swift, and Cinder. By the end of the book you will have learned to use Ceph effectively for your data storage requirements.
Table of Contents (18 chapters)
Title Page
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Deploying our Ceph cluster


So far we have downloaded and installed all the necessary dependencies and updated the necessary configuration files in order to prepare for Ceph deployment. In this section, we will make use of all of the work we did previously to finally deploy a Ceph cluster in the sandbox environment.

This proceeds in two phases:

The first phase will use Vagrant to create the virtual machines. Based on the modifications we did to the vagrant_variables.yml file at the end of this step we should see a total of five virtual machines created: 1 for Ceph monitor, 3 for Ceph OSDs, and 1 for the client.

$ vagrant up --no-provision --provider=virtualbox

This instructs vagrant to create the CPU, memory, and storage resources for each virtual machine and boot the machine up. It will use VirtualBox as a provider since we have it already installed on our machines. We are passing the --no-provision command-line flag to ensure that we do not provision each node with Ansible as soon as it comes...