Template:SetupStep CephRequirements: Difference between revisions

From OSNEXUS Online Documentation Site
Jump to navigation Jump to search
← Older edit
VisualWikitext
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Requirements Before Getting Started ==
== Requirements Before Getting Started ==


To achieve quorum a minimum of three systems are required.  The storage provided by the system can be SAS or SATA HDD or SSDs but a minimum of 1x SSD is required for use as a journal (write log) device in each system.  Systems must use a hardware RAID controller for QuantaStor boot/system devices and we recommend using a hardware RAID controller for the storage pools as well.
* 3x QuantaStor servers minimum
 
** Dual Intel or AMD CPUs
* 3x QuantaStor servers minimum (up to 64x Systems)
** 96 GB RAM
** Dual Intel Xeon or AMD Opteron CPU
** 2x SSDs in hardware RAID1 (boot/system)
** 128 GB RAM
** 4x or more SSDs/HDDs for OSD data devices per server
** 1x 375GB or larger high write endurance SSD/NVMe/NVRAM/Optane device for use as Journal Device
** 2x SSDs per server for Journal Groups (only required for HDD based OSD systems)
** 5x to 100x HDDs or SSD for data storage per system
** NTP / Time Synchronization
** Separate Networks for iSCSI and Ceph communication


=== Front-end / Back-end Network Configuration ===
=== Front-end / Back-end Network Configuration ===


Networking for scale-out file and block storage deployments use a separate front-end and back-end network to separate the client communication to the front-end network ports (S3/SWIFT, iSCSI/RBD) from the inter-node Ceph communication on the back-end.  This not only boosts performance, it increases the fault-tolerance, reliability and maintainability of the Ceph cluster. 
Network configuration for Ceph Clusters may use separate front-end and back-end networks.  Depending on the protocols to be used it can sometimes be easier and simpler to configure a given Ceph Cluster with a single subnet for both the front-end/public network and the back-end/cluster network communication.  With 100GbE and faster networks it is more common to deploy a single network configured for all cluster traffic.   
 
All nodes should have one or more ports designated as front-end ports and assigned IP address and subnet masks specifically for client access. One can have multiple physical, virtual IPs, and VLANs used on the front-end network to enable a variety of clients to access the storage.  The back-end network ports should all be physical ports but it is not required.   


A basic configuration Ceph network configuration:
[[File:qs4_front_back_network_ports.png|1024px]]
[[File:qs4_front_back_network_ports.png|1024px]]

Latest revision as of 07:08, 28 July 2020

Requirements Before Getting Started

  • 3x QuantaStor servers minimum
    • Dual Intel or AMD CPUs
    • 96 GB RAM
    • 2x SSDs in hardware RAID1 (boot/system)
    • 4x or more SSDs/HDDs for OSD data devices per server
    • 2x SSDs per server for Journal Groups (only required for HDD based OSD systems)

Front-end / Back-end Network Configuration

Network configuration for Ceph Clusters may use separate front-end and back-end networks. Depending on the protocols to be used it can sometimes be easier and simpler to configure a given Ceph Cluster with a single subnet for both the front-end/public network and the back-end/cluster network communication. With 100GbE and faster networks it is more common to deploy a single network configured for all cluster traffic.

Retrieved from "https://wiki.osnexus.com/index.php?title=Template:SetupStep_CephRequirements&oldid=18107"