yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1112884@xxxxxxxxxxxxxxxxxx>]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
       Status: Incomplete => Expired

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

Title:
  Allow customer-specified per-subnet and per-host DNS entries

Status in neutron:
  Expired

Bug description:
  We're running an operational OpenStack Folsom + Quantum cluster
  configured to host multiple tenants, each having their own subnet. It
  seems like you can only have one domain for all tenants, which seems
  like an artificial limitation since each dnsmasq process can take a
  different --domain argument. It also seems like only a translation of
  the VMs IP address is placed into the dnsmasq file. There is also no
  way to specify a DNS entry for the VM.

  Allow dhcp_domain to be set on a per-subnet basis via quantum. It
  could be done as an optional parameter for each subnet tracked by
  quantum, much like 'start' and 'end' for the allocation_pools. Doing
  so would ensure that any DHCP address received by VMs started in that
  subnet would set their search domain to the per-subnet dhcp_domain.
  The hostname would thus be - VM_NAME + '.' + DHCP_DOMAIN

  In addition to the feature above, the customer could specify an
  alternative hostname entry to place into the dnsmasq configuration.

  For example, assume the dhcp_domain selected for the tenant was
  'example.com'. They launch a named 'web-1' with an IP of 10.0.0.5.
  They specify that they also want this VM to be called 'web.blue.com',
  the following entries would be placed into the dnsmasq host file:

  fa:16:3e:76:56:11,10-0-0-5.example.com,10.0.0.5
  fa:16:3e:76:56:11,web-1.example.com,10.0.0.5
  fa:16:3e:76:56:11,web.blue.com,10.0.0.5

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