Deployment requirements
This information details important hardware, software, and network requirements that are needed for deploying a generalized stretch cluster configuration for three availability zones.
Software requirements
IBM Storage Ceph 9.9.0
Hardware requirements
Use the following minimum hardware requirements before deploying a stretch cluster configuration.
| Hardware criteria | Minimum and recommended |
|---|---|
| Processor |
|
| RAM |
|
| Network | A single 1 Gb/s (bonded 10+ Gb/s recommended). The network latency between the two data sites should be less than 10ms. |
| Hardware criteria | Minimum and recommended |
|---|---|
| Processor | 2 cores minimum |
| Storage drives | 100 GB per daemon. SSD is recommended. |
| Network | A single 1 Gb/s (10+ Gb/s recommended) |
| Hardware criteria | Minimum and recommended |
|---|---|
| Processor | 2 cores minimum |
| RAM | 2 GB per daemon (more for production) |
| Disk space | 1 GB per daemon |
| Network | A single 1 Gb/s (10+ Gb/s recommended) |
Daemon placement
Table 4 lists the daemon placement details across various hosts and data centers.
| Hostname | Data center | Services |
|---|---|---|
| host01 | DC1 | OSD+MON+MGR |
| host02 | DC1 | OSD+MON+MGR |
| host03 | DC1 | OSD+MDS+RGW |
| host04 | DC2 | OSD+MON+MGR |
| host05 | DC2 | OSD+MON+MGR |
| host06 | DC2 | OSD+MDS+RGW |
| host07 | DC3 (Tiebreaker) | MON |
Network configuration requirements
Use the following network configuration requirements before deploying stretch cluster configuration.
Note: You can use different subnets for each of the data centers.
- Have two separate networks, one public network and one cluster network.
- The latencies between data centers that run the IBM Storage Ceph Object Storage Devices (OSDs) cannot exceed 10 ms RTT.
- DC1
Ceph public/private network: 10.0.40.0/24
- DC2
Ceph public/private network: 10.0.40.0/24
- Tiebreaker
Ceph public/private network: 10.0.40.0/24
Cluster setup requirements
Ensure that the hostname is configured by using the bare or short hostname in all hosts.
hostnamectl set-hostname SHORT_NAME
Important: The hostname command should only return the short hostname, when run on all nodes. If the FQDN is returned, the cluster configuration will not be successful.