Bug 1371633 - mop off the glusterfs firewall service
Summary: mop off the glusterfs firewall service
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-30 16:58 UTC by Prasanna Kumar Kalever
Modified: 2020-02-07 07:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-15 03:09:17 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Prasanna Kumar Kalever 2016-08-30 16:58:11 UTC
Description of problem:
Currently glusterfs firewall service is created if firewalld installed.

It creates glusterfs firewall service during installation. 

glusterfs service : It contains all default ports which needs to be opened.

During installation  glusterfs.xml is copied into firewall service directory(/usr/lib/firewalld/services/).

This is what currently happens:
    1.For bricks: It opens the 512 ports, if brick is running out side this range(>49664) then admin need to open the port
    for that brick.
    2.By default this service is not enabled in any of zone.

    To enable this service(glusterfs) in firewall:

    1. Get active zone(s) in node
         firewall-cmd  --get-active-zones

    2. Attached this service(glusterfs) to zone(s)
       firewall-cmd  --zone=<zone_name>  --add-service=glusterfs               --To apply runtime
       firewall-cmd  --permanent  --zone=<zone_name>  --add-service=glusterfs  --To apply permanent



This mechanism for opening ports for firewall is no more needed with the new port map architecture, hence we need to mop this off.


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

Comment 1 Niels de Vos 2016-09-06 12:17:07 UTC
(In reply to Prasanna Kumar Kalever from comment #0)
...
> This mechanism for opening ports for firewall is no more needed with the new
> port map architecture, hence we need to mop this off.

Pointer to the updated documentation about the new port map architecture? How is GlusterD going to open ports dynamically?

Comment 2 Amar Tumballi 2019-05-09 20:09:43 UTC
Is it required even now? Why was no one bothered about in years?

Comment 3 Atin Mukherjee 2019-07-08 03:49:53 UTC
I don't think we're going to work on this any longer in GD1. Appreciate if this can be closed as won't fix. I'll wait for couple of days for Prasanna to come over, otherwise would close this.

Comment 4 Atin Mukherjee 2019-07-15 03:09:17 UTC
I'm closing this for now. If there's any valid justification please reopen.


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