Template:About Ceph - Revision history

Qadmin: /* Ceph CRUSH Maps and Resource Domains */

2024-01-16T20:43:52Z

Ceph CRUSH Maps and Resource Domains

← Older revision		Revision as of 20:43, 16 January 2024
Line 64:		Line 64:
	Ceph supports the ability to organize placement groups, which provide data mirroring across OSDs, so that high-availability and fault-tolerance can be maintained even in the event of a rack or site outage. By defining ''failure-domains'', such as a Rack of systems, a Site, or Building, a map can be created so that Placement Groups are intelligently laid out to ensure high-availability despite the outage of one or more failure-domains, depending on the level of redundancy.		Ceph supports the ability to organize placement groups, which provide data mirroring across OSDs, so that high-availability and fault-tolerance can be maintained even in the event of a rack or site outage. By defining ''failure-domains'', such as a Rack of systems, a Site, or Building, a map can be created so that Placement Groups are intelligently laid out to ensure high-availability despite the outage of one or more failure-domains, depending on the level of redundancy.

	This intelligent map is called the '''Ceph CRUSH map''', standing for Controlled, Scalable, Decentralized Placement of Replicated Data, and it defines how to mirror data in the Ceph cluster to ensure optimal performance and availability.		This intelligent map is called the '''Ceph CRUSH map''' ('''C'''ontrolled '''R'''eplication '''U'''nder '''S'''calable '''H'''ashing), standing for Controlled, Scalable, Decentralized Placement of Replicated Data, and it defines how to mirror data in the Ceph cluster to ensure optimal performance and availability.

	Creating CRUSH maps manually can be a complex process, so QuantaStor creates and configures CRUSH maps automatically, saving a large degree of administrative overhead. To facilitate automatic CRUSH map management, detail regarding where each QuantaStor system is deployed must be provided. This is done by creating a tree of ''Resource Domains'' via the WebUI (or via CLI/REST APIs) to organize the systems in a given QuantaStor Grid into Racks, Sites, and Buildings. QuantaStor uses this information to automatically generate an optimal CRUSH map when pools are provisioned, ensuring optimal performance and high-availability.		Creating CRUSH maps manually can be a complex process, so QuantaStor creates and configures CRUSH maps automatically, saving a large degree of administrative overhead. To facilitate automatic CRUSH map management, detail regarding where each QuantaStor system is deployed must be provided. This is done by creating a tree of ''Resource Domains'' via the WebUI (or via CLI/REST APIs) to organize the systems in a given QuantaStor Grid into Racks, Sites, and Buildings. QuantaStor uses this information to automatically generate an optimal CRUSH map when pools are provisioned, ensuring optimal performance and high-availability.

Qadmin: /* Ceph Object Storage Daemon / OSD */

2024-01-16T20:24:52Z

Ceph Object Storage Daemon / OSD

