After thinking about support for ipv6 + dhcpv6 in smart-poxy and Foreman some more, I realized that:
- while host duid management is possible, it’s going to be somewhat involved (quite a few different scenarios) and possibly fragile - dhcp servers can be configured to update dns records automatically using hostname (and domain name, if required) that client passes with dhcp request (or names can be generated automatically) - Foreman's main requirement is to set correct pxe boot options for managed hosts - multiple dhcp servers can co-exist on the same network/network segment, with responses selected by the client based on server precedence This leads me to think that having a small dhcp server (that we can interface with using a convenient set of api) dedicated to handling pxe requests in a given network segment and ignoring all request is an option that’s worth investigating. Turns out google has a project that fits the bill (https://github.com/google/netboot). I’m trying to establish a contact with project’s maintainers to find out about dhcpv6 state (not currently implemented) and see if they need help. Cheers, -d On Wed, Mar 8, 2017 at 11:53 AM, Lukas Zapletal <l...@redhat.com> wrote: > We can always try to offload the work on platform team, I've been > pretty successful in getting some work done in iPXE project for > example. The only issue is this can take some time until it gets to > the other team backlog. > > To be honest, I don't know which path you should take. I'd vote for > the cleanest one, that is trying to push proper IPv6 into ISC. If > there's no politics behind it, I don't believe they would not want to > have this kind of feature. On the other hand, they've been resisting > quite long time now (IPv6 is old how much, 20 years? :-) > > Since you already did great amount of investigation in the IPv6 field, > do you want to give dnsmasq a look in this regard? If this turns out > to be a good workaround, maybe the ISC IPv6 would not be so hot topic > then (when I finish with my provider). > > LZ > > On Tue, Mar 7, 2017 at 5:37 PM, Dmitri Dolguikh <witlessb...@gmail.com> wrote: >> On Tue, Mar 7, 2017 at 4:28 PM, Perry Gagne <pga...@redhat.com> wrote: >>> Wouldn't it be better to add support for fixed-address6 or is there some >>> issue with doing that? >> >> It looks to me like ISC aren’t really interested in extending >> functionality of dhcpd. On top of this, it may actually be more work >> than it looks: both memory db serialization and omapi need updates >> (the latter accepts fixed-addresses only atm). I have a pretty >> high-level understanding of dhcpd codebase, but even at this level it >> looks like omapi-related change might be quite big in scope. >> >> -d >> >>> >>> On Tue, Mar 7, 2017 at 11:27 AM, Dmitri Dolguikh <witlessb...@gmail.com> >>> wrote: >>>> >>>> On Tue, Mar 7, 2017 at 4:22 PM, Perry Gagne <pga...@redhat.com> wrote: >>>> >> This is definitely the case as far as ipv6-specific dhcpd >>>> >> configuration goes. The code I linked to is responsible for >>>> >> persistence of in-memory host records, and it doesn’t support ipv6 at >>>> >> all. >>>> > >>>> > Maybe I am confused. Are you trying to add support for fixed-address6 or >>>> > trying to work around the support not being there? >>>> >>>> The latter. >>>> -d >>>> >>>> > >>>> > On Mon, Mar 6, 2017 at 11:32 AM, Dmitri Dolguikh <witlessb...@gmail.com> >>>> > wrote: >>>> >> >>>> >> On Mon, Mar 6, 2017 at 4:11 PM, Perry Gagne <pga...@redhat.com> wrote: >>>> >> > >>>> >> > Doesn't ISC DHCPD use " fixed-address6", "range6", etc for DHCPv6. >>>> >> > The >>>> >> > code >>>> >> > you linked seems to be related to "fixed-address" which is the ipv4 >>>> >> > variant. >>>> >> > >>>> >> >>>> >> This is definitely the case as far as ipv6-specific dhcpd >>>> >> configuration goes. The code I linked to is responsible for >>>> >> persistence of in-memory host records, and it doesn’t support ipv6 at >>>> >> all. >>>> >> >>>> >> > Another question I have, does DHCP really need to be the one >>>> >> > assigning >>>> >> > the >>>> >> > address? Should DHCP just be providing config info, and leave the >>>> >> > address up >>>> >> > to SLAAC? [1] >>>> >> >>>> >> It is possible to use autoconf for IPv6 address (self-)assignment and >>>> >> rely on dhcp for host configuration only. I’m not sure how useful >>>> >> autoconf is in larger networks (anyone has experience with this?), but >>>> >> it has a potential for making our life harder. >>>> >> >>>> >> -d >>>> >> >>>> >> > >>>> >> > >>>> >> > [1] https://tools.ietf.org/html/rfc3736 >>>> >> > >>>> >> >>>> >> -- >>>> >> You received this message because you are subscribed to the Google >>>> >> Groups >>>> >> "foreman-dev" group. >>>> >> To unsubscribe from this group and stop receiving emails from it, send >>>> >> an >>>> >> email to foreman-dev+unsubscr...@googlegroups.com. >>>> >> For more options, visit https://groups.google.com/d/optout. >>>> > >>>> > >>>> > -- >>>> > You received this message because you are subscribed to the Google >>>> > Groups >>>> > "foreman-dev" group. >>>> > To unsubscribe from this group and stop receiving emails from it, send >>>> > an >>>> > email to foreman-dev+unsubscr...@googlegroups.com. >>>> > For more options, visit https://groups.google.com/d/optout. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "foreman-dev" group. >>>> To unsubscribe from this group and stop receiving emails from it, send an >>>> email to foreman-dev+unsubscr...@googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "foreman-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to foreman-dev+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-dev+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. > > > > -- > Later, > Lukas @lzap Zapletal > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
