Remove reference to EC being in beta
Closes-Bug: #1719095 Change-Id: I8051895987bf72c8095e72b5a521042a13993174 Signed-off-by: Thiago da Silva <thiago@redhat.com>
This commit is contained in:
parent
55d193eb76
commit
69a90dcd75
@ -17,13 +17,3 @@ erasure coding capability. It is entirely possible to share devices between
|
|||||||
storage policies, but for erasure coding it may make more sense to use
|
storage policies, but for erasure coding it may make more sense to use
|
||||||
not only separate devices but possibly even entire nodes dedicated for erasure
|
not only separate devices but possibly even entire nodes dedicated for erasure
|
||||||
coding.
|
coding.
|
||||||
|
|
||||||
.. important::
|
|
||||||
|
|
||||||
The erasure code support in Object Storage is considered beta in Kilo.
|
|
||||||
Most major functionality is included, but it has not been tested or
|
|
||||||
validated at large scale. This feature relies on ``ssync`` for durability.
|
|
||||||
We recommend deployers do extensive testing and not deploy production
|
|
||||||
data using an erasure code storage policy.
|
|
||||||
If any bugs are found during testing, please report them to
|
|
||||||
https://bugs.launchpad.net/swift
|
|
||||||
|
Loading…
Reference in New Issue
Block a user