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

R&D: Support for AWS ARM Instances

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • SDN Core
    • R&D: Support for AWS ARM Instances
    • False
    • False
    • To Do
    • 0
    • 0

      Goal: Identify gaps, if any, to support UPI OpenShift deployments on AWS ARM-based infrastructure for both openshift-sdn and ovn-kubernetes.

      Problem: Customers have a requirement to run workloads on ARM processor-based infrastructure, but currently there has not been an exploration on OpenShift's ability to support that infrastructure for networking components and features to determine what, if any, gaps exist in our ability to support it.

      Use Cases:

      • Edge deployments with minimum architecture resources, e.g. IoT, autom
      • Mitigating Intel and AMD dependency risks
      •  

      Open Questions:

      • Is this for openshift-sdn, ovn-kubernetes, or both?
      • Is there an SR-IOV requirement?
      • Does CI exist today for AWS ARM deployments?
      • This is AWS-only, with future goals of adding Azure and Bare Metal ARM-based infrastructures

      Dependencies (internal and external):

      Prioritized epics + deliverables (in scope / not in scope):

      Not in scope:

      •  
      •  

      Estimate (XS, S, M, L, XL, XXL):

      Previous Work:

      Acceptance criteria:

      Epic Done Checklist:

      • CI - CI Job & Automated tests: <link to CI Job & automated tests>
      • Release Enablement: <link to Feature Enablement Presentation> 
      • DEV - Upstream code and tests merged: <link to meaningful PR orf 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>
      • Notes for Done Checklist
        • Adding links to the above checklist with multiple teams contributing; select a meaningful reference for this Epic.
        • Checklist added to each Epic in the description, to be filled out as phases are completed - tracking progress towards “Done” for the Epic.

          There are no Sub-Tasks for this issue.

              Unassigned Unassigned
              mcurry@redhat.com Marc Curry
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: