Opened 10 years ago

Last modified 3 years ago

#620 new enhancement

IZ2870: daemons should support use of IPv6

Reported by: templedf Owned by:
Priority: normal Milestone:
Component: sge Version: 8.1.8
Severity: major Keywords: kernel, network, sockets, ports, tcp, ipv4, ipv6
Cc:

Description

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2870]

        Issue #:      2870             Platform:     All           Reporter: templedf (templedf)
       Component:     gridengine          OS:        All
     Subcomponent:    kernel           Version:      6.2              CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     andreas
          URL:
       * Summary:     daemons should support use of IPv6
   Status whiteboard:
      Attachments:

     Issue 2870 blocks:
   Votes for issue 2870:


   Opened: Mon Jan 12 14:13:00 -0700 2009 
------------------------


Grid Engine currently only supports IPv4.  If should be possible to use IPv6 as
well.

   ------- Additional comments from templedf Mon Jan 12 14:14:02 -0700 2009 -------
Changed to RFE

Change History (4)

comment:1 Changed 3 years ago by tourist

  • Keywords network sockets ports tcp ipv4 ipv6 added; removed
  • Severity set to major
  • Version changed from 6.2 to 8.1.8

Any progress in this issue?
In the meantime sge is the one and only service, which depends on ipv4 in my network.
IPv4-addresses are rare, also when using RFC1918 - it makes things more complex.

Regards,
Thomas Schäfer
tschaefer@…

comment:2 Changed 3 years ago by dlove

SGE <sge-bugs@…> writes:

Any progress in this issue?

Not that I know, and I haven't heard of anyone else asking. I looked at
it some time ago, anf found how rubbish a lot of relevant documentation
is... I concluded it's probably relatively easy to support either v4 or
v6, but relatively hard to support both. Contributions welcome, of
course.

In the meantime sge is the one and only service, which depends on ipv4 in
my network.
IPv4-addresses are rare, also when using RFC1918 - it makes things more
complex.

How are you using SGE? I'd be surprised if it was the only v4-only
thing in an HPC cluster. I don't understand how v6 is relevant to 1918
and -- at least in a cluster -- there's nothing to stop you running an
external v6 interface and internal v4.

comment:3 Changed 3 years ago by tourist

The documentation is not only rubbish at the network/sockets part. It seems to me this is a general problem with SGE. Some parts are up to date, or at least working in progress is visible. (e.g. support of systemd). Other parts like ipv6 are ignored over years.
But I don't want open a general discussion about a lot of problems you probably already know.

I am not able to make a contribution of code. I am just an admin. I can provide tests.

I use SGE in a Linux dualstack environment with three /25-IPv4 networks(partly with RFC1918-adresses) and one /48-IPv6 network split in to three /64 vlan. All external services are reachable via IPv4 and IPv6(from apache over ssh to vnc). For internal service like samba, nfs, IBMs tivoli storage , ntp, dns-resolver I avoid the risky ipv6-ipv4-fallback by using exclusively IPv6.
So I have a clear strategy. IPv6 first, exclusive if possible, dualstack if necessary just to stay connected with some other older parts of the world.

The(my) cluster is at moment just an evaluation setup with four machines. But it could grow.
My problem is not the external thing. The SGE-tcp-ports are firewalled to public internet. That is not the problem. My problem is the limited and fragmented ipv4 internal network. So the life would be much easier with ipv6. No (real) host limits in every vlan, no additionally routing (I have a limited access to the routers, because network management is done by others), easier ip-address-management.

So I would treat sge like every other only internally service, but I can't.

Last but not least - sge would look a bit more modern.

You are right there are some other things with ipv4-only. The unmaintained skype-version for linux and teamviewer. Both only for external use and only if the user it wants explicitly.

Regards,
Thomas Schäfer
tschaefer@…

Last edited 3 years ago by tourist (previous) (diff)

comment:4 Changed 3 years ago by dlove

SGE <sge-bugs@…> writes:

The documentations is not only rubbish to the network/sockets part.

I meant documentation on ipv6 implementation.

It
seems to me this is a general problem with SGE. Some parts are up to date,
or at least working in progress is visible. (e.g. support of systemd).
Other parts like ipv6 are ignored over years.

You should ask for your money back.

So I would treat sge like every other only internally service, but I
can't.

You have, for instance, BMCs that talk v6?

Last but not least - sge would look a bit more modern.

I don't know what that means, but none of this is likely to change
without people contributing in some way.

Note: See TracTickets for help on using tickets.