On Thu, Aug 17, 2017 at 12:46 PM, Kaushal M <kshlmster@xxxxxxxxx> wrote: > On Thu, Aug 3, 2017 at 2:12 PM, Milind Changire <mchangir@xxxxxxxxxx> wrote: >> >> >> On Thu, Aug 3, 2017 at 12:56 PM, Kaushal M <kshlmster@xxxxxxxxx> wrote: >>> >>> On Thu, Aug 3, 2017 at 2:14 AM, Niels de Vos <ndevos@xxxxxxxxxx> wrote: >>> > On Wed, Aug 02, 2017 at 05:03:35PM +0530, Prashanth Pai wrote: >>> >> Hi all, >>> >> >>> >> The ongoing work on glusterd2 necessitates following non-breaking and >>> >> non-exhaustive list of changes to glusterfs source code: >>> >> >>> >> Port management >>> >> - Remove hard-coding of glusterd's port as 24007 in clients and >>> >> elsewhere. >>> >> Glusterd2 can be configured to listen to clients on any port (still >>> >> defaults to >>> >> 24007 though) >>> >> - Let the bricks and daemons choose any available port and if needed >>> >> report >>> >> the port used to glusterd during the "sign in" process. Prasanna has >>> >> a >>> >> patch >>> >> to do this. >>> >> - Glusterd <--> brick (or any other local daemon) communication should >>> >> always happen over Unix Domain Socket. Currently glusterd and brick >>> >> process communicates over UDS and also port 24007. This will allow us >>> >> to set better authentication and rules for port 24007 as it shall >>> >> only be >>> >> used >>> >> by clients. >>> > >>> > I prefer this last point to be configurable. At least for debugging we >>> > should be able to capture network traces and display the communication >>> > in Wireshark. Defaulting to UNIX Domain Sockets is fine though. >>> >>> This is the communication between GD2 and bricks, of which there is >>> not a lot happening, and not much to capture. >>> But I agree, it will be nice to have this configurable. >>> >> >> Could glusterd start attempting port binding at 24007 and progress on to >> higher port numbers until successful and register the bound port number with >> rpcbind ? This way the setup will be auto-configurable and admins need not >> scratch their heads to decide upon one port number. Gluster clients could >> always talk to rpcbind on the nodes to get glusterd service port whenever a >> reconnect is required. > > 24007 has always been used as the GlusterD port. There was a plan to > have it registered with IANA as well. > Having a well defined port is useful to allow proper firewall rules to be setup. I seem to recall asking about this in another thread - is anyone planning to follow through with the registration? _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
