Deploying a new Ceph Octopus cluster - Revision history

Admin at 11:44, 6 April 2021

2021-04-06T11:44:28Z

← Older revision		Revision as of 11:44, 6 April 2021
Line 96:		Line 96:
	# wipefs -a <device>		# wipefs -a <device>
	</pre>		</pre>

			== Source ==
			* [https://docs.ceph.com/en/octopus/cephadm/install/# Deploying a New Ceph Cluster]

Admin: /* Deploy osd's */

2021-04-06T09:48:15Z

Deploy osd's

← Older revision		Revision as of 09:48, 6 April 2021
Line 75:		Line 75:
	</pre>		</pre>
	What ceph considers as an "available disk":		What ceph considers as an "available disk":
	** The device must have no partitions.		* The device must have no partitions.
	** The device must not have any LVM state.		* The device must not have any LVM state.
	** The device must not be mounted.		* The device must not be mounted.
	** The device must not contain a file system.		* The device must not contain a file system.
	** The device must not contain a Ceph BlueStore OSD.		* The device must not contain a Ceph BlueStore OSD.
	** The device must be larger than 5 GB.		* The device must be larger than 5 GB.

	When comes the time to create the osd's (one osd per available drive), you have several possibilities. You can let ceph to create osd's for all available drives like this:		When comes the time to create the osd's (one osd per available drive), you have several possibilities. You can let ceph to create osd's for all available drives like this:

Admin: /* Deploy osd's */

2021-04-06T09:47:40Z

Deploy osd's

← Older revision		Revision as of 09:47, 6 April 2021
Line 75:		Line 75:
	</pre>		</pre>
	What ceph considers as an "available disk":		What ceph considers as an "available disk":
	* The device must have no partitions.		** The device must have no partitions.
	* The device must not have any LVM state.		** The device must not have any LVM state.
	* The device must not be mounted.		** The device must not be mounted.
	* The device must not contain a file system.		** The device must not contain a file system.
	* The device must not contain a Ceph BlueStore OSD.		** The device must not contain a Ceph BlueStore OSD.
	* The device must be larger than 5 GB.		** The device must be larger than 5 GB.

	When comes the time to create the osd's (one osd per available drive), you have several possibilities. You can let ceph to create osd's for all available drives like this:		When comes the time to create the osd's (one osd per available drive), you have several possibilities. You can let ceph to create osd's for all available drives like this:

Admin at 09:46, 6 April 2021

2021-04-06T09:46:38Z

@@ Line 38: / Line 38: @@
 # ceph orch host add ceph2.wn.iihe.ac.be
 # ceph orch host add ceph3.wn.iihe.ac.be
 </pre>

Admin: /* Before you start */

2021-04-06T09:39:39Z

Before you start

← Older revision		Revision as of 09:39, 6 April 2021
Line 7:		Line 7:
	</pre>		</pre>

	Yet another remark: when you run the command 'hostname' on the machines of our cluster, you get the FQDN of the machine, ie the name followed by the domain name. Ceph will always rely on this, meaning that when you need to specify the name of a machine in a Ceph command, you must always use the FQDN, and not the short name. That explains why we have to add the flag <pre>--allow</pre> in the ceph bootstrap command below.		Yet another remark: when you run the command 'hostname' on the machines of our cluster, you get the FQDN of the machine, ie the name followed by the domain name. Ceph will always rely on this, meaning that when you need to specify the name of a machine in a Ceph command, you must always use the FQDN, and not the short name. That explains why we have to add the flag <pre>--allow-fqdn-hostname</pre> in the ceph bootstrap command below.

	== Bootstrap a new cluster ==		== Bootstrap a new cluster ==

Admin: /* Before you start */

2021-04-06T09:39:13Z

Before you start

← Older revision		Revision as of 09:39, 6 April 2021
Line 7:		Line 7:
	</pre>		</pre>

	Yet another remark: when you run the command 'hostname' on the machines of our cluster, you get the FQDN of the machine, ie the name followed by the domain name. Ceph will always rely on this, meaning that when you need to specify the name of a machine in a Ceph command, you must always use the FQDN, and not the short name. That explains why we have to add the flag <pre>--allow</pre> ~~when we~~		Yet another remark: when you run the command 'hostname' on the machines of our cluster, you get the FQDN of the machine, ie the name followed by the domain name. Ceph will always rely on this, meaning that when you need to specify the name of a machine in a Ceph command, you must always use the FQDN, and not the short name. That explains why we have to add the flag <pre>--allow</pre> in the ceph bootstrap command below.

	== Bootstrap a new cluster ==		== Bootstrap a new cluster ==

Admin: /* Before you start */

2021-04-06T09:38:28Z

Before you start

← Older revision		Revision as of 09:38, 6 April 2021
Line 6:		Line 6:
	# cephadm shell		# cephadm shell
	</pre>		</pre>

			Yet another remark: when you run the command 'hostname' on the machines of our cluster, you get the FQDN of the machine, ie the name followed by the domain name. Ceph will always rely on this, meaning that when you need to specify the name of a machine in a Ceph command, you must always use the FQDN, and not the short name. That explains why we have to add the flag <pre>--allow</pre> when we

	== Bootstrap a new cluster ==		== Bootstrap a new cluster ==

Admin at 09:31, 6 April 2021

2021-04-06T09:31:23Z

← Older revision		Revision as of 09:31, 6 April 2021
Line 19:		Line 19:
	</pre>		</pre>
	Take note of the "admin" password that is generated, you'll need it to connect to the Ceph Dashboard.		Take note of the "admin" password that is generated, you'll need it to connect to the Ceph Dashboard.

			== Add other hosts to the cluster ==
			* The other nodes of the Ceph cluster must be installed with Quattor with the following include in their object template:
			<pre>
			include 'config/ceph/nodes';
			</pre>

			* Copy the ssh pubkey of the ceph adm in the authorized_keys of other hosts: do it with Quattor (see config/ceph/nodes)

			* Tell Ceph that new nodes are part of the cluster:
			<pre>
			# ceph orch host add <new_host>
			</pre>
			For example:
			<pre>
			# ceph orch host add ceph2.wn.iihe.ac.be
			# ceph orch host add ceph3.wn.iihe.ac.be
			</pre>

Admin: Created page with "== Before you start == Very important remark if you reinstall a ceph cluster: make sure to power off the nodes from a previous cluster deployment, otherwise the mon nodes will..."

2021-04-06T09:27:25Z

Created page with "== Before you start == Very important remark if you reinstall a ceph cluster: make sure to power off the nodes from a previous cluster deployment, otherwise the mon nodes will..."

New page

== Before you start ==
Very important remark if you reinstall a ceph cluster: make sure to power off the nodes from a previous cluster deployment, otherwise the mon nodes will spawn a mon on the first machine to reach the quorum and the boostrap will fail! (The other nodes are not aware that you reinstall a new cluster.)

Another important remark: for all the Ceph commands, you must type them in the ceph shell that you launch with:
<pre>
# cephadm shell
</pre>

== Bootstrap a new cluster ==
* Reinstall ceph1 that will be the ceph adm machine, ie the machine that will be used to bootstrap the ceph cluster and deploy all the other ceph node. The object template need contain the line:
<pre>
include 'config/ceph/adm';
</pre>

* Once the machine is quattor-installed, log in to it and do the following:
<pre>
# mkdir -p /etc/ceph
# cephadm bootstrap --mon-ip *<ceph1-ip>* --allow-fqdn-hostname
</pre>
Take note of the "admin" password that is generated, you'll need it to connect to the Ceph Dashboard.