Allow configuration of dhcp_domain in nova.conf
Bug #1482045 reported by
Jordan Callicoat
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-ansible |
Fix Released
|
Wishlist
|
Jesse Pretorius | ||
Kilo |
Fix Released
|
Wishlist
|
Jesse Pretorius | ||
Trunk |
Fix Released
|
Wishlist
|
Jesse Pretorius |
Bug Description
The dhcp_domain is used by the neutron-dhcp-agent for handing out the domain via DHCP option. However, we are using neutron-
The dhcp_domain option was parameterized for dhcp-agent in LP:#1430872. A similar option should be added to the nova.conf template so that instances querying the metadata API (e.g., via cloud-init) see a consistent hostname as what is handed out via DHCP.
Changed in openstack-ansible: | |
status: | Incomplete → Triaged |
importance: | Undecided → Wishlist |
assignee: | nobody → Jesse Pretorius (jesse-pretorius) |
tags: | added: low-hanging-fruit |
tags: | removed: low-hanging-fruit |
no longer affects: | openstack-ansible/juno |
To post a comment you must log in.
dhcp_domain in nova.conf should only be used for nova network, whereas we only deploy neutron at this stage and we have this facilitated in neutron via the variable neutron_dhcp_domain
Can you please provide more information about this? Was this Juno or Kilo?