Scale-out Block Setup (ceph) - Revision history

Qadmin: Link multi-admin approval to Security Configuration#Multi-admin Approvals

2026-09-28T16:40:50Z

Link multi-admin approval to Security Configuration#Multi-admin Approvals

← Older revision		Revision as of 16:40, 28 September 2026
Line 309:		Line 309:
	'''Modify Redundancy (CRUSH) Rule Selection''' -- reached by right-clicking the pool, since there is no toolbar button -- changes the '''Name''', '''Description''', '''Pool Layout''' and '''Redundancy Rule'''. '''Pool Type''' is displayed and permanently read-only, and the layout combo is disabled for an erasure pool: a replicated pool can be moved between Replica-3, 4 and 5, but a pool cannot be converted between replicated and erasure.		'''Modify Redundancy (CRUSH) Rule Selection''' -- reached by right-clicking the pool, since there is no toolbar button -- changes the '''Name''', '''Description''', '''Pool Layout''' and '''Redundancy Rule'''. '''Pool Type''' is displayed and permanently read-only, and the layout combo is disabled for an erasure pool: a replicated pool can be moved between Replica-3, 4 and 5, but a pool cannot be converted between replicated and erasure.

	'''Delete Block Storage Pool''' shows a read-only ''Storage Pool Information'' panel -- Scale-out Type, Data Pool Type, Storage Class, Object Count and Space Utilized -- and a '''Force (required when Scale-out Storage Pool is in use)''' checkbox. For a block pool the confirmation is explicit that this is not recoverable: ''"WARNING: All Scale-out Storage Volumes (RBDs) contained in the selected Storage Pool will be destroyed."'' For an erasure-coded pool, remember the second delete described under [[#What an erasure-coded block pool actually creates\|What an erasure-coded block pool actually creates]].		'''Delete Block Storage Pool''' shows a read-only ''Storage Pool Information'' panel -- Scale-out Type, Data Pool Type, Storage Class, Object Count and Space Utilized -- and a '''Force (required when Scale-out Storage Pool is in use)''' checkbox. For a block pool the confirmation is explicit that this is not recoverable: ''"WARNING: All Scale-out Storage Volumes (RBDs) contained in the selected Storage Pool will be destroyed."'' For an erasure-coded pool, remember the second delete described under [[#What an erasure-coded block pool actually creates\|What an erasure-coded block pool actually creates]]. Where [[Security Configuration#Multi-admin Approvals\|multi-admin approval]] covers block pool deletes, the delete is held until the required number of administrators approve it.

	== How the placement group count is chosen ==		== How the placement group count is chosen ==

Qadmin: Point at the renamed Encryption Bypass page directly rather than through the redirect - the feature is not Ceph-specific

2026-09-04T05:58:13Z

Point at the renamed Encryption Bypass page directly rather than through the redirect - the feature is not Ceph-specific

← Older revision		Revision as of 05:58, 4 September 2026
Line 133:		Line 133:
	* '''Enable Encryption''' -- unchecked by default. Ticking it enables the '''Encryption''' tab, which is otherwise disabled.		* '''Enable Encryption''' -- unchecked by default. Ticking it enables the '''Encryption''' tab, which is otherwise disabled.

	'''Encryption''' offers '''Software Encryption''' (dmcrypt/LUKS, the default mode) or '''Hardware Encryption''' (self-encrypting drives), and a '''Key Server Profile''' when keys are to be held off the appliance. Encryption is a cluster-wide property applied to every OSD built in the cluster; there is no per-OSD encryption control anywhere in the interface, and WAL and metadata-DB devices share their OSD's key. Where some devices already encrypt themselves and you do not want to double-encrypt them, see [[~~Ceph~~ Encryption Bypass]]. For how QuantaStor's software encryption and its key material work generally, see [[Software Encryption]].		'''Encryption''' offers '''Software Encryption''' (dmcrypt/LUKS, the default mode) or '''Hardware Encryption''' (self-encrypting drives), and a '''Key Server Profile''' when keys are to be held off the appliance. Encryption is a cluster-wide property applied to every OSD built in the cluster; there is no per-OSD encryption control anywhere in the interface, and WAL and metadata-DB devices share their OSD's key. Where some devices already encrypt themselves and you do not want to double-encrypt them, see [[Encryption Bypass]]. For how QuantaStor's software encryption and its key material work generally, see [[Software Encryption]].

	'''Advanced Settings''' carries the two OSD failure timers and a '''Domain Suffix''' field. The timers are described under [[#Monitoring cluster health\|Monitoring cluster health]] below.		'''Advanced Settings''' carries the two OSD failure timers and a '''Domain Suffix''' field. The timers are described under [[#Monitoring cluster health\|Monitoring cluster health]] below.
Line 609:		Line 609:
	* [[Fibre Channel Target Port Management]] -- presenting volumes over FC		* [[Fibre Channel Target Port Management]] -- presenting volumes over FC
	* [[Physical Disks/Devices]] -- disk discovery and per-disk operations		* [[Physical Disks/Devices]] -- disk discovery and per-disk operations
	* [[~~Ceph~~ Encryption Bypass]] -- excluding self-encrypting media from cluster encryption		* [[Encryption Bypass]] -- excluding self-encrypting media from cluster encryption
	* [[Ceph Cluster Import]] -- adopting an existing Ceph cluster		* [[Ceph Cluster Import]] -- adopting an existing Ceph cluster
	* [[Performance Monitoring]] -- watching the cluster under load		* [[Performance Monitoring]] -- watching the cluster under load

Qadmin: Note that deleting an erasure-coded block pool leaves its _ec_data pool behind and needs a second delete (QSTOR-12460, QSTOR-12352)

2026-09-03T08:45:31Z

Note that deleting an erasure-coded block pool leaves its _ec_data pool behind and needs a second delete (QSTOR-12460, QSTOR-12352)

← Older revision		Revision as of 08:45, 3 September 2026
Line 309:		Line 309:
	'''Modify Redundancy (CRUSH) Rule Selection''' -- reached by right-clicking the pool, since there is no toolbar button -- changes the '''Name''', '''Description''', '''Pool Layout''' and '''Redundancy Rule'''. '''Pool Type''' is displayed and permanently read-only, and the layout combo is disabled for an erasure pool: a replicated pool can be moved between Replica-3, 4 and 5, but a pool cannot be converted between replicated and erasure.		'''Modify Redundancy (CRUSH) Rule Selection''' -- reached by right-clicking the pool, since there is no toolbar button -- changes the '''Name''', '''Description''', '''Pool Layout''' and '''Redundancy Rule'''. '''Pool Type''' is displayed and permanently read-only, and the layout combo is disabled for an erasure pool: a replicated pool can be moved between Replica-3, 4 and 5, but a pool cannot be converted between replicated and erasure.

	'''Delete Block Storage Pool''' shows a read-only ''Storage Pool Information'' panel -- Scale-out Type, Data Pool Type, Storage Class, Object Count and Space Utilized -- and a '''Force (required when Scale-out Storage Pool is in use)''' checkbox. For a block pool the confirmation is explicit that this is not recoverable: ''"WARNING: All Scale-out Storage Volumes (RBDs) contained in the selected Storage Pool will be destroyed."''		'''Delete Block Storage Pool''' shows a read-only ''Storage Pool Information'' panel -- Scale-out Type, Data Pool Type, Storage Class, Object Count and Space Utilized -- and a '''Force (required when Scale-out Storage Pool is in use)''' checkbox. For a block pool the confirmation is explicit that this is not recoverable: ''"WARNING: All Scale-out Storage Volumes (RBDs) contained in the selected Storage Pool will be destroyed."'' For an erasure-coded pool, remember the second delete described under [[#What an erasure-coded block pool actually creates\|What an erasure-coded block pool actually creates]].

	== How the placement group count is chosen ==		== How the placement group count is chosen ==
Line 352:		Line 352:

	Measured on the same four-node cluster, {{Code\|1=K=2}} + {{Code\|1=M=2}} produced an {{Code\|1=_ec_data}} pool at {{Code\|1=size 4 min_size 3}} with 128 PGs and the companion replicated pool at {{Code\|1=size 3 min_size 2}} with 128 PGs.		Measured on the same four-node cluster, {{Code\|1=K=2}} + {{Code\|1=M=2}} produced an {{Code\|1=_ec_data}} pool at {{Code\|1=size 4 min_size 3}} with 128 PGs and the companion replicated pool at {{Code\|1=size 3 min_size 2}} with 128 PGs.

			'''Deleting an erasure-coded block pool takes two operations.''' Deleting the pool by its plain name removes only the replicated half; the {{Code\|1=_ec_data}} pool is left behind, still holding its placement groups, and has to be deleted separately. After deleting an erasure-coded block pool, check the Scale-out Storage Pools grid for a leftover {{Code\|1=<name>_ec_data}} row and delete that too. Tracked as QSTOR-12460.

	== Provisioning Storage Volumes ==		== Provisioning Storage Volumes ==

Qadmin: Rewrite from the product for 6.9: full Create OSDs & Journals / Create Scale-out Storage Pool / cluster dialog coverage, PG formula, journal group removal rules, safe OSD removal, multipath presentation. Corrects Replica-2, auto-K/M, MDB sizes, journal-partition checkbox label and the Resource-Domain CRUSH claim; drops unsourced cluster/node limits (QSTOR-12352)

2026-09-03T08:39:17Z

Rewrite from the product for 6.9: full Create OSDs & Journals / Create Scale-out Storage Pool / cluster dialog coverage, PG formula, journal group removal rules, safe OSD removal, multipath presentation. Corrects Replica-2, auto-K/M, MDB sizes, journal-partition checkbox label and the Resource-Domain CRUSH claim; drops unsourced cluster/node limits (QSTOR-12352)

Show changes

Qadmin: /* Provisioning Scale-out Storage Volumes (Ceph RBDs) */

2023-12-11T19:15:38Z

Provisioning Scale-out Storage Volumes (Ceph RBDs)

← Older revision		Revision as of 19:15, 11 December 2023
Line 64:		Line 64:

	[[File:Create Strg Pool - Web.jpg\|1024px]]		[[File:Create Strg Pool - Web.jpg\|1024px]]

			'''Navigation:''' Storage Management --> Storage Pools --> Storage Pool --> Create (toolbar)

	= Management and Operation =		= Management and Operation =

Qadmin: /* Create the Scale-out Storage Pools (Ceph Pools) */

2023-12-07T19:15:05Z

Create the Scale-out Storage Pools (Ceph Pools)

← Older revision		Revision as of 19:15, 7 December 2023
Line 44:		Line 44:

	For the purpose of this guide, we will be specifically creating a ''Block Storage'' pool. To do so, make sure that you click on ''Create Block Storage Pool'' in the ''Block Storage'' category of the ribbon bar.		For the purpose of this guide, we will be specifically creating a ''Block Storage'' pool. To do so, make sure that you click on ''Create Block Storage Pool'' in the ''Block Storage'' category of the ribbon bar.

			'''Navigation:''' Scale-out Storage Configuration --> Scale-out Storage Pools --> Block Storage --> Create Block Storage Pool ''(toolbar)''

	[[File:Crt Scale-out Strg Pool.jpg\|512px]]		[[File:Crt Scale-out Strg Pool.jpg\|512px]]

Qadmin: /* Provisioning Scale-out Storage Volumes (Ceph RBDs) */

2023-04-11T19:26:45Z

Provisioning Scale-out Storage Volumes (Ceph RBDs)

← Older revision		Revision as of 19:26, 11 April 2023
Line 61:		Line 61:
	To create a new storage volume for Scale-out storage, navigate to ''Storage Management''. From there click on ''Storage Volumes'', which will bring up the ''Storage Volume'' category in the ribbon bar. Click on ''Create''. The dialog for creating a storage volume will appear. In this dialog, it's important to make sure that the storage volume is going to be created from the correct pool. You can double check this in the ''Storage Pool'' field. After everything is filled out press ''OK'' and the new volume will be created.		To create a new storage volume for Scale-out storage, navigate to ''Storage Management''. From there click on ''Storage Volumes'', which will bring up the ''Storage Volume'' category in the ribbon bar. Click on ''Create''. The dialog for creating a storage volume will appear. In this dialog, it's important to make sure that the storage volume is going to be created from the correct pool. You can double check this in the ''Storage Pool'' field. After everything is filled out press ''OK'' and the new volume will be created.

	[[File:Create ~~Storage~~ Pool - Web.jpg\|1024px]]		[[File:Create Strg Pool - Web.jpg\|1024px]]

	= Management and Operation =		= Management and Operation =

Qadmin: /* Provisioning Scale-out Storage Volumes (Ceph RBDs) */

2023-04-11T19:26:16Z

Provisioning Scale-out Storage Volumes (Ceph RBDs)

← Older revision		Revision as of 19:26, 11 April 2023
Line 61:		Line 61:
	To create a new storage volume for Scale-out storage, navigate to ''Storage Management''. From there click on ''Storage Volumes'', which will bring up the ''Storage Volume'' category in the ribbon bar. Click on ''Create''. The dialog for creating a storage volume will appear. In this dialog, it's important to make sure that the storage volume is going to be created from the correct pool. You can double check this in the ''Storage Pool'' field. After everything is filled out press ''OK'' and the new volume will be created.		To create a new storage volume for Scale-out storage, navigate to ''Storage Management''. From there click on ''Storage Volumes'', which will bring up the ''Storage Volume'' category in the ribbon bar. Click on ''Create''. The dialog for creating a storage volume will appear. In this dialog, it's important to make sure that the storage volume is going to be created from the correct pool. You can double check this in the ''Storage Pool'' field. After everything is filled out press ''OK'' and the new volume will be created.

	[[File:~~Ceph~~-~~Volume~~.~~png~~\|~~920px\|Creating a new volume~~]]		[[File:Create Storage Pool - Web.jpg\|1024px]]

	= Management and Operation =		= Management and Operation =

Qadmin: /* Create the Scale-out Storage Pools (Ceph Pools) */

2023-04-11T19:02:20Z

Create the Scale-out Storage Pools (Ceph Pools)

← Older revision		Revision as of 19:02, 11 April 2023
Line 45:		Line 45:
	For the purpose of this guide, we will be specifically creating a ''Block Storage'' pool. To do so, make sure that you click on ''Create Block Storage Pool'' in the ''Block Storage'' category of the ribbon bar.		For the purpose of this guide, we will be specifically creating a ''Block Storage'' pool. To do so, make sure that you click on ''Create Block Storage Pool'' in the ''Block Storage'' category of the ribbon bar.

	[[File:~~Create~~ Scale-out Strg Pool.jpg\|512px]]		[[File:Crt Scale-out Strg Pool.jpg\|512px]]

	* Ceph Cluster: Select the appropriate cluster if the Grid includes multiple Ceph Clusters		* Ceph Cluster: Select the appropriate cluster if the Grid includes multiple Ceph Clusters

Qadmin: /* Create the Scale-out Storage Pools (Ceph Pools) */

2023-04-11T19:01:42Z

Create the Scale-out Storage Pools (Ceph Pools)

← Older revision		Revision as of 19:01, 11 April 2023
Line 45:		Line 45:
	For the purpose of this guide, we will be specifically creating a ''Block Storage'' pool. To do so, make sure that you click on ''Create Block Storage Pool'' in the ''Block Storage'' category of the ribbon bar.		For the purpose of this guide, we will be specifically creating a ''Block Storage'' pool. To do so, make sure that you click on ''Create Block Storage Pool'' in the ''Block Storage'' category of the ribbon bar.

	[[File:Create Scale-out ~~Storage~~ Pool.jpg\|512px]]		[[File:Create Scale-out Strg Pool.jpg\|512px]]

	* Ceph Cluster: Select the appropriate cluster if the Grid includes multiple Ceph Clusters		* Ceph Cluster: Select the appropriate cluster if the Grid includes multiple Ceph Clusters