yahoo-eng-team team mailing list archive

[Brian Haley <1860488@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Some PXE implementations, including iPXE, use vendor-specific options
encapsulated in a single top-level option to send configuration data in
DHCP packets. As an example, iPXE encapsulates various options in option
175.

This is fully supported by dnsmasq (see below), however, the original
code which translates a DHCP option name and value into a dnsmasq
command-line argument would expect any non-numeric option 'name' to be a
named option, hence prepending with `option:`.

The dhcp agent should be changed to ensure `encap:X,Y` is properly translated
into either `encap:X,Y` if Y is numerical, or `encap:X,option:Y` if Y is text.

** Affects: neutron
     Importance: Medium
     Assignee: Brian Haley (brian-haley)
         Status: In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1860488

Title:
  Encapsulated DHCP options are not supported in neutron

Status in neutron:
  In Progress

Bug description:
  Some PXE implementations, including iPXE, use vendor-specific options
  encapsulated in a single top-level option to send configuration data in
  DHCP packets. As an example, iPXE encapsulates various options in option
  175.

  This is fully supported by dnsmasq (see below), however, the original
  code which translates a DHCP option name and value into a dnsmasq
  command-line argument would expect any non-numeric option 'name' to be a
  named option, hence prepending with `option:`.

  The dhcp agent should be changed to ensure `encap:X,Y` is properly translated
  into either `encap:X,Y` if Y is numerical, or `encap:X,option:Y` if Y is text.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1860488/+subscriptions