This book assumes a medium level of proficiency on the Linux operating system, and a basic knowledge of storage technologies and networking. Although the book will go through a simple multinode setup of a Ceph cluster, it would be advisable that the reader has some prior experience of using Ceph. Although the book uses Virtual Box, feel free to use any other lab environment, such as VMware Workstation or other tools.

This book requires that you have enough resources for the whole Ceph lab environment. The minimum hardware or virtual requirements are listed as follows:

• CPU: 2 cores
• Memory: 8 GB RAM (16 GB recommended)
• Disk space: 40 GB

To follow along with book, you'll need the following software:

• VirtualBox
• vagrant

Internet connectivity is required to install the necessary packages that are part of the examples in each chapter.

You can download the example code files for this book from your account at www.packt.com. If you purchased this book elsewhere, you can visit www.packt.com/support and register to have the files emailed directly to you.

You can download the code files by following these steps:

1. Log in or register at www.packt.com.
2. Select the SUPPORT tab.
3. Click on Code Downloads & Errata.
4. Enter the name of the book in the Search box and follow the onscreen instructions.

Once the file is downloaded, please make sure that you unzip or extract the folder using the latest version of:

• WinRAR/7-Zip for Windows
• Zipeg/iZip/UnRarX for Mac
• 7-Zip/PeaZip for Linux

The code bundle for the book is also hosted on GitHub at https://github.com/PacktPublishing/Mastering-Ceph-Second-Edition. In case there's an update to the code, it will be updated on the existing GitHub repository.

We also have other code bundles from our rich catalog of books and videos available at https://github.com/PacktPublishing/. Check them out!

We also provide a PDF file that has color images of the screenshots/diagrams used in this book. You can download it here: https://www.packtpub.com/sites/default/files/downloads/9781789610703_ColorImages.pdf.

There are a number of text conventions used throughout this book.

CodeInText: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: "Install the corosync, pacemaker, and cmrsh toolsets using the following code:"

A block of code is set as follows:

Vagrant.configure("2") do |config|
nodes.each do |node|
config.vm.define node[:hostname] do |nodeconfig|
nodeconfig.vm.box = "bento/ubuntu-16.04" 

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

Vagrant.configure("2") do |config|
nodes.each do |node|
config.vm.define node[:hostname] do |nodeconfig|
nodeconfig.vm.box = "bento/ubuntu-16.04" 

Any command-line input or output is written as follows:

 yum install *.rpm 

Bold: Indicates a new term, an important word, or words that you see onscreen. For example, words in menus or dialog boxes appear in the text like this. Here is an example: "Click on the Repo URL link, which will take you to the repository directory tree."