GlusterFS firewalld control

[Christopher Blum <cblum@xxxxxxxxxx>]

Hey Gluster Developers,

I'm fairly new to GlusterFS, but noticed, that it is missing the possibility to control firewalld, which is also addressed in [1]

Since I wanted to propose a solution for this problem, I briefly talked to Niels de Vos and we identified 2 possible ways to fix this:

1) Use the dbus connection to control firewalld when we do bind() as a server - it looks like there is only one place where we do that [2]

     --> Pretty much a catch all solution, but will require to link against dbus and a precompiler check for OSs with firewalld

2) Use the glusterfs hooks to call a script, when we create volumes to open up the (dynamic) ports of the involved bricks

     --> Easier to implement, but where do we get the port information from? Additionally involves the creation of a static config for the glusterd process.

Looking at [3], we need to open up additional (dynamic) ports for NFS? Is that info correct?

Since I'm fairly new, I would welcome a discussion, which approach is best in your opinion. Please also tell me if any assumptions from above are incorrect...

Best Regards,

Chris

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1057295

[2] https://forge.gluster.org/glusterfs-core/glusterfs/blobs/master/rpc/rpc-transport/socket/src/socket.c#line758

[3] http://www.gluster.org/community/documentation/index.php/Gluster_3.1:_Installing_GlusterFS_on_Red_Hat_Package_Manager_(RPM)_Distributions

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel