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

[platform-external[aws][CI] Create end-to-end test for External platform that runs on AWS

    XMLWordPrintable

Details

    • Sprint 249, Sprint 248, Sprint 243, Sprint 244, Sprint 245, Sprint 246, Sprint 247, Sprint 250, OpenShift SPLAT - Sprint 255

    Description

      Background

      As a followup to OCPCLOUD-1782, we should create an "External" platform type test that is run on AWS infrastructure. There are currently a few platform "None" steps that are associated with AWS in the ci-operator, these should be used as reference for building a new test that will deploy OpenShift on AWS using platform "External". This will be similar to the vSphere platform "None" (and platform "External" from 1782) tests with the major exception of using AWS as the infrastructure.

      Steps

      • investigate AWS platform None tests
      • create new steps to deploy a platform External for AWS
      • create a new workflow/chain to capture a full test run
      • create a new job in ci-operator to run as a periodic test, once a week to begin with

      Stakeholders

      • openshift eng

      Definition of Done

      • platform External test is passing on AWS
      • Docs
      • n/a
      • Testing
      • n/a

      Attachments

        Issue Links

          clones

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OCPCLOUD-1911 Create end-to-end test for External platform that runs on AWS

          • 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.
          • To Do
          duplicates

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OCPCLOUD-1911 Create end-to-end test for External platform that runs on AWS

          • 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.
          • To Do
          is blocked by

          Task - Represents a small unit of work that is not end-user facing. SPLAT-1425 [platform-external] Create support of "platform external" in the CI e2e workflow

          • 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 cloned by

          Spike - Represents a research-related task. SPLAT-1368 [platform-external[aws][CI] Research: Create end-to-end test for External platform that runs on OCI

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • To Do
          links to

          GitHub openshift/release#45921: SPLAT-1158: platform-external - provision cluster and install CCM with native e2e

          Activity

            People

              rhn-support-mrbraga Marco Braga
              mimccune@redhat.com Michael McCune
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: