<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Thanks Niels and Joe,<br>
<br>
Changed my patch to use 24009. Dynamic port is not required since
one process per node.<br>
<br>
24005 is already registered by "med-ci" as checked in
/etc/services<br>
</tt>
<pre class="moz-signature" cols="72">regards
Aravinda</pre>
<div class="moz-cite-prefix">On Sunday 28 August 2016 02:13 PM,
Niels de Vos wrote:<br>
</div>
<blockquote
cite="mid:20160828084307.GA1310@chromebook.lan.nixpanic.net"
type="cite">
<pre wrap="">On Sat, Aug 27, 2016 at 02:02:43PM -0700, Joe Julian wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 08/27/2016 12:15 PM, Niels de Vos wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Sat, Aug 27, 2016 at 08:52:11PM +0530, Aravinda wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
As part of Client events support, glustereventsd needs to be configured to
use a port. Following ports are already used by Gluster components.
24007 For glusterd
24008 For glusterd RDMA port management
38465 Gluster NFS service
38466 Gluster NFS service
38467 Gluster NFS service
38468 Gluster NFS service
38469 Gluster NFS service
49152-49664 512 ports for bricks
If I remember correctly, 24009+ ports were used by old GlusterFS(<3.4). In
the patch eventsd is using 24005. Please suggest which port glustereventsd
can use?(Can we use 24009 port)
<a class="moz-txt-link-freetext" href="http://review.gluster.org/15189">http://review.gluster.org/15189</a>
</pre>
</blockquote>
<pre wrap="">I guess you can use 24009, but it would be way better to either:
a. use glusterd-portmapper and get a dynamic port 49152+
</pre>
</blockquote>
<pre wrap="">Strongly disagree. It's enough that we have to poke dynamic holes in
firewalls already (sure it's easy with firewalld, but with hardware
firewalls or openstack security groups we just have to open a huge hole),
adding one that we also need to use as a service endpoint is too much.
</pre>
</blockquote>
<pre wrap="">
Heh, yes, of course. I also think it needs quite some work in
glustereventsd to be able to use it, and then the clients need to
request the port from glusterd before they can consume events. It is the
way how other gluster clients work atm.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">b. register a port at IANA, see /etc/services
(maybe we should try to register the 24007+24008 ports in any case)
</pre>
</blockquote>
<pre wrap="">+100
</pre>
</blockquote>
<pre wrap="">
This definitely has my preference too. I've always wanted to try to
register port 24007/8, and maybe the time has come to look into it.
Thanks for sharing your opinion!
Niels
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gluster-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://www.gluster.org/mailman/listinfo/gluster-devel">http://www.gluster.org/mailman/listinfo/gluster-devel</a></pre>
</blockquote>
<br>
</body>
</html>