{"id":19367,"date":"2024-01-11T09:52:09","date_gmt":"2024-01-11T06:52:09","guid":{"rendered":"https:\/\/kifarunix.com\/?p=19367"},"modified":"2024-04-09T23:57:31","modified_gmt":"2024-04-09T20:57:31","slug":"how-to-deploy-ceph-storage-cluster-on-debian","status":"publish","type":"post","link":"https:\/\/kifarunix.com\/how-to-deploy-ceph-storage-cluster-on-debian\/","title":{"rendered":"How to Deploy Ceph Storage Cluster on Debian 12"},"content":{"rendered":"<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1622\" height=\"834\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2024\/01\/ceph-reef-18.2.1-dashboard.png\" alt=\"\" class=\"wp-image-19750\" title=\"\" srcset=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2024\/01\/ceph-reef-18.2.1-dashboard.png?v=1704947079 1622w, https:\/\/kifarunix.com\/wp-content\/uploads\/2024\/01\/ceph-reef-18.2.1-dashboard-768x395.png?v=1704947079 768w, https:\/\/kifarunix.com\/wp-content\/uploads\/2024\/01\/ceph-reef-18.2.1-dashboard-1536x790.png?v=1704947079 1536w\" sizes=\"(max-width: 1622px) 100vw, 1622px\" \/><\/figure><\/div>\n\n\n<p>Follow through this post to learn how to deploy Ceph storage cluster on Debian 12. Ceph is a scalable distributed storage system designed for cloud infrastructure and web-scale&nbsp;<a href=\"https:\/\/docs.ceph.com\/docs\/master\/glossary\/#term-ceph-object-storage\" target=\"_blank\" rel=\"noreferrer noopener\">object storage<\/a>. It can also be used to provide&nbsp;<a href=\"https:\/\/docs.ceph.com\/docs\/master\/glossary\/#term-ceph-block-device\" target=\"_blank\" rel=\"noreferrer noopener\">Ceph Block Storage<\/a>&nbsp;as well as&nbsp;<a href=\"https:\/\/docs.ceph.com\/docs\/master\/glossary\/#term-ceph-file-system\" target=\"_blank\" rel=\"noreferrer noopener\">Ceph File System storage<\/a>.<\/p>\n\n\n\n<p>As of this blog post update, CEPH Reef is the current stable <a href=\"https:\/\/docs.ceph.com\/en\/latest\/releases\/\" target=\"_blank\" rel=\"noreferrer noopener\">release<\/a>.<\/p>\n\n\n\n<div class=\"wp-block-rank-math-toc-block\" id=\"rank-math-toc\"><h2>Table of Contents<\/h2><nav><ul><li><a href=\"#deploying-ceph-storage-cluster-on-debian-12\">Deploying Ceph Storage Cluster on Debian 12<\/a><ul><li><a href=\"#the-ceph-storage-cluster-daemons\">The Ceph Storage Cluster Daemons<\/a><\/li><li><a href=\"#ceph-storage-cluster-deployment-methods\">Ceph Storage Cluster Deployment Methods<\/a><\/li><li><a href=\"#ceph-depolyment-requirements\">Ceph Depolyment Requirements<\/a><\/li><li><a href=\"#prepare-ceph-nodes-for-ceph-storage-cluster-deployment-on-debian-12\">Prepare Ceph Nodes for Ceph Storage Cluster Deployment on Debian 12<\/a><ul><li><a href=\"#our-ceph-storage-cluster-deployment-architecture\">Our Ceph Storage Cluster Deployment Architecture<\/a><\/li><li><a href=\"#ceph-storage-nodes-hardware-requirements\">Ceph Storage Nodes Hardware Requirements<\/a><\/li><li><a href=\"#create-ceph-deployment-user-account\">Create Ceph Deployment User Account<\/a><\/li><li><a href=\"#attach-storage-disks-to-ceph-osd-nodes\">Attach Storage Disks to Ceph OSD Nodes<\/a><\/li><li><a href=\"#set-hostnames-and-update-hosts-file\">Set Hostnames and Update Hosts File<\/a><\/li><li><a href=\"#set-time-synchronization\">Set Time Synchronization<\/a><\/li><li><a href=\"#install-ssh-server-on-each-node\">Install SSH Server on Each Node<\/a><\/li><li><a href=\"#enable-root-login-on-other-nodes-from-ceph-admin-node\">Enable Root Login on Other Nodes from Ceph Admin Node<\/a><\/li><li><a href=\"#install-python-3\">Install Python3<\/a><\/li><li><a href=\"#install-docker-ce-on-each-node\">Install Docker CE on Each Node<\/a><\/li><li><a href=\"#install-lvm-package-on-each-node\">Install LVM Package on each Node<\/a><\/li><\/ul><\/li><li><a href=\"#setup-ceph-storage-cluster-on-debian-12\">Setup Ceph Storage Cluster on Debian 12<\/a><ul><li><a href=\"#install-cephadm-utility-on-ceph-admin-node\">Install\u00a0cephadm\u00a0Utility on Ceph Admin Node<\/a><\/li><\/ul><\/li><li><a href=\"#initialize-ceph-cluster-monitor-on-ceph-admin-node\">Initialize Ceph Cluster Monitor On Ceph Admin Node<\/a><\/li><li><a href=\"#enable-ceph-cli\">Enable Ceph CLI<\/a><\/li><li><a href=\"#copy-ssh-keys-to-other-ceph-nodes\">Copy SSH Keys to Other Ceph Nodes<\/a><\/li><li><a href=\"#drop-into-ceph-cli\">Drop into Ceph CLI<\/a><\/li><li><a href=\"#add-ceph-monitor-node-to-ceph-cluster\">Add Ceph Monitor Node to Ceph Cluster<\/a><\/li><li><a href=\"#add-ceph-osd-nodes-to-ceph-cluster\">Add Ceph OSD Nodes to Ceph Cluster<\/a><\/li><li><a href=\"#list-ceph-cluster-nodes\">List Ceph Cluster Nodes;<\/a><\/li><li><a href=\"#create-ceph-os-ds-from-osd-nodes-drives\">Create Ceph OSDs from OSD Nodes Drives<\/a><\/li><li><a href=\"#check-ceph-cluster-health\">Check Ceph Cluster Health<\/a><\/li><li><a href=\"#accessing-ceph-admin-web-user-interface\">Accessing Ceph Admin Web User Interface<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"deploying-ceph-storage-cluster-on-debian-12\">Deploying Ceph Storage Cluster on Debian 12<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"the-ceph-storage-cluster-daemons\">The Ceph Storage Cluster Daemons<\/h3>\n\n\n\n<p>Ceph Storage Cluster&nbsp;is made up of different daemons eas performing specific role.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Ceph Object Storage Daemon (OSD,&nbsp;<\/strong><code><strong>ceph-osd<\/strong><\/code><strong>)<\/strong>\n<ul class=\"wp-block-list\">\n<li>It provides ceph object data store.<\/li>\n\n\n\n<li>It also performs data replication , data recovery, rebalancing and provides storage information to Ceph Monitor.<\/li>\n\n\n\n<li>At least an OSD is required per storage device.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Ceph Monitor (<\/strong><code><strong>ceph-mon<\/strong><\/code><strong>)<\/strong>\n<ul class=\"wp-block-list\">\n<li>It maintains maps of the entire Ceph cluster state including monitor map, manager map, the OSD map, and the CRUSH map.<\/li>\n\n\n\n<li>manages authentication between daemons and clients.<\/li>\n\n\n\n<li>A Ceph cluster must contain a minimum of three running monitors in order to be both redundant and highly-available.&nbsp;If there are at least five nodes on the cluster, it is recommended to run five monitors in the cluster.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Ceph Manager<\/strong>&nbsp;(<strong><code>ceph-mgr<\/code><\/strong>)\n<ul class=\"wp-block-list\">\n<li>keeps track of runtime metrics and the current state of the Ceph cluster, including storage utilization, current performance metrics, and system load.<\/li>\n\n\n\n<li>manages and exposes Ceph cluster web dashboard and API.<\/li>\n\n\n\n<li>At least two managers are required for HA.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Ceph Metadata Server (MDS):<\/strong>\n<ul class=\"wp-block-list\">\n<li>Manages metadata for the Ceph File System (CephFS). Coordinates metadata access and ensures consistency across clients.<\/li>\n\n\n\n<li>One or more, depending on the requirements of the CephFS.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>RADOS Gateway (RGW):<\/strong>\n<ul class=\"wp-block-list\">\n<li>Also called \u201cCeph Object Gateway\u201d<\/li>\n\n\n\n<li>is a component of the Ceph storage system that provides object storage services with a RESTful interface. RGW allows applications and users to interact with Ceph storage using industry-standard APIs, such as the S3 (Simple Storage Service) API (compatible with Amazon S3) and the Swift API (compatible with OpenStack Swift).<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"ceph-storage-cluster-deployment-methods\">Ceph Storage Cluster Deployment Methods<\/h3>\n\n\n\n<p>There are different methods you can use to deploy Ceph storage cluster.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code><strong>cephadm<\/strong><\/code> leverages container technology (specifically, Docker containers) to deploy and manage Ceph services on a cluster of machines.<\/li>\n\n\n\n<li><strong><code>Rook<\/code><\/strong>&nbsp;deploys and manages Ceph clusters running in Kubernetes, while also enabling management of storage resources and provisioning via Kubernetes APIs.<\/li>\n\n\n\n<li><strong><code>ceph-ansible<\/code><\/strong>&nbsp;deploys and manages Ceph clusters using Ansible.<\/li>\n\n\n\n<li>ceph-salt&nbsp;installs Ceph using Salt and cephadm.<\/li>\n\n\n\n<li>jaas.ai\/ceph-mon&nbsp;installs Ceph using Juju.<\/li>\n\n\n\n<li>Installs Ceph via <a href=\"https:\/\/github.com\/openstack\/puppet-ceph\" target=\"_blank\" rel=\"noreferrer noopener\">Puppet<\/a>.<\/li>\n\n\n\n<li>Ceph can also be&nbsp;<a href=\"https:\/\/docs.ceph.com\/en\/latest\/install\/index_manual\/#install-manual\" target=\"_blank\" rel=\"noopener\">installed manually<\/a>.<\/li>\n<\/ul>\n\n\n\n<p>Use of cephadm and rooks are the recommended methods for deploying Ceph storage cluster.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"ceph-depolyment-requirements\">Ceph Depolyment Requirements<\/h3>\n\n\n\n<p>Depending on the deployment method you choose, there are different requirements for deploying Ceph storage cluster<\/p>\n\n\n\n<p>In this tutorial, we will use cephadm to deploy Ceph storage cluster.<\/p>\n\n\n\n<p>Below are the requirements for deploying Ceph storage cluster via cephadm;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Python 3<\/li>\n\n\n\n<li>Systemd<\/li>\n\n\n\n<li>Podman or <a href=\"#install-docker-ce-on-debian-12\">Docker for running containers<\/a> (<strong>we use docker in this setup<\/strong>)<\/li>\n\n\n\n<li><a href=\"https:\/\/kifarunix.com\/install-and-setup-ntp-server-on-debian-12-debian-11\/\" target=\"_blank\" rel=\"noreferrer noopener\">Time synchronization (such as chrony or NTP)<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/docs.ceph.com\/en\/latest\/ceph-volume\/lvm\/prepare\/\" target=\"_blank\" rel=\"noreferrer noopener\">LVM2<\/a> for provisioning storage devices. You can still use raw disks or raw paritions WITHOUT filesystem if you want.<\/li>\n<\/ul>\n\n\n\n<p>All the required dependencies are installed automatically by the bootstrap process.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"prepare-ceph-nodes-for-ceph-storage-cluster-deployment-on-debian-12\">Prepare Ceph Nodes for Ceph Storage Cluster Deployment on Debian 12<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"our-ceph-storage-cluster-deployment-architecture\">Our Ceph Storage Cluster Deployment Architecture<\/h4>\n\n\n\n<p>The diagram below depicts our ceph storage cluster deployment architecture. In a typical production environment, you would have at least 3 monitor nodes as well as at least 3 OSDs.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"720\" height=\"696\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/ceph-cluster-network-diagram-arch.png\" alt=\"\" class=\"wp-image-19354\" title=\"\"><\/figure>\n\n\n\n<p>If your cluster nodes are in the same network subnet, <strong>cephadm<\/strong> will automatically add up to five monitors to the subnet, as new hosts are added to the cluster.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"ceph-storage-nodes-hardware-requirements\">Ceph Storage Nodes Hardware Requirements<\/h4>\n\n\n\n<p>Check the <a href=\"https:\/\/docs.ceph.com\/en\/latest\/start\/hardware-recommendations\/\" target=\"_blank\" rel=\"noreferrer noopener\">hardware recommendations page<\/a> for the Ceph storage cluster nodes hardware requirements.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"create-ceph-deployment-user-account\">Create Ceph Deployment User Account<\/h4>\n\n\n\n<p>We will be deploying Ceph on Debian 12 using a root user account. So to follow along, ensure you have access to the root account on your Ceph cluster nodes. Bear in mind that root user account is a superuser account, hence, &#8220;With great power comes great responsibility&#8221;.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>whoami<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>root<\/code><\/pre>\n\n\n\n<p>If you would like to use non root user account to bootstrap Ceph cluster, <a href=\"https:\/\/docs.ceph.com\/en\/reef\/cephadm\/install\/#cephadm-bootstrap-further-info\" target=\"_blank\" rel=\"noreferrer noopener\">read more on the here<\/a>.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"attach-storage-disks-to-ceph-osd-nodes\">Attach Storage Disks to Ceph OSD Nodes<\/h4>\n\n\n<div class=\"gb-container gb-container-b2481987\">\n\n<p>Each Ceph OSD nodes in our architecture above has unallocated 3 raw disks, \/dev\/vd{a,b} of 50 GB each.<\/p>\n\n<\/div>\n\n\n<pre class=\"wp-block-code\"><code>lsblk<\/code><\/pre>\n\n\n\n<p>Sample output;<\/p>\n\n\n\n<pre class=\"scroll-box\"><code>NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS\nsda      8:0    0  100G  0 disk \n\u251c\u2500sda1   8:1    0   98G  0 part \/\n\u251c\u2500sda2   8:2    0    1K  0 part \n\u2514\u2500sda5   8:5    0    2G  0 part \nvda    253:0    0   50G  0 disk \nvdb    253:16   0   50G  0 disk \n<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"set-hostnames-and-update-hosts-file\">Set Hostnames and Update Hosts File<\/h4>\n\n\n\n<p>To begin with, setup up your nodes hostnames;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>hostnamectl set-hostname ceph-mgr-mon01<\/code><\/pre>\n\n\n\n<p><strong>Set the respective hostnames on other nodes.<\/strong><\/p>\n\n\n\n<p>If you are not using DNS for name resolution, then update the hosts file accordingly.<\/p>\n\n\n\n<p>For example, in our setup, each node hosts file should contain the lines below;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>less \/etc\/hosts<\/code><\/pre>\n\n\n\n<pre class=\"scroll-sz\"><code>...\n192.168.122.170 ceph-mgr-mon01\n192.168.122.127 ceph-mon02\n192.168.122.184 ceph-mon03\n192.168.122.188 ceph-osd01\n192.168.122.30 ceph-osd02\n192.168.122.51 ceph-osd03\n<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"set-time-synchronization\">Set Time Synchronization<\/h4>\n\n\n\n<p>Ensure that the time on <strong>all the nodes<\/strong> is synchronized. Thus install Chrony on each and set it up such that all nodes uses the same NTP server.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>apt install chrony -y<\/code><\/pre>\n\n\n\n<p>Edit the Chrony configuration and set your NTP server by replacing the NTP server pools with your NTP server address.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>vim \/etc\/chrony\/chrony.conf<\/code><\/pre>\n\n\n\n<p>Define your NTP Server. Replace <strong>ntp.kifarunix-demo.com<\/strong> with your respective NTP server address.<\/p>\n\n\n\n<pre class=\"scroll-sz\"><code>...\n#pool 2.debian.pool.ntp.org iburst\n<strong>pool ntp.kifarunix-demo.com iburst<\/strong>\n...\n<\/code><\/pre>\n\n\n\n<p>Restart Chronyd<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>systemctl restart chrony<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"install-ssh-server-on-each-node\">Install SSH Server on Each Node<\/h4>\n\n\n\n<p>Ceph deployment through cephadm utility requires that an SSH server is installed on all the nodes.<\/p>\n\n\n\n<p>Debian 12 comes with SSH server already installed. If not, install and start it as follows;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>apt install openssh-server<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>systemctl enable --now ssh<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"enable-root-login-on-other-nodes-from-ceph-admin-node\">Enable Root Login on Other Nodes from Ceph Admin Node<\/h4>\n\n\n\n<p>In order to add other nodes to the Ceph cluster using Ceph Admin Node, you will have to use the root user account.<\/p>\n\n\n\n<p>Thus, on the Ceph Monitor, Ceph OSD nodes, enable root login from the Ceph Admin node;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>vim \/etc\/ssh\/sshd_config<\/code><\/pre>\n\n\n\n<p>Add the configs below, replacing the IP address for Ceph Admin accordingly.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Match Address 192.168.122.170\n        PermitRootLogin yes<\/code><\/pre>\n\n\n\n<p>Reload ssh;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>systemctl reload sshd<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"install-python-3\">Install Python3<\/h4>\n\n\n\n<p>Python is required to deploy Ceph. Python 3 is installed by default on Debian 12;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>python3 -V<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>Python 3.11.2<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"install-docker-ce-on-each-node\">Install Docker CE on Each Node<\/h4>\n\n\n\n<p id=\"install-docker-on-each-osd-nodes\">The cephadm utility is used to bootstrap a Ceph cluster and to manage ceph daemons deployed with systemd and Docker containers.<\/p>\n\n\n\n<p>It can also use Podman, which will be installed along with other Ceph packages as can be seen in the later stages of this guide.<\/p>\n\n\n\n<p>To install Docker CE on each Ceph cluster node, follow the guide below;<\/p>\n\n\n\n<p><a href=\"https:\/\/kifarunix.com\/how-to-install-docker-ce-on-debian-12\/\" target=\"_blank\" rel=\"noreferrer noopener\">How to Install Docker CE on Debian 12<\/a><\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"install-lvm-package-on-each-node\">Install LVM Package on each Node<\/h4>\n\n\n\n<p>Ceph requires LVM2 for provisioning storage devices. Install the package on each node.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>apt install lvm2 -y<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"setup-ceph-storage-cluster-on-debian-12\">Setup Ceph Storage Cluster on Debian 12<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"install-cephadm-utility-on-ceph-admin-node\">Install&nbsp;<code>cephadm<\/code>&nbsp;Utility on Ceph Admin Node<\/h4>\n\n\n\n<p><strong>On the Ceph admin node<\/strong>, you need to install the cephadm utility.<\/p>\n\n\n\n<p><em><a href=\"https:\/\/docs.ceph.com\/en\/latest\/cephadm\/#cephadm\" target=\"_blank\" rel=\"noopener\">Cephadm<\/a>&nbsp;installs and manages a Ceph cluster using containers and systemd, with tight integration with the CLI and dashboard GUI.<\/em><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><em>cephadm only supports Octopus and newer releases.<\/em><\/li>\n\n\n\n<li><em>cephadm is fully integrated with the new orchestration API and fully supports the new CLI and dashboard features to manage cluster deployment.<\/em><\/li>\n\n\n\n<li><em>cephadm requires container support (podman or docker) and Python 3<\/em>.<\/li>\n<\/ul>\n\n\n\n<p>If you check the cephadm utility provided by the default repos, it is a lower version. The current version as of this writing is 18.2.0.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>apt-cache policy cephadm<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>cephadm:\n  Installed: (none)\n  Candidate: 16.2.11+ds-2\n  Version table:\n     16.2.11+ds-2 500\n        500 http:\/\/deb.debian.org\/debian bookworm\/main amd64 Packages\n<\/code><\/pre>\n\n\n\n<p>To install the current cephadm release version, you need the current Ceph release repos installed.<\/p>\n\n\n\n<p>To install Ceph release repos on Debian 12, run the commands below<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>wget -q -O- 'https:\/\/download.ceph.com\/keys\/release.asc' | \\\ngpg --dearmor -o \/etc\/apt\/trusted.gpg.d\/cephadm.gpg<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>echo deb https:\/\/download.ceph.com\/debian-reef\/ $(lsb_release -sc) main \\\n&gt; \/etc\/apt\/sources.list.d\/ceph.list<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>apt update<\/code><\/pre>\n\n\n\n<p>Then, check the available version of cephadm package now.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>apt-cache policy cephadm<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>cephadm:\n  Installed: (none)\n  Candidate: 18.2.1-1~bpo12+1\n  Version table:\n     18.2.1-1~bpo12+1 500\n        500 https:\/\/download.ceph.com\/debian-reef bookworm\/main amd64 Packages\n     16.2.11+ds-2 500\n        500 http:\/\/deb.debian.org\/debian bookworm\/main amd64 Packages\n<\/code><\/pre>\n\n\n\n<p>As you can see, the Ceph repo provides current release version of cephadm package. Thus, install it as follows;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>apt install cephadm<\/code><\/pre>\n\n\n\n<p>During the installation, you may see some errors relating to the cephadm user account that is being created. Since we are using root user account to bootstrap our Ceph cluster, then we ignore this error.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"initialize-ceph-cluster-monitor-on-ceph-admin-node\">Initialize Ceph Cluster Monitor On Ceph Admin Node<\/h3>\n\n\n\n<p>Your nodes are now ready to deploy a Ceph storage cluster.<\/p>\n\n\n\n<p>It is now time to bootstrap the Ceph cluster in order to create the first Ceph monitor daemon on Ceph admin node. Thus, run the command below, substituting the IP address with that of the <strong>Ceph admin node<\/strong> accordingly.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cephadm bootstrap --mon-ip 192.168.122.170<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>Creating directory \/etc\/ceph for ceph.conf\nVerifying podman|docker is present...\nVerifying lvm2 is present...\nVerifying time synchronization is in place...\nUnit chrony.service is enabled and running\nRepeating the final host check...\ndocker (\/usr\/bin\/docker) is present\nsystemctl is present\nlvcreate is present\nUnit chrony.service is enabled and running\nHost looks OK\nCluster fsid: 456f0baa-affa-11ee-be1c-525400575614\nVerifying IP 192.168.122.170 port 3300 ...\nVerifying IP 192.168.122.170 port 6789 ...\nMon IP `192.168.122.170` is in CIDR network `192.168.122.0\/24`\nMon IP `192.168.122.170` is in CIDR network `192.168.122.0\/24`\nInternal network (--cluster-network) has not been provided, OSD replication will default to the public_network\nPulling container image quay.io\/ceph\/ceph:v18...\nCeph version: ceph version 18.2.1 (7fe91d5d5842e04be3b4f514d6dd990c54b29c76) reef (stable)\nExtracting ceph user uid\/gid from container image...\nCreating initial keys...\nCreating initial monmap...\nCreating mon...\nWaiting for mon to start...\nWaiting for mon...\nmon is available\nAssimilating anything we can from ceph.conf...\nGenerating new minimal ceph.conf...\nRestarting the monitor...\nSetting public_network to 192.168.122.0\/24 in mon config section\nWrote config to \/etc\/ceph\/ceph.conf\nWrote keyring to \/etc\/ceph\/ceph.client.admin.keyring\nCreating mgr...\nVerifying port 0.0.0.0:9283 ...\nVerifying port 0.0.0.0:8765 ...\nVerifying port 0.0.0.0:8443 ...\nWaiting for mgr to start...\nWaiting for mgr...\nmgr not available, waiting (1\/15)...\nmgr not available, waiting (2\/15)...\nmgr not available, waiting (3\/15)...\nmgr is available\nEnabling cephadm module...\nWaiting for the mgr to restart...\nWaiting for mgr epoch 5...\nmgr epoch 5 is available\nSetting orchestrator backend to cephadm...\nGenerating ssh key...\nWrote public SSH key to \/etc\/ceph\/ceph.pub\nAdding key to root@localhost authorized_keys...\nAdding host ceph-mgr-mon01...\nDeploying mon service with default placement...\nDeploying mgr service with default placement...\nDeploying crash service with default placement...\nDeploying ceph-exporter service with default placement...\nDeploying prometheus service with default placement...\nDeploying grafana service with default placement...\nDeploying node-exporter service with default placement...\nDeploying alertmanager service with default placement...\nEnabling the dashboard module...\nWaiting for the mgr to restart...\nWaiting for mgr epoch 9...\nmgr epoch 9 is available\nGenerating a dashboard self-signed certificate...\nCreating initial admin user...\nFetching dashboard port number...\nCeph Dashboard is now available at:\n\n\t     URL: https:\/\/ceph-mgr-mon01:8443\/\n\t    User: admin\n\tPassword: 0lquv02zaw\n\nEnabling client.admin keyring and conf on hosts with \"admin\" label\nSaving cluster configuration to \/var\/lib\/ceph\/456f0baa-affa-11ee-be1c-525400575614\/config directory\nEnabling autotune for osd_memory_target\nYou can access the Ceph CLI as following in case of multi-cluster or non-default config:\n\n\tsudo \/usr\/sbin\/cephadm shell --fsid 456f0baa-affa-11ee-be1c-525400575614 -c \/etc\/ceph\/ceph.conf -k \/etc\/ceph\/ceph.client.admin.keyring\n\nOr, if you are only running a single cluster on this host:\n\n\tsudo \/usr\/sbin\/cephadm shell \n\nPlease consider enabling telemetry to help improve Ceph:\n\n\tceph telemetry on\n\nFor more information see:\n\n\thttps:\/\/docs.ceph.com\/en\/latest\/mgr\/telemetry\/\n\nBootstrap complete.\n<\/code><\/pre>\n\n\n\n<p>According to the documentation, the bootstrap command;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><em>Create a monitor and manager daemon for the new cluster on the localhost.<\/em><\/li>\n\n\n\n<li><em>Generate a new SSH key for the Ceph cluster and add it to the root user\u2019s&nbsp;<code>\/root\/.ssh\/authorized_keys<\/code>&nbsp;file.<\/em><\/li>\n\n\n\n<li><em>Write a copy of the public key to&nbsp;<code>\/etc\/ceph\/ceph.pub<\/code>.<\/em><\/li>\n\n\n\n<li><em>Write a minimal configuration file to&nbsp;<code>\/etc\/ceph\/ceph.conf<\/code>. This file is needed to communicate with the new cluster.<\/em><\/li>\n\n\n\n<li><em>Write a copy of the&nbsp;<code>client.admin<\/code>&nbsp;administrative (privileged!) secret key to&nbsp;<code>\/etc\/ceph\/ceph.client.admin.keyring<\/code>.<\/em><\/li>\n\n\n\n<li><em>Add the&nbsp;<code>_admin<\/code>&nbsp;label to the bootstrap host. By default, any host with this label will (also) get a copy of&nbsp;<code>\/etc\/ceph\/ceph.conf<\/code>&nbsp;and&nbsp;<code>\/etc\/ceph\/ceph.client.admin.keyring<\/code>.<\/em><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"enable-ceph-cli\">Enable Ceph CLI<\/h3>\n\n\n\n<p>When bootstrap command completes, a command for accessing Ceph CLI is provided. Execute that command to access Ceph CLI, in case of multi-cluster or non-default config:<\/p>\n\n\n\n<pre class=\"scroll-sz\"><code>sudo \/usr\/sbin\/cephadm shell \\\n\t--fsid 456f0baa-affa-11ee-be1c-525400575614 \\\n\t-c \/etc\/ceph\/ceph.conf \\\n\t-k \/etc\/ceph\/ceph.client.admin.keyring\n<\/code><\/pre>\n\n\n\n<p>Otherwise, for the default config, just execute;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo cephadm shell<\/code><\/pre>\n\n\n\n<p>This drops you onto Ceph CLI. You should see your shell prompt change!<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>root@ceph-mgr-mon01:\/#<\/code><\/pre>\n\n\n\n<p>You can run the ceph commands eg to check the Ceph status;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ceph -s<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>  cluster:\n    id:     456f0baa-affa-11ee-be1c-525400575614\n    health: HEALTH_WARN\n            OSD count 0 < osd_pool_default_size 3\n \n  services:\n    mon: 1 daemons, quorum ceph-mgr-mon01 (age 8m)\n    mgr: ceph-mgr-mon01.gioqld(active, since 7m)\n    osd: 0 osds: 0 up, 0 in\n \n  data:\n    pools:   0 pools, 0 pgs\n    objects: 0 objects, 0 B\n    usage:   0 B used, 0 B \/ 0 B avail\n    pgs:\n<\/code><\/pre>\n\n\n\n<p>You can exit the ceph CLI by pressing <strong>Ctrl+D<\/strong> or  type <strong>exit<\/strong> and press ENTER.<\/p>\n\n\n\n<p>There are other ways in which you can access the Ceph CLI. For example, you can run Ceph CLI commands using cephadm command.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cephadm shell -- ceph -s<\/code><\/pre>\n\n\n\n<p><em>Or You could install Ceph CLI tools on the host (ignore errors about cephadm user account);<\/em><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code><em>apt install ceph-common<\/em><\/code><\/pre>\n\n\n\n<p><em>With this method, then you can just ran the Ceph commands easily;<\/em><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code><em>ceph -s<\/em><\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"copy-ssh-keys-to-other-ceph-nodes\">Copy SSH Keys to Other Ceph Nodes<\/h3>\n\n\n\n<p>Copy the SSH key generated by the bootstrap command to Ceph Monitor, OSD1 and OSD2 root user account. Ensure Root Login is permitted on the Ceph monitor node.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>for i in ceph-mon02 ceph-mon03 ceph-osd01 ceph-osd02 ceph-osd03; do ssh-copy-id -f -i \/etc\/ceph\/ceph.pub root@$i; done<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"drop-into-ceph-cli\">Drop into Ceph CLI<\/h3>\n\n\n\n<p>You can drop into the Ceph CLI to execute the next commands.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cephadm shell<\/code><\/pre>\n\n\n\n<p>Or if you installed the ceph-common package, no need to drop into the cli as you can directly execute the ceph commands from the terminal.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"add-ceph-monitor-node-to-ceph-cluster\">Add Ceph Monitor Node to Ceph Cluster<\/h3>\n\n\n\n<p>At this point, we have just provisioned Ceph Admin node only. You can list all the hosts known to the Ceph ochestrator (ceph-mgr) using the command below<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ceph orch host ls<\/code><\/pre>\n\n\n\n<p>Sample output;<\/p>\n\n\n\n<pre class=\"scroll-sz\"><code>HOST            ADDR             LABELS  STATUS  \nceph-mgr-mon01  192.168.122.170  _admin          \n1 hosts in cluster\n<\/code><\/pre>\n\n\n\n<p>So next, add the Ceph Monitor node to the cluster.<\/p>\n\n\n\n<p>Assuming you have copied the Ceph SSH public key, execute the command below to add the Ceph Monitor to the cluster;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>for i in 02 03; do ceph orch host add ceph-mon$i; done<\/code><\/pre>\n\n\n\n<p>Sample command output;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Added host 'ceph-mon02' with addr '192.168.122.127'\nAdded host 'ceph-mon03' with addr '192.168.122.184'<\/code><\/pre>\n\n\n\n<p>Next, label the nodes as per their roles;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ceph orch host label add ceph-mgr-mon01 ceph-mgr-mon01<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>for i in 02 03; do ceph orch host label add ceph-mon$i mon$i; done<\/code><\/pre>\n\n\n\n<p>Kindly note that if you have 5 or more nodes (including OSD nodes and admin nodes in the cluster within the same network, a maximum of 5 noded will be automatically assigned monitor roles). If you have nodes in different networks, a minimum of three monitors is recommended!<\/p>\n\n\n\n<p>Similarly, there will be at least two managers deployed automatically.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"add-ceph-osd-nodes-to-ceph-cluster\">Add Ceph OSD Nodes to Ceph Cluster<\/h3>\n\n\n\n<p>Similarly, add the OSD Nodes to the cluster;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>for i in 01 02 03; do ceph orch host add ceph-osd$i; done<\/code><\/pre>\n\n\n\n<p>Define their respective labels;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>for i in 01 02 03; do ceph orch host label add ceph-osd$i osd$i; done<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"list-ceph-cluster-nodes\">List Ceph Cluster Nodes;<\/h3>\n\n\n\n<p>You can list the Ceph cluster nodes;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ceph orch host ls<\/code><\/pre>\n\n\n\n<p>Sample output;<\/p>\n\n\n\n<pre class=\"scroll-box\"><code>HOST            ADDR             LABELS                 STATUS  \nceph-mgr-mon01  192.168.122.170  _admin,ceph-mgr-mon01          \nceph-mon02      192.168.122.127  mon02                          \nceph-mon03      192.168.122.184  mon03                          \nceph-osd01      192.168.122.188  osd01                          \nceph-osd02      192.168.122.30   osd02                          \nceph-osd03      192.168.122.51   osd03                          \n6 hosts in cluster\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"create-ceph-os-ds-from-osd-nodes-drives\">Create Ceph OSDs from OSD Nodes Drives<\/h3>\n\n\n\n<p>To create a Ceph OSD from the OSD node logical volumes, run the command below.\u00a0<strong>Replace ceph-vg\/ceph-lv<\/strong>\u00a0with Volume group and logical volume names accordingly. Otherwise, use the raw device path.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo ceph orch daemon add osd ceph-mon:ceph-vg\/ceph-lv<\/code><\/pre>\n\n\n\n<p>Command output;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Created osd(s) 0 on host 'ceph-mon'<\/code><\/pre>\n\n\n\n<p>Repeat the same for the other OSD nodes.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo ceph orch daemon add osd ceph-osd1:ceph-vg\/ceph-lv<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo ceph orch daemon add osd ceph-osd2:ceph-vg\/ceph-lv<\/code><\/pre>\n\n\n\n<p>The Ceph OSDs are now ready for use.<\/p>\n\n\n\n<p>In our setup, we have unallocated raw storage devices  raw disks of 50G on each OSD node to be used as&nbsp;<a href=\"https:\/\/docs.ceph.com\/en\/reef\/rados\/configuration\/storage-devices\/#bluestore\" target=\"_blank\" rel=\"noreferrer noopener\">bluestore<\/a>&nbsp;for OSD daemons.<\/p>\n\n\n\n<p>You can list the devices that are available on the OSD nodes for creating OSDs using the command below;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ceph orch device ls<\/code><\/pre>\n\n\n\n<p>A storage device is considered&nbsp;<em>available<\/em>&nbsp;if all of the following conditions are met:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The device must have no partitions.<\/li>\n\n\n\n<li>The device must not have any LVM state.<\/li>\n\n\n\n<li>The device must not be mounted.<\/li>\n\n\n\n<li>The device must not contain a file system.<\/li>\n\n\n\n<li>The device must not contain a Ceph BlueStore OSD.<\/li>\n\n\n\n<li>The device must be larger than 5 GB.<\/li>\n<\/ul>\n\n\n\n<p>Sample output;<\/p>\n\n\n\n<pre class=\"scroll-box\"><code>HOST        PATH      TYPE  DEVICE ID   SIZE  AVAILABLE  REFRESHED  REJECT REASONS  \nceph-osd01  \/dev\/vda  hdd              50.0G  Yes        6m ago                     \nceph-osd01  \/dev\/vdb  hdd              50.0G  Yes        6m ago                     \nceph-osd02  \/dev\/vda  hdd              50.0G  Yes        5m ago                     \nceph-osd02  \/dev\/vdb  hdd              50.0G  Yes        5m ago                     \nceph-osd03  \/dev\/vda  hdd              50.0G  Yes        5m ago                     \nceph-osd03  \/dev\/vdb  hdd              50.0G  Yes        5m ago\n<\/code><\/pre>\n\n\n\n<p>You can add all the available devices to ceph OSDs at once or just add them one by one.<\/p>\n\n\n\n<p>To attach them all at once;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ceph orch apply osd --all-available-devices --method {raw|lvm}<\/code><\/pre>\n\n\n\n<p>Use raw method if you are using raw disks (like in our case here).<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ceph orch apply osd --all-available-devices --method raw<\/code><\/pre>\n\n\n\n<p>Otherwise, if you are using LVM volumes, use lvm method;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ceph orch apply osd --all-available-devices --method lvm<\/code><\/pre>\n\n\n\n<p>Command output;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Scheduled osd.all-available-devices update...<\/code><\/pre>\n\n\n\n<p>Note that when you add devices using this approach, then;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>If you add new disks to the cluster, they will be automatically used to create new OSDs.<\/li>\n\n\n\n<li>In the event that an OSD is removed, and the LVM physical volume is cleaned, a new OSD will be generated automatically.<\/li>\n<\/ul>\n\n\n\n<p>If you wish to prevent this behavior (i.e., disable the automatic creation of OSDs on available devices), use the 'unmanaged' parameter:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ceph orch apply osd --all-available-devices --unmanaged=true<\/code><\/pre>\n\n\n\n<p>To manually create an OSD from a specific device on a specific host:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ceph orch daemon add osd &lt;host&gt;:&lt;device-path&gt;<\/code><\/pre>\n\n\n\n<p>If you check again, the disks are now added to Ceph and not available for other use anymore;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ceph orch device ls<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>HOST        PATH      TYPE  DEVICE ID   SIZE  AVAILABLE  REFRESHED  REJECT REASONS              \nceph-osd01  \/dev\/vda  hdd              50.0G  No         10s ago    Has BlueStore device label  \nceph-osd01  \/dev\/vdb  hdd              50.0G  No         10s ago    Has BlueStore device label  \nceph-osd02  \/dev\/vda  hdd              50.0G  No         10s ago    Has BlueStore device label  \nceph-osd02  \/dev\/vdb  hdd              50.0G  No         10s ago    Has BlueStore device label  \nceph-osd03  \/dev\/vda  hdd              50.0G  No         10s ago    Has BlueStore device label  \nceph-osd03  \/dev\/vdb  hdd              50.0G  No         10s ago    Has BlueStore device label\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"check-ceph-cluster-health\">Check Ceph Cluster Health<\/h3>\n\n\n\n<p>To verify the health status of the ceph cluster, simply execute the command&nbsp;<code>ceph s<\/code>&nbsp;on the admin node or even on each OSD node (if you have installed cephadm\/ceph commands there).<\/p>\n\n\n\n<p>To check Ceph cluster health status from the admin node;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ceph -s<\/code><\/pre>\n\n\n\n<p>Sample output;<\/p>\n\n\n\n<pre class=\"scroll-box\"><code>  cluster:\n    id:     456f0baa-affa-11ee-be1c-525400575614\n    health: HEALTH_OK\n \n  services:\n    mon: 5 daemons, quorum ceph-mgr-mon01,ceph-mon02,ceph-mon03,ceph-osd01,ceph-osd03 (age 14m)\n    mgr: ceph-mgr-mon01.htboob(active, since 45m), standbys: ceph-mon02.wgbbcc\n    osd: 6 osds: 6 up (since 3m), 6 in (since 4m)\n \n  data:\n    pools:   1 pools, 1 pgs\n    objects: 2 objects, 577 KiB\n    usage:   160 MiB used, 300 GiB \/ 300 GiB avail\n    pgs:     1 active+clean\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"accessing-ceph-admin-web-user-interface\">Accessing Ceph Admin Web User Interface<\/h3>\n\n\n\n<p>The bootstrap commands give a url and credentials to use to access the Ceph admin web user interface;<\/p>\n\n\n\n<pre class=\"scroll-box\"><code>Ceph Dashboard is now available at:\n\n\t     URL: https:\/\/ceph-mgr-mon01:8443\/\n\t    User: admin\n\tPassword: 0lquv02zaw\n<\/code><\/pre>\n\n\n\n<p>Thus, open the browser and navigate to the URL above. Or you can use the cephadm node resolvable hostname or IP address if you want. Sample URL: <strong><code>https:\/\/ceph-mgr-mon01:8443<\/code><\/strong>.<\/p>\n\n\n\n<p><strong>Open the port, 8443\/TCP, on firewall if any is running.<\/strong><\/p>\n\n\n\n<p>Enter the provided credential and reset your admin password and proceed to login to Ceph Admin UI.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1383\" height=\"850\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/ceph-reef-18-login-page.png?v=1700079083\" alt=\"\" class=\"wp-image-19276\" title=\"\" srcset=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/ceph-reef-18-login-page.png?v=1700079083 1383w, https:\/\/kifarunix.com\/wp-content\/uploads\/2023\/11\/ceph-reef-18-login-page-768x472.png?v=1700079083 768w\" sizes=\"(max-width: 1383px) 100vw, 1383px\" \/><\/figure>\n\n\n\n<p>If you want, you can activate the <a href=\"https:\/\/docs.ceph.com\/en\/latest\/mgr\/telemetry\/#telemetry-module\" target=\"_blank\" rel=\"noreferrer noopener\">telemetry module<\/a> by clicking <strong>Activate<\/strong> button or just from the Ceph admin node CLI;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cephadm shell -- ceph telemetry on --license sharing-1-0<\/code><\/pre>\n\n\n\n<p>Go through other Ceph menu to see more about Ceph.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1911\" height=\"714\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2022\/02\/ceph-admin-UI.png\" alt=\"Deploy Ceph Storage Cluster on Debian 12\" class=\"wp-image-11665\" title=\"\" srcset=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2022\/02\/ceph-admin-UI.png?v=1645335335 1911w, https:\/\/kifarunix.com\/wp-content\/uploads\/2022\/02\/ceph-admin-UI-768x287.png?v=1645335335 768w, https:\/\/kifarunix.com\/wp-content\/uploads\/2022\/02\/ceph-admin-UI-1536x574.png?v=1645335335 1536w\" sizes=\"(max-width: 1911px) 100vw, 1911px\" \/><\/figure>\n\n\n\n<p>Ceph Dashboard;<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1622\" height=\"834\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2024\/01\/ceph-reef-18.2.1-dashboard.png?v=1704947079\" alt=\"\" class=\"wp-image-19750\" title=\"\" srcset=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2024\/01\/ceph-reef-18.2.1-dashboard.png?v=1704947079 1622w, https:\/\/kifarunix.com\/wp-content\/uploads\/2024\/01\/ceph-reef-18.2.1-dashboard-768x395.png?v=1704947079 768w, https:\/\/kifarunix.com\/wp-content\/uploads\/2024\/01\/ceph-reef-18.2.1-dashboard-1536x790.png?v=1704947079 1536w\" sizes=\"(max-width: 1622px) 100vw, 1622px\" \/><\/figure>\n\n\n\n<p>Under the Cluster Menu, you can see quite other details; hosts, disks, OSDs etc.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1613\" height=\"821\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2024\/01\/ceph-cluster-details.png?v=1704947132\" alt=\"\" class=\"wp-image-19751\" title=\"\" srcset=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2024\/01\/ceph-cluster-details.png?v=1704947132 1613w, https:\/\/kifarunix.com\/wp-content\/uploads\/2024\/01\/ceph-cluster-details-768x391.png?v=1704947132 768w, https:\/\/kifarunix.com\/wp-content\/uploads\/2024\/01\/ceph-cluster-details-1536x782.png?v=1704947132 1536w\" sizes=\"(max-width: 1613px) 100vw, 1613px\" \/><\/figure>\n\n\n\n<p>There you go. That marks the end of our tutorial on how to deploy Ceph storage cluster.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Follow through this post to learn how to deploy Ceph storage cluster on Debian 12. Ceph is a scalable distributed storage system designed for cloud<\/p>\n","protected":false},"author":10,"featured_media":19276,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_lock_modified_date":false,"footnotes":""},"categories":[39,1338,121],"tags":[7354,7353,7352,7351],"class_list":["post-19367","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-storage","category-ceph","category-howtos","tag-ceph-osd-2","tag-ceph-storage","tag-debian-12-ceph","tag-deploy-ceph-debian-12","generate-columns","tablet-grid-50","mobile-grid-100","grid-parent","grid-50","resize-featured-image"],"_links":{"self":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/19367"}],"collection":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/comments?post=19367"}],"version-history":[{"count":12,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/19367\/revisions"}],"predecessor-version":[{"id":22104,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/19367\/revisions\/22104"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/media\/19276"}],"wp:attachment":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/media?parent=19367"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/categories?post=19367"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/tags?post=19367"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}