Bug 1420287

Summary: [Doc RFE] Document guidelines and instructions (as determined) regarding how to confirm/verify that in-flight encryption is enabled/functioning for CNS 3.5 volumes
Product: Red Hat Gluster Storage Reporter: Anjana Suparna Sriram <asriram>
Component: doc-Container_Native_Storage_with_OpenShiftAssignee: storage-doc
Status: CLOSED DUPLICATE QA Contact: storage-qa-internal <storage-qa-internal>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: cns-3.5CC: asriram, rhs-bugs, storage-doc
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-10 12:26:05 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:

Description Anjana Suparna Sriram 2017-02-08 11:16:57 UTC
Additional info: 
- For example, RHGS administrator manually sets up certificates and configuration through login at the RHGS server container.
- (from Humble) “As discussed in our planning exit meeting, this belongs to 'static provisioning' section. Setting up everything before we install cns is the plan for now. However, we are exploring the feasibility of bind mount and secrets to pass the certs to gluster pod. If test turn green on this feature, we may have a section before trying cns-deploy.”

Comment 2 Anjana Suparna Sriram 2017-02-10 12:26:05 UTC

*** This bug has been marked as a duplicate of bug 1421111 ***