Bug 2208257

Summary: [DDF] We mention replica 2 several times in the "Managing and allocating storage resources" guide (chapters 2.1, 3.1,
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Disha Walvekar <dwalveka>
Component: documentationAssignee: Disha Walvekar <dwalveka>
Status: VERIFIED --- QA Contact: Olive Lakra <olakra>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.11CC: cblum, ddf-bot, dwalveka, nberry, odf-bz-bot, olakra
Target Milestone: ---Keywords: NoDocsQEReview
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2115744 Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2115744, 2208259, 2208261    
Bug Blocks:    

Description Disha Walvekar 2023-05-18 11:48:09 UTC
+++ This bug was initially created as a clone of Bug #2115744 +++

We mention replica 2 several times in the "Managing and allocating storage resources" guide (chapters 2.1, 3.1, 3.2) but never that using replica 2 requires a support exception.

Reported by: rhn-stor-cblum

https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.10/html/managing_and_allocating_storage_resources/storage-classes_rhodf#annotations:3c61f817-f37b-4c54-be0e-21ba79d11c23

--- Additional comment from RHEL Program Management on 2022-08-05 08:29:22 UTC ---

This bug having no release flag set previously, is now set with release flag 'odf‑4.11.0' to '?', and so is being proposed to be fixed at the ODF 4.11.0 release. Note that the 3 Acks (pm_ack, devel_ack, qa_ack), if any previously set while release flag was missing, have now been reset since the Acks are to be set against a release flag.

--- Additional comment from Chris Blum on 2022-09-16 13:07:19 UTC ---

After re-reading the doc and talking to Eran it becomes clearer what is meant in this documentation:
The steps detailed in this chapter show how to configure an *additional* storage class for an *additional storage pool*
We still need a support exception if a customer wants to use replica 2 on the default pool, but no support exception is needed for using replica 2 on additional pools.

Thus this documentation is formally correct, but I think we need an info box stating the above, so it's clear what is and isn't supported when customers stumble over this section.

--- Additional comment from Red Hat Bugzilla on 2022-12-31 19:54:44 UTC ---

remove performed by PnT Account Manager <pnt-expunge>

--- Additional comment from Red Hat Bugzilla on 2022-12-31 23:43:55 UTC ---

remove performed by PnT Account Manager <pnt-expunge>

--- Additional comment from Red Hat Bugzilla on 2023-01-01 08:29:22 UTC ---

Account disabled by LDAP Audit

--- Additional comment from Disha Walvekar on 2023-05-15 10:54:07 UTC ---

Hi @cblum 

Based on the description and the comment, I have drafted a note as follows: 

NOTE - Using 2-way replication data protection policy is not supported for the default pool. However, you can use 2-way replication if you are creating an additional pool.


For now, I have not added anything related to raising a support exception. Please let me know if you me add that the customers can raise a support exception to use 2 replica for default pool. 
Can you also share the link with which customers can raise a support exception?

Thank you!

--- Additional comment from Disha Walvekar on 2023-05-15 10:55:38 UTC ---

Link to the draft - https://docs.google.com/document/d/1dW3YuJ0slwiJJ2s9yBeAFvvodTJYvbHsGX6PSp26UiM/edit

--- Additional comment from Chris Blum on 2023-05-16 11:53:47 UTC ---

Thanks for working on this. The draft looks ok to me.