Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-2782

AWS Local Zone Support for OCP UPI/IPI

    XMLWordPrintable

Details

    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%

    Description

      AWS Local Zone Support for OCP UPI/IPI

      Current AWS Based OCP deployment models do not address Local Zones which offer lower latency and geo-proximity to OCP Cluster Consumers.

      OCP Install Support for AWS Local Zones will address Customer Segments where low latency and data locality requirements enforce as deal breaker/show-stopper for our sales teams engagements. 

      Attachments

        Issue Links

          is blocked by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. HIVE-2086 Support AWS Local Zones

          • Undefined - Priority not specified.
          • Closed
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. HIVE-2253 MachinePools (AWS): Support edge pool / Local Zones

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • In Progress

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SPLAT-636 AWS Local Zones - Phase I - IPI edge pool - Installer support to automatically create the MachineSets when installing in existing VPC

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SPLAT-635 AWS Local Zones - Phase 0 IPI - Document options to create compute nodes on Day-0

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SPLAT-657 AWS Local Zones - Phase II - IPI automation - Installer support to create resources in Local Zone for edge pool

          • 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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SPLAT-557 [aws][local-zones] research - create a cluster with MachineSets in Local Zones(day-0)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPPLAN-9630 Add support to AWS Local Zones (Phase 0)

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-222 Add support to AWS Local Zones (Phase I)

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-350 Add support to AWS Local Zones (Phase II)

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Spike - Represents a research-related task. SPLAT-526 [aws][local-zones] research - extend compute nodes using subnets in Local Zones [day-2]

          • 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
          links to

          GitHub openshift/enhancements#1232: installer-aws: create edge compute pool for AWS Local Zones

          GitHub openshift/installer#6371: RFE-2782: Create edge compute pool to support AWS Local Zones

          GitHub openshift/installer#6931: RFE-2782: Create edge compute pool to support AWS Local Zones

          GitHub openshift/installer#7137: SPLAT-657: AWS Local Zones subnets automation for edge compute pool

          Activity

            People

              mak.redhat.com Marcos Entenza Garcia
              fnar@redhat.com fatih nar
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: