Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1693979 - [gluster-ansible] Enable RHGS SSL/TLS encryption with self-signed certs
Summary: [gluster-ansible] Enable RHGS SSL/TLS encryption with self-signed certs
Status: POST
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: gluster-ansible
Version: rhgs-3.4
Hardware: x86_64
OS: Linux
Target Milestone: ---
: RHGS 3.5.0
Assignee: Sachidananda Urs
Depends On:
Blocks: 1693980
TreeView+ depends on / blocked
Reported: 2019-03-29 08:15 UTC by SATHEESARAN
Modified: 2019-04-11 07:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1693980 (view as bug list)
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description SATHEESARAN 2019-03-29 08:15:55 UTC
Description of problem:
RHGS supports SSL/TLS encryption and gluster-ansible should help in setting up such encryption using self-signed

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

How reproducible:
Not Applicable

Steps to Reproduce:
Not applicable

Actual results:
No way to enable RHGS SSL/TLS encryption using self-signed certs using gluster-ansible

Expected results:
Provide a way to enable RHGS SSL/TLS encryption using self-signed certs

Comment 1 SATHEESARAN 2019-03-29 08:20:54 UTC
Please refer the RHGS Admin guide for getting the self-signed certs

The high-level steps include:
1. Create the certs under /etc/ssl/ on all the hosts
       glusterfs.pem,, glusterfs.key will be concatenation of 'glusterfs.pem' from all the hosts

2. Create a file - /var/lib/glusterd/secure-access - that enables encryption on the management layer
3. Restart glusterd
4. On the volumes, set the volume options:
        server.ssl=on, client.ssl=on
5. Restart volumes if they are already started. Its better to set the options before starting the volume.

Make sure, all these changes happen before creating the gluster cluster using 'peer probe'

Comment 2 SATHEESARAN 2019-03-29 08:33:01 UTC
Missed one more volume option:
     auth.ssl-allow=<CN_of_host1>, <CN_of_host2>, etc
        Note: CN is the common name of the host used during certificate generation

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