Bug 1269249

Summary: [Docs]Need to clearly address status of Cache Tiering as Tech-Review feature and not production supported
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Mike Hackett <mhackett>
Component: DocumentationAssignee: ceph-docs <ceph-docs>
Status: CLOSED CURRENTRELEASE QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.3.0CC: jowilkin, kdreyer, ngoswami
Target Milestone: rc   
Target Release: 1.3.2   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-18 10:06:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mike Hackett 2015-10-06 19:34:36 UTC 
Description of problem:
Customer has requested clarification of the status of Cache Tiering as tech-review feature and not production supported in Ceph documentation. It is labeled as Tech Preview only in Fixed Issues section of the 1.3 Release Notes and not clearly documented further in that doc. 
Also in the 1.3 Storage Strategies doc it is listed in a section as being configurable with Erasure Coding and not labeled as tech preview.

Example: 
https://access.redhat.com/documentation/en/red-hat-ceph-storage/version-1.3/red-hat-ceph-storage-13-storage-strategies/#erasure-code

https://access.redhat.com/webassets/avalon/d/Red_Hat_Ceph_Storage-1.3-Release_Notes-en-US/Red_Hat_Ceph_Storage-1.3-Release_Notes-en-US.pdf
Comment 4 John Wilkins 2015-10-13 17:43:42 UTC 
Added additional notes to v1.3 and v1.2.3 to clearly state that erasure coding and cache tiering are tech previews.

https://gitlab.cee.redhat.com/jowilkin/red-hat-ceph-storage-release-notes/commit/a2f144ff0d6f8c7b64ae71f78fb3e3c5e415aa57

https://gitlab.cee.redhat.com/jowilkin/red-hat-ceph-storage-release-notes/commit/2bbb671660fcba60737d04140c37f66c270c4ab1
Comment 5 Anjana Suparna Sriram 2015-12-18 10:06:53 UTC 
Fixed in 1.3.2 release.