Uploaded image for project: 'OpenShift Node'
  1. OpenShift Node
  2. OCPNODE-968

WorkerLatencyProfiles automation and rollback

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • None
    • None
    • WorkerLatencyProfiles enhancements follow up
    • False
    • None
    • False
    • Not Selected
    • To Do
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal

      Why is this important?

      • Allow automation while using WorkerLatencyProfiles

      Scenarios

      1. Be able to move from default to low WorkerLatencyProfiles
      2. System will log event if change fails, and rollback to previous state

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • Rollback of state if state change fails

      Dependencies (internal and external)

      1. MCO approval
      2. Openshift API approvalĀ 
      3. Workload approval

      Previous Work (Optional):

      1. None

      Open questions::

      1. None

      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>

              harpatil@redhat.com Harshal Patil
              harpatil@redhat.com Harshal Patil
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: