----- Original Message -----
From: "Dan Callaghan" <dcallagh(a)redhat.com>
To: "beaker-devel" <beaker-devel(a)lists.fedorahosted.org>
Sent: Wednesday, November 27, 2013 11:27:33 AM
Subject: Re: [Beaker-devel] Questions regarding DHCP/DNS requirements for IPv6 support
Excerpts from Raymond Mancy's message of 2013-11-27 11:16:15 +1000:
> ----- Original Message -----
> > From: "Nick Coghlan" <ncoghlan(a)redhat.com>
> > To: "beaker-devel" <beaker-devel(a)lists.fedorahosted.org>
> > Sent: Monday, November 25, 2013 4:15:45 PM
> > Subject: [Beaker-devel] Questions regarding DHCP/DNS requirements for
> > IPv6 support
> >
> > This is mostly aimed at Amit (since he's been looking into this lately),
> > but I've been pondering exactly what is needed from an environmental
> > point of view to enable testing of IPv6-only systems directly within
> > Beaker.
> >
> > My current understanding of the supporting config Beaker needs to
> > support this is below, so my general questions are: a) did I miss
> > anything?; and b) is anything I have listed wrong?
> >
> > * Main beaker server
> >
> > - needs both A and AAAA records assigned in DNS
> > - needs to serve the task library yum repo over both IPv4 and IPv6
> >
> > * Lab controllers
> >
> > - need both A and AAAA records assigned in DNS
> > - beaker-proxy needs to listen on both IPv4 and IPv6 (implemented in
> > 0.14.4)
> > - TFTP server needs to be serving over both IPv4 and IPv6
> >
>
> In beaker-provision we would also need to change how we write out
> our PXE config file. We only support IPv4 at the moment. I'm guessing it is
> more or less
> as simple as s/socket.gethostbyname/socket.getaddrinfo/.
This is an interesting point. I think that the current pressure to
support IPv6-only is just about the *harness* running with IPv4 turned
off -- I don't think it matters that the system was first installed over
IPv4. Mainly because PXE (the Intel firmware/protocol) is IPv4-only
anyway.
My mistake, I assumeed by the comment 'IPv6-only systems' that the system
would never have IPv4 available to it (ever!).
UEFI network booting apparently supports IPv6 though, somehow or
other
(I noticed my new laptop offers it). So Beaker may need to support it in
future. But it's a completely separate issue to the harness talking over
IPv6.
--
Dan Callaghan <dcallagh(a)redhat.com>
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
_______________________________________________
Beaker-devel mailing list
Beaker-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/beaker-devel