Re: [Gluster-devel] Events API new Port requirement

[Sankarshan Mukhopadhyay]

On Fri, Sep 9, 2016 at 3:55 AM, Niels de Vos  wrote:
> On Thu, Sep 08, 2016 at 10:03:03PM +0530, Sankarshan Mukhopadhyay wrote:
>> On Sun, Aug 28, 2016 at 2:13 PM, Niels de Vos  wrote:
>> > 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.
>>
>> Has someone within the project previously undertaken the process of
>> requesting the IANA for assignment of a new service name and port
>> number value?
>
> Not that I know. I think Amar had an interest several years ago, but
> I've never seen any requests or results.
>
> There are some Red Hat colleagues that might have experience with this.
> I can ask and see if they can provide any guidance. But if there is
> someone very interested and eager to request these ports, please go
> ahead (and CC me on the communications).
>

If you can reach out and obtain the necessary information, it would be
a good first step.


-- 
sankarshan mukhopadhyay

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

Re: [Gluster-devel] Events API new Port requirement

[Niels de Vos]

On Thu, Sep 08, 2016 at 10:03:03PM +0530, Sankarshan Mukhopadhyay wrote:
> On Sun, Aug 28, 2016 at 2:13 PM, Niels de Vos  wrote:
> > 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.
> 
> Has someone within the project previously undertaken the process of
> requesting the IANA for assignment of a new service name and port
> number value?

Not that I know. I think Amar had an interest several years ago, but
I've never seen any requests or results.

There are some Red Hat colleagues that might have experience with this.
I can ask and see if they can provide any guidance. But if there is
someone very interested and eager to request these ports, please go
ahead (and CC me on the communications).

Niels


signature.asc
Description: PGP signature
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Events API new Port requirement

[Sankarshan Mukhopadhyay]

On Sun, Aug 28, 2016 at 2:13 PM, Niels de Vos  wrote:
> 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.

Has someone within the project previously undertaken the process of
requesting the IANA for assignment of a new service name and port
number value?


-- 
sankarshan mukhopadhyay

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

Re: [Gluster-devel] Events API new Port requirement

[Aravinda]

Thanks Niels and Joe,

Changed my patch to use 24009. Dynamic port is not required since one 
process per node.


24005 is already registered by "med-ci" as checked in /etc/services

regards
Aravinda

On Sunday 28 August 2016 02:13 PM, Niels de Vos wrote:

On Sat, Aug 27, 2016 at 02:02:43PM -0700, Joe Julian wrote:

On 08/27/2016 12:15 PM, Niels de Vos wrote:

On Sat, Aug 27, 2016 at 08:52:11PM +0530, Aravinda wrote:

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-49664512 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)
http://review.gluster.org/15189

I guess you can use 24009, but it would be way better to either:

a. use glusterd-portmapper and get a dynamic port 49152+

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.

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.


b. register a port at IANA, see /etc/services
 (maybe we should try to register the 24007+24008 ports in any case)

+100

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


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


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

Re: [Gluster-devel] Events API new Port requirement

[Niels de Vos]

On Sat, Aug 27, 2016 at 02:02:43PM -0700, Joe Julian wrote:
> On 08/27/2016 12:15 PM, Niels de Vos wrote:
> > On Sat, Aug 27, 2016 at 08:52:11PM +0530, Aravinda wrote:
> > > 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-49664512 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)
> > > http://review.gluster.org/15189
> > I guess you can use 24009, but it would be way better to either:
> > 
> > a. use glusterd-portmapper and get a dynamic port 49152+
> 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.

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.

> > b. register a port at IANA, see /etc/services
> > (maybe we should try to register the 24007+24008 ports in any case)
> +100

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


signature.asc
Description: PGP signature
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Events API new Port requirement

[Joe Julian]

On 08/27/2016 12:15 PM, Niels de Vos wrote:

On Sat, Aug 27, 2016 at 08:52:11PM +0530, Aravinda wrote:

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-49664512 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)
http://review.gluster.org/15189

I guess you can use 24009, but it would be way better to either:

a. use glusterd-portmapper and get a dynamic port 49152+
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.

b. register a port at IANA, see /etc/services
(maybe we should try to register the 24007+24008 ports in any case)

+100


HTH,
Niels


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


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

Re: [Gluster-devel] Events API new Port requirement

[Niels de Vos]

On Sat, Aug 27, 2016 at 08:52:11PM +0530, Aravinda wrote:
> 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-49664512 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)
> http://review.gluster.org/15189

I guess you can use 24009, but it would be way better to either:

a. use glusterd-portmapper and get a dynamic port 49152+
b. register a port at IANA, see /etc/services
   (maybe we should try to register the 24007+24008 ports in any case)

HTH,
Niels


signature.asc
Description: PGP signature
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Events API new Port requirement

[Aravinda]

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-49664512 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)

http://review.gluster.org/15189

--
regards
Aravinda

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