Uploaded image for project: 'On Prem Networking'
  1. On Prem Networking
  2. OPNET-567

Resolv-prepender Simplification

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • Resolv-prepender Simplification
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • To Do
    • 0% To Do, 33% In Progress, 67% Done

      Template:

      Networking Definition of Planned

      Epic Template descriptions and documentation

      Epic Goal

      Simplify the resolv-prepender process to eliminate consistently problematic aspects. Most notably this will include reducing our reliance on the dispatcher script for proper configuration of /etc/resolv.conf by replacing it with a systemd watch on the /var/run/NetworkManager/resolv.conf file.

      Why is this important?

      Over the past five years or so of on-prem networking, the resolv-prepender script has consistently been a problem. Most of these problems relate to the fact that it is triggered as a NetworkManager dispatcher script, which has proven unreliable, despite years of playing whack-a-mole with various bugs and misbehaviors. We believe there is a simpler, less bug-prone way to do this that will improve both the user experience and reduce the bug load from this particular area of on-prem networking.

      Planning Done Checklist

      The following items must be completed on the Epic prior to moving the Epic from Planning to the ToDo status

      • Priority+ is set by engineering
      • Epic must be Linked to a +Parent Feature
      • Target version+ must be set
      • Assignee+ must be set
      • (Enhancement Proposal is Implementable
      • (No outstanding questions about major work breakdown
      • (Are all Stakeholders known? Have they all been notified about this item?
      • Does this epic affect SD? {}Have they been notified{+}? (View plan definition for current suggested assignee)
        1. Please use the “Discussion Needed: Service Delivery Architecture Overview” checkbox to facilitate the conversation with SD Architects. The SD architecture team monitors this checkbox which should then spur the conversation between SD and epic stakeholders. Once the conversation has occurred, uncheck the “Discussion Needed: Service Delivery Architecture Overview” checkbox and record the outcome of the discussion in the epic description here.
        2. The guidance here is that unless it is very clear that your epic doesn’t have any managed services impact, default to use the Discussion Needed checkbox to facilitate that conversation.

      Additional information on each of the above items can be found here: Networking Definition of Planned

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement
        details and documents.

      ...

      Dependencies (internal and external)

      1.

      ...

      Previous Work (Optional):

      1. …

      Open questions::

      1. …

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

            mkowalsk@redhat.com Mat Kowalski
            bnemec@redhat.com Benjamin Nemec
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: