diff options
author | John Wilkins <john.wilkins@inktank.com> | 2013-10-22 17:11:07 -0700 |
---|---|---|
committer | John Wilkins <john.wilkins@inktank.com> | 2013-10-22 17:11:07 -0700 |
commit | 828537c8597260017d8ade1c5cee934e4859dc9b (patch) | |
tree | c20a377ee8bb8a05852ea54fefb4617ced6f9a9b | |
parent | 105fb61f87957095d20f315d4bb12aaab3487577 (diff) | |
download | ceph-828537c8597260017d8ade1c5cee934e4859dc9b.tar.gz |
doc: Added ARM. Added Calxeda hardware example.
fixes: #5608
Signed-off-by: John Wilkins <john.wilkins@inktank.com>
-rw-r--r-- | doc/start/hardware-recommendations.rst | 105 |
1 files changed, 71 insertions, 34 deletions
diff --git a/doc/start/hardware-recommendations.rst b/doc/start/hardware-recommendations.rst index 90d29e5e7e2..58d290aa564 100644 --- a/doc/start/hardware-recommendations.rst +++ b/doc/start/hardware-recommendations.rst @@ -10,11 +10,7 @@ issues. Hardware planning should include distributing Ceph daemons and other processes that use Ceph across many hosts. Generally, we recommend running Ceph daemons of a specific type on a host configured for that type of daemon. We recommend using other hosts for processes that utilize your -data cluster (e.g., OpenStack, CloudStack, etc). - -`Inktank`_ provides excellent premium support for hardware planning. - -.. _Inktank: http://www.inktank.com +data cluster (e.g., OpenStack, CloudStack, etc). .. tip:: Check out the Ceph blog too. Articles like `Ceph Write Throughput 1`_, @@ -251,33 +247,39 @@ Minimum Hardware Recommendations Ceph can run on inexpensive commodity hardware. Small production clusters and development clusters can run successfully with modest hardware. -+--------------+----------------+------------------------------------+ -| Process | Criteria | Minimum Recommended | -+==============+================+====================================+ -| ``ceph-osd`` | Processor | 1x 64-bit AMD-64/i386 dual-core | -| +----------------+------------------------------------+ -| | RAM | 500 MB per daemon | -| +----------------+------------------------------------+ -| | Volume Storage | 1x Disk per daemon | -| +----------------+------------------------------------+ -| | Network | 2x 1GB Ethernet NICs | -+--------------+----------------+------------------------------------+ -| ``ceph-mon`` | Processor | 1x 64-bit AMD-64/i386 | -| +----------------+------------------------------------+ -| | RAM | 1 GB per daemon | -| +----------------+------------------------------------+ -| | Disk Space | 10 GB per daemon | -| +----------------+------------------------------------+ -| | Network | 2x 1GB Ethernet NICs | -+--------------+----------------+------------------------------------+ -| ``ceph-mds`` | Processor | 1x 64-bit AMD-64/i386 quad-core | -| +----------------+------------------------------------+ -| | RAM | 1 GB minimum per daemon | -| +----------------+------------------------------------+ -| | Disk Space | 1 MB per daemon | -| +----------------+------------------------------------+ -| | Network | 2x 1GB Ethernet NICs | -+--------------+----------------+------------------------------------+ ++--------------+----------------+--------------------------------------+ +| Process | Criteria | Minimum Recommended | ++==============+================+======================================+ +| ``ceph-osd`` | Processor | - 1x 64-bit AMD-64 | +| | | - 1x 32-bit ARM dual-core or better | +| | | - 1x i386 dual-core | +| +----------------+--------------------------------------+ +| | RAM | 500 MB per daemon | +| +----------------+--------------------------------------+ +| | Volume Storage | 1x Disk per daemon | +| +----------------+--------------------------------------+ +| | Network | 2x 1GB Ethernet NICs | ++--------------+----------------+--------------------------------------+ +| ``ceph-mon`` | Processor | - 1x 64-bit AMD-64/i386 | +| | | - 1x 32-bit ARM dual-core or better | +| | | - 1x i386 dual-core | +| +----------------+--------------------------------------+ +| | RAM | 1 GB per daemon | +| +----------------+--------------------------------------+ +| | Disk Space | 10 GB per daemon | +| +----------------+--------------------------------------+ +| | Network | 2x 1GB Ethernet NICs | ++--------------+----------------+--------------------------------------+ +| ``ceph-mds`` | Processor | - 1x 64-bit AMD-64 quad-core | +| | | - 1x 32-bit ARM quad-core | +| | | - 1x i386 quad-core | +| +----------------+--------------------------------------+ +| | RAM | 1 GB minimum per daemon | +| +----------------+--------------------------------------+ +| | Disk Space | 1 MB per daemon | +| +----------------+--------------------------------------+ +| | Network | 2x 1GB Ethernet NICs | ++--------------+----------------+--------------------------------------+ .. tip:: If you are running an OSD with a single disk, create a partition for your volume storage that is separate from the partition @@ -285,13 +287,16 @@ and development clusters can run successfully with modest hardware. OS and the volume storage. -Production Cluster Example -========================== +Production Cluster Examples +=========================== Production clusters for petabyte scale data storage may also use commodity hardware, but should have considerably more memory, processing power and data storage to account for heavy traffic loads. +Dell Example +------------ + A recent (2012) Ceph cluster project is using two fairly robust hardware configurations for Ceph OSDs, and a lighter configuration for monitors. @@ -326,6 +331,38 @@ configurations for Ceph OSDs, and a lighter configuration for monitors. +----------------+----------------+------------------------------------+ +Calxeda Example +--------------- + +A recent (2013) Ceph cluster project is using ARM hardware with low +power consumption and high storage density for for Ceph OSDs. + ++----------------+----------------+----------------------------------------+ +| Configuration | Criteria | Minimum Recommended | ++================+================+========================================+ +| SuperMicro | Processor Card | 3x Calxeda EnergyCard building blocks | +| SC 847 Chassis +----------------+----------------------------------------+ +| 4U | CPU | 4x ECX-1000 ARM 1.4 GHz SoC per card | +| +----------------+----------------------------------------+ +| | RAM | 4 GB per System-on-a-chip (SoC) | +| +----------------+----------------------------------------+ +| | Volume Storage | 36x 3TB Seagate Barracuda SATA | +| +----------------+----------------------------------------+ +| | Client Network | 1x 10GB Ethernet NICs | +| +----------------+----------------------------------------+ +| | OSD Network | 1x 10GB Ethernet NICs | +| +----------------+----------------------------------------+ +| | Mgmt. Network | 1x 1GB Ethernet NICs | ++----------------+----------------+----------------------------------------+ + +The project enables the deployment of 36 Ceph OSD Daemons, one for each +3TB drive. Each processor runs 3 Ceph OSD Daemons. Four processors per +card allows the 12 processors in with just four cards. This configuration +provides 108TB of storage (slightly less after full ratio settings) per +4U chassis. + + + .. _Ceph Write Throughput 1: http://ceph.com/community/ceph-performance-part-1-disk-controller-write-throughput/ .. _Ceph Write Throughput 2: http://ceph.com/community/ceph-performance-part-2-write-throughput-without-ssd-journals/ .. _Argonaut v. Bobtail Performance Preview: http://ceph.com/uncategorized/argonaut-vs-bobtail-performance-preview/ |