Uploaded image for project: 'Performance and Scale for AI Platforms'
  1. Performance and Scale for AI Platforms
  2. PSAP-494

Address the technical debt carried from previous NTO releases

    XMLWordPrintable

Details

    • NTO technical debt
    • False
    • False
    • Done
    • 100
    • 100% 100%
    • Undefined

    Description

      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

      • Clear the technical debt to keep the project clean and address some documentation issues; in no particular order:
        • cleanup of the NTO Makefile; get rid of yq and use the openshift-supported openshift/build-machinery-go patching system
        • optionally increase verbosity for openshift-tuned and the operator (will be messy wrt. API)
        • Work with the DOC writers to create a diagram for the MachineConfigLabels functionality
        • DOC: nodes with both both master/worker roles and targeting non-custom MCPs – use master not worker pool
        • SNO consider removing leader election: 
          Investigate how to safely disable leader election for NTO on SNO clusters.  See what is the correct way of dealing with BZ1986477 on SNO.  Perhaps we can use a special deployment manifest for SNO?  Or use the node annotations: machineconfiguration.openshift.io/controlPlaneTopology: HighlyAvailable|SingleReplica to skip leader election on SNO clusters.

      Why is this important?

      • Operator performance, easier maintenance and better product documentation.

      Scenarios

      1. ...

      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>

      Attachments

        Issue Links

          is cloned by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. PSAP-641 Address the technical debt carried from previous NTO releases

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. PSAP-733 4.12: Address the technical debt carried from previous NTO releases

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Activity

            People

              jmencak Jiri Mencak
              jmencak Jiri Mencak
              Liquan Cui Liquan Cui
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: