From: Thomas Johnson Date: Tue, 17 Mar 2015 16:32:24 +0000 (+0100) Subject: doc-rados-operations-crush-map: Swap Raid4 for Erasure X-Git-Tag: v9.0.0~158^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=refs%2Fpull%2F4045%2Fhead;p=ceph.git doc-rados-operations-crush-map: Swap Raid4 for Erasure Signed-off-by: Thomas Johnson --- diff --git a/doc/rados/operations/crush-map.rst b/doc/rados/operations/crush-map.rst index ec982440887..01db2b30799 100644 --- a/doc/rados/operations/crush-map.rst +++ b/doc/rados/operations/crush-map.rst @@ -493,8 +493,8 @@ CRUSH rules defines placement and replication strategies or distribution polici that allow you to specify exactly how CRUSH places object replicas. For example, you might create a rule selecting a pair of targets for 2-way mirroring, another rule for selecting three targets in two different data -centers for 3-way mirroring, and yet another rule for RAID-4 over six storage -devices. For a detailed discussion of CRUSH rules, refer to +centers for 3-way mirroring, and yet another rule for erasure coding over six +storage devices. For a detailed discussion of CRUSH rules, refer to `CRUSH - Controlled, Scalable, Decentralized Placement of Replicated Data`_, and more specifically to **Section 3.2**. @@ -503,7 +503,7 @@ A rule takes the following form:: rule { ruleset - type [ replicated | raid4 ] + type [ replicated | erasure ] min_size max_size step take @@ -534,7 +534,7 @@ A rule takes the following form:: :Type: String :Required: Yes :Default: ``replicated`` -:Valid Values: Currently only ``replicated`` +:Valid Values: Currently only ``replicated`` and ``erasure`` ``min_size``