Support networks' dns_domain option
Bug #1777978 reported by
Numan Siddique
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-ovn |
In Progress
|
Undecided
|
Numan Siddique |
Bug Description
We don't support this yet in networking-ovn.
Changed in networking-ovn: | |
assignee: | nobody → Numan Siddique (numansiddique) |
status: | New → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/556580 /git.openstack. org/cgit/ openstack/ networking- ovn/commit/ ?id=fb1b29e74ae 7bfe30894fc0a0b 840da697fecaee
Committed: https:/
Submitter: Zuul
Branch: master
commit fb1b29e74ae7bfe 30894fc0a0b840d a697fecaee
Author: Numan Siddique <email address hidden>
Date: Thu Mar 22 16:07:26 2018 +0530
Support per network dns domain name in internal OVN dns
If user has set network's dns_domain attribute, this patch stores an .<net_dns_ domain> =<IP ADDRESSES>
additional record in the DNS.records column as
<port host_name>
This patch doesn't handle the scenario when a network's dns_domain
is updated. This is presently left as TODO and it will be supported
as a follow up patch.
Handling the DNS entries in the OVN NB DB seems to become more complicated Switch_ Port.options column and the dns domain name and network's domain Switch. options and let ovn-northd read these values and update
and I think it is better if we store the dns name of a port in
Logical_
name in Logical_
the OVN SB DB 'DNS' table. I will pursue this approach before addressing the
above TODO.
Change-Id: Ic9068d4bbb4602 aa9d8c5d9cce845 7b39057c802
Partial-bug: #1777978