Bug 1217555 - [RFE][HC] Configure TLS (1.2 or above) for gluster volume access from oVirt UI
Summary: [RFE][HC] Configure TLS (1.2 or above) for gluster volume access from oVirt UI
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: ---
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ovirt-4.4.1
: ---
Assignee: Gobinda Das
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1596034
TreeView+ depends on / blocked
 
Reported: 2015-04-30 15:54 UTC by Sahina Bose
Modified: 2020-03-05 09:42 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-05 09:42:55 UTC
oVirt Team: Gluster
Embargoed:
rule-engine: ovirt-4.4?
ylavi: planning_ack?
ylavi: devel_ack?
ylavi: testing_ack?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1360980 0 unspecified CLOSED [RFE] Configure SSL options for gluster volume 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1405891 0 medium CLOSED [RFE] Reusing vdsm certs for Gluster infra 2022-02-23 14:50:44 UTC

Internal Links: 1360980 1405891

Description Sahina Bose 2015-04-30 15:54:53 UTC
Description of problem:

SSL needs to be configured per gluster volume as well as on nodes to allow secure access to data for clients. This configuration needs to be supported from oVirt UI

Comment 1 Red Hat Bugzilla Rules Engine 2015-10-19 10:58:56 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 2 Sahina Bose 2016-07-28 10:50:37 UTC
There's an RFE opened in gdeploy for this feature - Bug 1360980. Since gdeploy will be used to prepare HC environment, priority for this is lowered - pushing this out of 4.1.0

Comment 3 Yaniv Kaul 2018-03-01 09:00:05 UTC
Raising to HIGH - rest of our encryption (in 4.2) is already using TLS 1.2.

Comment 4 Sahina Bose 2018-11-21 15:19:56 UTC
The volume configuration via cockpit handles this. Not a high priority, hence deferring this

Comment 7 Sahina Bose 2018-11-29 05:44:52 UTC
We can reuse the gluster-ansible role to setup TLS for the volume. Would this be a possibility to integrate to Cockpit and engine?

Comment 8 Gobinda Das 2020-03-05 09:42:55 UTC
We have features in gluster ansible for this.Now we don't have plan to integrate with cockpit.Closing this for now and will create one once will have plan.


Note You need to log in before you can comment on or make changes to this bug.