Uploaded image for project: 'OpenShift Specialist Platform Team'
  1. OpenShift Specialist Platform Team
  2. SPLAT-557

[aws][local-zones] research - create a cluster with MachineSets in Local Zones(day-0)

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Major
    • None
    • Alongside OpenShift 4.11

    Description

      As a Customer I would like to install a OpenShift cluster with support of MachineSets in AWS Local Zones for compute nodes on Day-0, so I can deploy user-workloads with sensitive latency close to the end users.

      This research complements the Day-2 to deploy MachineSet for compute nodes on AWS Local Zones[2].

      DESCRIPTION

      Research if it's possible to create an OCP cluster with compute machines in an subnet located in AWS Local Zone.

      This card will help DOC and QE team to create the product documentation to create a cluster with support of compute nodes MachineSet on Local Zones as Day-0 Operation.

      Goal:

      Document the steps to create a cluster with 4.11 installer under the following circumstances:
      1) The user deploys OCP on an existing network
      2) The user manually modifies the MachineSet manifest prior to deployment to include:

      • Representative name and label suffixes for the Local Zone
      • Volume type to the one supported in Local Zones, "gp2"
      • Instance type to the ones supported in Local Zones
      • Availability Zone name for the Local Zone
      • Subnet name to the one created by the user in the Local Zone

       

      ENGINEERING DOC

      [1] AWS Local Zone doc: https://aws.amazon.com/about-aws/global-infrastructure/localzones
      [2] Initial Research for Day-2: https://issues.redhat.com/browse/SPLAT-526 

       

      Attachments

        Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SPLAT-558 [aws][local-zones] research - deploy a new ingress-controller for ALB on Local Zones

          • 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
          is related to

          Feature Request - Feature requests from customers and/or users RFE-2782 AWS Local Zone Support for OCP UPI/IPI

          • 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.
          • Accepted

          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

          Activity

            People

              rhn-support-mrbraga Marco Braga
              rhn-support-mrbraga Marco Braga
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 week, 1 day
                  1w 1d