Uploaded image for project: 'Agent-based Installer for OpenShift'
  1. Agent-based Installer for OpenShift
  2. AGENT-1002

Enable Agent-based Installer to install OCP on Oracle Private Cloud Appliance (PCA)

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • None
    • Enable Agent-based Installer to install OCP on Oracle Private Cloud Appliance (PCA)
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-1704 - OpenShift on Oracle Private Cloud Appliance (PCA)
    • OCPSTRAT-1704OpenShift on Oracle Private Cloud Appliance (PCA)
    • 100% To Do, 0% In Progress, 0% Done

      Epic Goal

      • Validate OCP deployment on Oracle Private Cloud Appliance (PCA) using the agent-based installer

      Why is this important?

      • There is a significant list of Oracle customers waiting to deploy OpenShift on Oracle Private Cloud Appliance (PCA) service. The Oracle eng team has validated this works already for Assisted and Agent-based installers but we'll need to e2e test the process to ensure this is working with no issues and doesn't require any changes from the agent-based side  

      Scenarios

      1. Use agent-based to deploy OCP on Oracle Private Cloud Appliance (PCA) for both connected and disconnected scenarios

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents

      Previous Work (Optional):

      1. The Oracle team has tested this already and demoed it to Red Hat last week. Jointly with Oracle we'll need to document e2e the process the same way we are doing for OpenShift on Oracle Cloud

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or 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>

              Unassigned Unassigned
              mak.redhat.com Marcos Entenza Garcia
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: