Bug 1722071

Summary: [RFE] Enable SSL termination for RadosGW
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Giulio Fidente <gfidente>
Component: Ceph-AnsibleAssignee: Giulio Fidente <gfidente>
Status: CLOSED ERRATA QA Contact: Vasishta <vashastr>
Severity: medium Docs Contact: Bara Ancincova <bancinco>
Priority: medium    
Version: 4.0CC: aschoen, ceph-eng-bugs, dsavinea, dwojewod, gmeno, nthomas, tserlin
Target Milestone: rcKeywords: FutureFeature
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-ansible-4.0.0-0.1.rc10.el8cp Doc Type: Enhancement
Doc Text:
.Ability to configure Ceph Object Gateway to use TLS encryption This release of {product} provides the ability to configure the Ceph Object Gateway listener with an SSL certificate for TLS encryption by using the `radosgw_frontend_ssl_certificate` variable to secure the Transmission Control Protocol (TCP) traffic.
Story Points: ---
Clone Of:
: 1796891 (view as bug list) Environment:
Last Closed: 2020-01-31 12:46:20 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:
Bug Depends On:    
Bug Blocks: 1642481, 1701416, 1730176, 1796891    

Description Giulio Fidente 2019-06-19 13:04:38 UTC
We need to add the bits to configure SSL for civetweb

Comment 1 Yaniv Kaul 2019-06-20 02:51:29 UTC
Although we plan to move to Beast?

Comment 2 Giulio Fidente 2019-06-20 09:26:24 UTC
(In reply to Yaniv Kaul from comment #1)
> Although we plan to move to Beast?

indeed my initial comment assumed civetweb but we migrated to beast already upstream (OSP16 and OSP15); the ceph-ansible change will be updated to deal with both civetweb and beast

Comment 5 Giridhar Ramaraju 2019-08-05 13:10:41 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 6 Giridhar Ramaraju 2019-08-05 13:11:44 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 13 errata-xmlrpc 2020-01-31 12:46:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0312