Support networks' dns_domain option

Bug #1777978 reported by Numan Siddique
6
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
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-ovn (master)

Reviewed: https://review.openstack.org/556580
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=fb1b29e74ae7bfe30894fc0a0b840da697fecaee
Submitter: Zuul
Branch: master

commit fb1b29e74ae7bfe30894fc0a0b840da697fecaee
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
    additional record in the DNS.records column as
    <port host_name>.<net_dns_domain>=<IP ADDRESSES>

    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
    and I think it is better if we store the dns name of a port in
    Logical_Switch_Port.options column and the dns domain name and network's domain
    name in Logical_Switch.options and let ovn-northd read these values and update
    the OVN SB DB 'DNS' table. I will pursue this approach before addressing the
    above TODO.

    Change-Id: Ic9068d4bbb4602aa9d8c5d9cce8457b39057c802
    Partial-bug: #1777978

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-ovn (stable/queens)

Fix proposed to branch: stable/queens
Review: https://review.openstack.org/584940

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-ovn (stable/queens)

Reviewed: https://review.openstack.org/584940
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=fdff1ffa5c64b4898f25cb99bbe6001ebcab3321
Submitter: Zuul
Branch: stable/queens

commit fdff1ffa5c64b4898f25cb99bbe6001ebcab3321
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
    additional record in the DNS.records column as
    <port host_name>.<net_dns_domain>=<IP ADDRESSES>

    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
    and I think it is better if we store the dns name of a port in
    Logical_Switch_Port.options column and the dns domain name and network's domain
    name in Logical_Switch.options and let ovn-northd read these values and update
    the OVN SB DB 'DNS' table. I will pursue this approach before addressing the
    above TODO.

    Change-Id: Ic9068d4bbb4602aa9d8c5d9cce8457b39057c802
    Partial-bug: #1777978
    (cherry picked from commit fb1b29e74ae7bfe30894fc0a0b840da697fecaee)

tags: added: in-stable-queens
Revision history for this message
root (maxbomb) wrote : Re: [Bug 1777978] Re: Support networks' dns_domain option

Cheak ...

في الأربعاء، ٦ مارس، ٢٠١٩ ١٠:٠٠ م OpenStack Infra <
<email address hidden>> كتب:

> Reviewed: https://review.openstack.org/584940
> Committed:
> https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=fdff1ffa5c64b4898f25cb99bbe6001ebcab3321
> Submitter: Zuul
> Branch: stable/queens
>
> commit fdff1ffa5c64b4898f25cb99bbe6001ebcab3321
> 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
> additional record in the DNS.records column as
> <port host_name>.<net_dns_domain>=<IP ADDRESSES>
>
> 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
> and I think it is better if we store the dns name of a port in
> Logical_Switch_Port.options column and the dns domain name and
> network's domain
> name in Logical_Switch.options and let ovn-northd read these values
> and update
> the OVN SB DB 'DNS' table. I will pursue this approach before
> addressing the
> above TODO.
>
> Change-Id: Ic9068d4bbb4602aa9d8c5d9cce8457b39057c802
> Partial-bug: #1777978
> (cherry picked from commit fb1b29e74ae7bfe30894fc0a0b840da697fecaee)
>
>
> ** Tags added: in-stable-queens
>
> --
> You received this bug notification because you are subscribed to
> networking-ovn.
> Matching subscriptions: root
> https://bugs.launchpad.net/bugs/1777978
>
> Title:
> Support networks' dns_domain option
>
> Status in networking-ovn:
> In Progress
>
> Bug description:
> We don't support this yet in networking-ovn.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/networking-ovn/+bug/1777978/+subscriptions
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.