Bug 1751266

Summary: [RFE] Automatcially generate and deploy self signed cert by default on the overcloud
Product: Red Hat OpenStack Reporter: Kevin Jones <kejones>
Component: rhosp-directorAssignee: RHOS Maint <rhos-maint>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: aschultz, augol, dbecker, dcaspin, ggrasza, hrybacki, mburns, morazi
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-30 20:15:12 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 Kevin Jones 2019-09-11 14:36:39 UTC 
Description of problem:
Currently RHOSP Director deploys the overcloud by default without TLS enabled on the public endpoints. All other Red Hat products TMK deploy by default with a self signed cert.

Even the undercloud gives the ability to generate and automatically deploy a self signed cert.

However, the process for the overcloud is very manual and tedious.

Please automate and deploy self-signed certs on public endpoints by default.


Version-Release number of selected component (if applicable):
All

How reproducible:
100%

Actual results:
A default overcloud deployment deploys without TLS on the public endpoints.

Expected results:
A default overcloud deployment should deploy with TLS with an auto-generated self-signed cert.

Additional info:
It would also be nice to automatically inject the undercloud CA in the overcloud hosts by default as well rather than having to go find the CA file and create a yaml template to include it.
Comment 1 Harry Rybacki 2020-07-21 15:44:28 UTC 
*** Bug 1672754 has been marked as a duplicate of this bug. ***
Comment 2 Harry Rybacki 2020-07-21 16:40:28 UTC 
*** Bug 1566598 has been marked as a duplicate of this bug. ***
Comment 3 Doron Caspin 2021-04-30 20:15:12 UTC 
After review between PM and engineering, we have decided to close this RFE due to a lack of capacity. Please reopen this issue if you feel it still needs to be addressed and requests re-evaluation.