From 69a90dcd7511756ff72d89bb0b6f744e1a135456 Mon Sep 17 00:00:00 2001 From: Thiago da Silva Date: Mon, 25 Sep 2017 13:27:50 -0400 Subject: [PATCH] Remove reference to EC being in beta Closes-Bug: #1719095 Change-Id: I8051895987bf72c8095e72b5a521042a13993174 Signed-off-by: Thiago da Silva --- doc/source/admin/objectstorage-EC.rst | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/doc/source/admin/objectstorage-EC.rst b/doc/source/admin/objectstorage-EC.rst index 6f1996b537..2e324079d0 100644 --- a/doc/source/admin/objectstorage-EC.rst +++ b/doc/source/admin/objectstorage-EC.rst @@ -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 not only separate devices but possibly even entire nodes dedicated for erasure 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