← Older revision		Revision as of 20:24, 16 January 2024
Line 30:		Line 30:
	QuantaStor Scale-out SAN with Ceph deployments must have at least 3x OSDs per system, making 9x OSDs total the minimum number OSDs. QuantaStor 5 and newer versions use the BlueStore OSD storage back-end. For additional BlueStore information see, [https://ceph.io/community/new-luminous-bluestore/ New in Luminous: BlueStore.]		QuantaStor Scale-out SAN with Ceph deployments must have at least 3x OSDs per system, making 9x OSDs total the minimum number OSDs. QuantaStor 5 and newer versions use the BlueStore OSD storage back-end. For additional BlueStore information see, [https://ceph.io/community/new-luminous-bluestore/ New in Luminous: BlueStore.]

	'''N.B.,''' for ease of use ~~their~~ is an Auto Config button that will optimize selection of available devices.		'''N.B.,''' for ease of use there is an Auto Config button that will optimize selection of available devices.

	== Journal Groups ==		== Journal Groups ==

Qadmin: /* Ceph Object Storage Daemon / OSD */

2024-01-16T20:24:23Z

Ceph Object Storage Daemon / OSD

← Older revision		Revision as of 20:24, 16 January 2024
Line 29:		Line 29:

	QuantaStor Scale-out SAN with Ceph deployments must have at least 3x OSDs per system, making 9x OSDs total the minimum number OSDs. QuantaStor 5 and newer versions use the BlueStore OSD storage back-end. For additional BlueStore information see, [https://ceph.io/community/new-luminous-bluestore/ New in Luminous: BlueStore.]		QuantaStor Scale-out SAN with Ceph deployments must have at least 3x OSDs per system, making 9x OSDs total the minimum number OSDs. QuantaStor 5 and newer versions use the BlueStore OSD storage back-end. For additional BlueStore information see, [https://ceph.io/community/new-luminous-bluestore/ New in Luminous: BlueStore.]

			'''N.B.,''' for ease of use their is an Auto Config button that will optimize selection of available devices.

	== Journal Groups ==		== Journal Groups ==

Qadmin: /* Ceph Terminology & Concepts */

2023-12-13T19:47:10Z

Ceph Terminology & Concepts

← Older revision		Revision as of 19:47, 13 December 2023
Line 2:		Line 2:

	This section will introduce Ceph terms and concepts to familiarize oneself with to become more proficient with Ceph Cluster administration in QuantaStor. This discussion will address general concepts surrounding Ceph. To implement Ceph in QuantaStor it is recommended to see '''Getting Started''' to quickly implement Ceph. '''Getting Started''' can be found at Storage Management --> Storage System --> Storage System --> Getting Started (toolbar).		This section will introduce Ceph terms and concepts to familiarize oneself with to become more proficient with Ceph Cluster administration in QuantaStor. This discussion will address general concepts surrounding Ceph. To implement Ceph in QuantaStor it is recommended to see '''Getting Started''' to quickly implement Ceph. '''Getting Started''' can be found at Storage Management --> Storage System --> Storage System --> Getting Started (toolbar).

			[https://wiki.osnexus.com/index.php?title=%2B_Getting_Started_Overview Getting Started in Administration guide.]

	[https://docs.ceph.com/en/latest/start/intro/ Further Information: Introduction to Ceph].		[https://docs.ceph.com/en/latest/start/intro/ Further Information: Introduction to Ceph].

Qadmin: /* Hardware RAID */

2023-12-08T17:22:32Z

Hardware RAID

← Older revision		Revision as of 17:22, 8 December 2023
Line 49:		Line 49:

	== Hardware RAID ==		== Hardware RAID ==
	Although Hardware RAID may be used in Ceph Clusters as an underlying storage abstraction for OSDs '''it is generally not recommended'''. It does have applications in very large Ceph clusters (ie. 1000s of OSDs) and with clusters comprised of servers with limited RAM and CPU core count. Roughly speaking each OSD requires approximately 2GB of RAM and a 1GHz fractional CPU core. A server with 60x HDD based OSDs will require a large dual-processor configuration and 192GB of RAM. By combining disks using HW RAID these requirements are reduced 5:1. QuantaStor does have integrated hardware RAID management and monitoring to manage configurations that use hardware RAID. But again, we do not recommend the use of HW RAID except in specialized configurations and in hyper-scale configurations.		Although Hardware RAID may be used in Ceph Clusters as an underlying storage abstraction for OSDs '''it is generally not recommended'''. It does have applications in very large Ceph clusters (ie. 1000s of OSDs) and with clusters comprised of servers with limited RAM and CPU core count. Roughly speaking each OSD requires approximately 2GB of RAM and a 1GHz fractional CPU core. A server with 60x HDD based OSDs will require a large dual-processor configuration and 192GB of RAM. By combining disks using HW RAID these requirements are reduced 5:1. QuantaStor does have integrated hardware RAID management and monitoring to manage configurations that use hardware RAID. But again, '''we do not recommend the use of HW RAID except in specialized configurations and in hyper-scale configurations'''.

	== Ceph Placement Groups (PGs) ==		== Ceph Placement Groups (PGs) ==

Qadmin: /* Ceph Object Storage Daemon / OSD */

2023-12-08T17:14:02Z

Ceph Object Storage Daemon / OSD

← Older revision		Revision as of 17:14, 8 December 2023
Line 24:		Line 24:
	'''Navigation:''' Scale-out Storage Configuration --> Data & Journal Devices --> Data & Journal Devices --> Create OSDs & Journals ''(toolbar)''		'''Navigation:''' Scale-out Storage Configuration --> Data & Journal Devices --> Data & Journal Devices --> Create OSDs & Journals ''(toolbar)''

	The Ceph '''Object Storage Daemon''', known as the OSD, is a daemon process that reads and writes data and generally maps 1-to-1 to a HDD or a SSD device. OSD devices may be used by multiple Storage Pools so after the OSDs are added one my allocate pools for file, block, and object storage which all use the available OSDs in the cluster to store their data.		The Ceph '''Object Storage Daemon''', known as the OSD, is a daemon process that reads and writes data and generally maps 1-to-1 to a HDD or a SSD device. OSD devices may be used by multiple Storage Pools so after the OSDs are added one may allocate pools for file, block, and object storage which all use the available OSDs in the cluster to store their data.

	QuantaStor Scale-out SAN with Ceph deployments must have at least 3x OSDs per system, making 9x OSDs total the minimum number OSDs. QuantaStor 5 and newer versions use the BlueStore OSD storage back-end. For additional BlueStore information see, [https://ceph.io/community/new-luminous-bluestore/ New in Luminous: BlueStore.]		QuantaStor Scale-out SAN with Ceph deployments must have at least 3x OSDs per system, making 9x OSDs total the minimum number OSDs. QuantaStor 5 and newer versions use the BlueStore OSD storage back-end. For additional BlueStore information see, [https://ceph.io/community/new-luminous-bluestore/ New in Luminous: BlueStore.]

Qadmin: /* Ceph Terminology & Concepts */

2023-12-07T20:11:52Z

Ceph Terminology & Concepts

← Older revision		Revision as of 20:11, 7 December 2023
Line 3:		Line 3:
	This section will introduce Ceph terms and concepts to familiarize oneself with to become more proficient with Ceph Cluster administration in QuantaStor. This discussion will address general concepts surrounding Ceph. To implement Ceph in QuantaStor it is recommended to see '''Getting Started''' to quickly implement Ceph. '''Getting Started''' can be found at Storage Management --> Storage System --> Storage System --> Getting Started (toolbar).		This section will introduce Ceph terms and concepts to familiarize oneself with to become more proficient with Ceph Cluster administration in QuantaStor. This discussion will address general concepts surrounding Ceph. To implement Ceph in QuantaStor it is recommended to see '''Getting Started''' to quickly implement Ceph. '''Getting Started''' can be found at Storage Management --> Storage System --> Storage System --> Getting Started (toolbar).

	[https://docs.ceph.com/en/latest/start/intro/ Introduction to Ceph].		[https://docs.ceph.com/en/latest/start/intro/ Further Information: Introduction to Ceph].

	== Ceph Cluster ==		== Ceph Cluster ==

Qadmin: /* Ceph Terminology & Concepts */

2023-12-07T20:11:17Z

Ceph Terminology & Concepts

← Older revision		Revision as of 20:11, 7 December 2023
Line 3:		Line 3:
	This section will introduce Ceph terms and concepts to familiarize oneself with to become more proficient with Ceph Cluster administration in QuantaStor. This discussion will address general concepts surrounding Ceph. To implement Ceph in QuantaStor it is recommended to see '''Getting Started''' to quickly implement Ceph. '''Getting Started''' can be found at Storage Management --> Storage System --> Storage System --> Getting Started (toolbar).		This section will introduce Ceph terms and concepts to familiarize oneself with to become more proficient with Ceph Cluster administration in QuantaStor. This discussion will address general concepts surrounding Ceph. To implement Ceph in QuantaStor it is recommended to see '''Getting Started''' to quickly implement Ceph. '''Getting Started''' can be found at Storage Management --> Storage System --> Storage System --> Getting Started (toolbar).

	[~~https:~~https://docs.ceph.com/en/latest/start/intro/ Introduction to Ceph].		[https://docs.ceph.com/en/latest/start/intro/ Introduction to Ceph].

	== Ceph Cluster ==		== Ceph Cluster ==

Qadmin: /* Ceph Terminology & Concepts */

2023-12-07T20:10:38Z

Ceph Terminology & Concepts

← Older revision		Revision as of 20:10, 7 December 2023
Line 2:		Line 2:

	This section will introduce Ceph terms and concepts to familiarize oneself with to become more proficient with Ceph Cluster administration in QuantaStor. This discussion will address general concepts surrounding Ceph. To implement Ceph in QuantaStor it is recommended to see '''Getting Started''' to quickly implement Ceph. '''Getting Started''' can be found at Storage Management --> Storage System --> Storage System --> Getting Started (toolbar).		This section will introduce Ceph terms and concepts to familiarize oneself with to become more proficient with Ceph Cluster administration in QuantaStor. This discussion will address general concepts surrounding Ceph. To implement Ceph in QuantaStor it is recommended to see '''Getting Started''' to quickly implement Ceph. '''Getting Started''' can be found at Storage Management --> Storage System --> Storage System --> Getting Started (toolbar).

			[https:https://docs.ceph.com/en/latest/start/intro/ Introduction to Ceph].

	== Ceph Cluster ==		== Ceph Cluster ==

Qadmin: /* Ceph Object Storage Daemon / OSD */

2023-12-07T20:03:19Z

Ceph Object Storage Daemon / OSD

← Older revision		Revision as of 20:03, 7 December 2023
Line 20:		Line 20:
	[[File:Create OSDs & Journals - OSD Devices.jpg\|712px]] [[File:Create OSDs & Journals - Journal Devices.jpg.jpg\|712px]]		[[File:Create OSDs & Journals - OSD Devices.jpg\|712px]] [[File:Create OSDs & Journals - Journal Devices.jpg.jpg\|712px]]

	'''Navigation:''' Scale-out Storage Configuration --> Data & Journal Devices --> Create OSDs & Journals ''(toolbar)''		'''Navigation:''' Scale-out Storage Configuration --> Data & Journal Devices --> Data & Journal Devices --> Create OSDs & Journals ''(toolbar)''

	The Ceph '''Object Storage Daemon''', known as the OSD, is a daemon process that reads and writes data and generally maps 1-to-1 to a HDD or a SSD device. OSD devices may be used by multiple Storage Pools so after the OSDs are added one my allocate pools for file, block, and object storage which all use the available OSDs in the cluster to store their data.		The Ceph '''Object Storage Daemon''', known as the OSD, is a daemon process that reads and writes data and generally maps 1-to-1 to a HDD or a SSD device. OSD devices may be used by multiple Storage Pools so after the OSDs are added one my allocate pools for file, block, and object storage which all use the available OSDs in the cluster to store their data.