Uploaded image for project: 'Fast Datapath Product'
  1. Fast Datapath Product
  2. FDP-2904

[RFE] Make OVN DNS TTL configurable

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • OVN
    • None
    • [RFE] Make OVN DNS TTL configurable
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      ( ) The acceptance criteria defined below are met.

      ( ) The epics work is available in a downstream build (nightly/async or other)

      ( ) Test coverage is available in downstream CI if applicable

      ( ) All cards under the epic have been moved to Done

      ( ) Failed Test Plans have bugs added as children to the epic/feature.

      Show
      Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) The acceptance criteria defined below are met. ( ) The epics work is available in a downstream build (nightly/async or other) ( ) Test coverage is available in downstream CI if applicable ( ) All cards under the epic have been moved to Done ( ) Failed Test Plans have bugs added as children to the epic/feature.
    • rhel-9
    • rhel-net-ovn
    • 100% To Do, 0% In Progress, 0% Done
    • ssg_networking

      This epic tracks all the effort needed to deliver the solution related to the feature request described below.

      What's the feature?

      Currently, if OVN is configured to reply for DNS requests, it always replies with a hardcoded DNS_DEFAULT_RR_TTL, with is 3600 seconds.  It should be configurable instead.

      Why is it needed?

      In a dynamic cloud environment workloads can come and go quickly.  Services can be re-spawned on different IP addresses.  But if other workloads may cache the DNS reply for up to an hour, they may have trouble connecting to the service that was moved to a different IP.  For example, default DNS TTL in OpenShift is just 5 seconds, which allows a very fast service fail-over to a new pod.

      Who will benefit? 

      OpenStack allows to use OVN DNS for VMs and services running in it.  This may be a good thing to have TTL configurable, so the connection issues can be avoided on VM fail-over.  Other environments may also find this functionality useful.

              ovnteam@redhat.com OVN Team
              imaximet@redhat.com Ilya Maximets
              OVN QE OVN QE
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: