Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-165

Day 2 Multi-architecture compute support for Azure (GA)

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-10Install and update OpenShift on Infrastructure Providers
    • 100
    • 100% 100%
    • 0
    • 0

      Feature Overview (aka. Goal Summary)  

      Allow Arm architecture nodes to be added to an existing Azure OpenShift x86 architecture cluster as a day 2 operation.

      Why is this important?
      Arm architecture based systems have been heavily adopted by multiple cloud providers (including AWS) and we need to provide support for those platforms
      It is not always possible to have all the applications in a cluster available on Arm so it is necessary to be able to have a mixed architecture cluster

      Goals (aka. expected user outcomes)

      Add an Azure Arm instance to a running OpenShift on Azure cluster (day 2 operation)

      Requirements (aka. Acceptance Criteria):

      A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

       

      Use Cases (Optional):

      Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

       

      Questions to Answer (Optional):

      Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

       

      Out of Scope

      Day 1 (installation) of mixed architecture clusters)
      Conversion of mixed architecture clusters to single architecture clusters

       

      Background

      Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

       

      Customer Considerations

      Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

       

      Documentation Considerations

      Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

       

      Interoperability Considerations

      Which other projects and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

            Unassigned Unassigned
            rhn-support-dhardie Duncan Hardie
            Prashanth Sundararaman Prashanth Sundararaman
            Jon Thomas Jon Thomas
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: