Uploaded image for project: 'OpenShift SDN'
  1. OpenShift SDN
  2. SDN-1755

Core Networking Debuggability

XMLWordPrintable

    • Core Networking Debuggability
    • False
    • False
    • Done
    • OCPPLAN-6007 - OpenShift Core Networking Improvements
    • OCPPLAN-6007OpenShift Core Networking Improvements
    • 0% To Do, 0% In Progress, 100% Done
    • Undefined
    • 0
    • 0

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      • Continue to improve the debugability of the product

      Why is this important?

      • The SDN is challenging to inspect and debug because of the volume of traffic, the transitory nature of problems, the distributed aspect (a problem on a remote system can cause the symptom to appear elsewhere)
      • Making the system self-diagnosing (as much as possible)
      • Making it easier for customers to inspect and diagnose problems prevents calls
      • Making it easier for support to help customers inspect and diagnose problems, or start debugging issues prevents engineering engagements
      • Making it easier for engineering to focus in on the actual problems reduces time to resolution

      Scenarios

      1. We should enhance the existing network health checks
      2. We should make sure that all health check data is surfaced in a useful way and included in the must-gather
      3. We should make tooling that can run against a must-gather so that we can identify common issues, or pull useful data out from the heap of data

      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. None known

      Previous Work (Optional):

      1. https://issues.redhat.com/browse/SDN-1132

      Open questions::

      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>

              npinaeva@redhat.com Nadia Pinaeva
              bbennett@redhat.com Ben Bennett
              Mehul Modi Mehul Modi
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: