[RFE] no relation exists to set upstream DNS servers based on server pools managed by designate
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Designate Charm |
Triaged
|
Medium
|
Pedro Guimarães | ||
OpenStack Designate-Bind Charm |
In Progress
|
Medium
|
Pedro Guimarães | ||
OpenStack Neutron Gateway Charm |
In Progress
|
Medium
|
Pedro Guimarães | ||
OpenStack Neutron Open vSwitch Charm |
In Progress
|
Medium
|
Pedro Guimarães |
Bug Description
There is currently a config option called "dns-servers" to set nameserver IP addresses used by dnsmasq as forwarders.
https:/
Providing those addresses via config is far from being flexible if Designate is used with a managed pool of servers (e.g., provided by designate-bind charm).
instance -> dnsmasq -> bind9 (managed by designate-bind charm) -> upstream DNS server
In order to provide external name resolution for instances designate-bind charm also needs to configure recursion in bind9 config (currently recursion is disabled) and allow queries from IP addresses of compute nodes hosting dnsmasq daemons.
NOTE: given that designate can manage multiple pools of different backends (e.g. bind9, InfoBlox, PowerDNS etc.) it makes sense to consider providing dns-servers via a neutron-ovs <-> designate relation.
description: | updated |
Changed in charm-designate: | |
status: | New → Triaged |
Changed in charm-designate-bind: | |
status: | New → Triaged |
Changed in charm-neutron-openvswitch: | |
status: | New → Triaged |
Changed in charm-designate: | |
importance: | Undecided → Medium |
Changed in charm-designate-bind: | |
importance: | Undecided → Medium |
Changed in charm-neutron-openvswitch: | |
importance: | Undecided → Medium |
Changed in charm-designate: | |
milestone: | none → 18.08 |
Changed in charm-designate-bind: | |
milestone: | none → 18.08 |
Changed in charm-neutron-openvswitch: | |
milestone: | none → 18.08 |
Changed in charm-designate: | |
assignee: | nobody → Pedro Guimarães (pguimaraes) |
Changed in charm-designate-bind: | |
assignee: | nobody → Pedro Guimarães (pguimaraes) |
Changed in charm-neutron-openvswitch: | |
assignee: | nobody → Pedro Guimarães (pguimaraes) |
Changed in charm-neutron-gateway: | |
assignee: | nobody → Pedro Guimarães (pguimaraes) |
milestone: | none → 18.08 |
Changed in charm-designate-bind: | |
status: | Triaged → In Progress |
Changed in charm-neutron-gateway: | |
milestone: | 18.08 → 18.11 |
Changed in charm-neutron-openvswitch: | |
milestone: | 18.08 → 18.11 |
Changed in charm-designate: | |
milestone: | 18.08 → 18.11 |
Changed in charm-designate-bind: | |
milestone: | 18.08 → 18.11 |
tags: | added: canonical-bootstack |
Changed in charm-neutron-openvswitch: | |
milestone: | 18.11 → 19.04 |
Changed in charm-designate: | |
milestone: | 18.11 → 19.04 |
Changed in charm-designate-bind: | |
milestone: | 18.11 → 19.04 |
Changed in charm-neutron-gateway: | |
milestone: | 18.11 → 19.04 |
Changed in charm-neutron-gateway: | |
importance: | Undecided → Medium |
Changed in charm-neutron-openvswitch: | |
milestone: | 19.04 → 19.07 |
Changed in charm-designate: | |
milestone: | 19.04 → 19.07 |
Changed in charm-designate-bind: | |
milestone: | 19.04 → 19.07 |
Changed in charm-neutron-gateway: | |
milestone: | 19.04 → 19.07 |
Changed in charm-neutron-openvswitch: | |
milestone: | 19.07 → 19.10 |
Changed in charm-designate: | |
milestone: | 19.07 → 19.10 |
Changed in charm-designate-bind: | |
milestone: | 19.07 → 19.10 |
Changed in charm-neutron-gateway: | |
milestone: | 19.07 → 19.10 |
Changed in charm-neutron-openvswitch: | |
milestone: | 19.10 → 20.01 |
Changed in charm-designate: | |
milestone: | 19.10 → 20.01 |
Changed in charm-designate-bind: | |
milestone: | 19.10 → 20.01 |
Changed in charm-neutron-gateway: | |
milestone: | 19.10 → 20.01 |
Changed in charm-neutron-openvswitch: | |
milestone: | 20.01 → 20.05 |
Changed in charm-designate: | |
milestone: | 20.01 → 20.05 |
Changed in charm-designate-bind: | |
milestone: | 20.01 → 20.05 |
Changed in charm-neutron-gateway: | |
milestone: | 20.01 → 20.05 |
Changed in charm-neutron-openvswitch: | |
milestone: | 20.05 → 20.08 |
Changed in charm-designate: | |
milestone: | 20.05 → 20.08 |
Changed in charm-designate-bind: | |
milestone: | 20.05 → 20.08 |
Changed in charm-neutron-gateway: | |
milestone: | 20.05 → 20.08 |
Changed in charm-neutron-openvswitch: | |
milestone: | 20.08 → none |
Changed in charm-designate: | |
milestone: | 20.08 → none |
Changed in charm-designate-bind: | |
milestone: | 20.08 → none |
Changed in charm-neutron-gateway: | |
milestone: | 20.08 → none |
> In order to provide external name resolution for instances designate-bind charm also needs to configure recursion in bind9 config (currently recursion is disabled) and allow queries from IP addresses of compute nodes hosting dnsmasq daemons.
FWIW, Dmitrii opened another bug around recursive name resolution as: /bugs.launchpad .net/charm- designate- bind/+bug/ 1776952
https:/
It can be discussed there instead of the scope of designate-neutron relation to pass forwarders.