Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-8863

Support clusterOSImage for vSphere Disconnected

XMLWordPrintable

    • Support clusterOSImage for vSphere Disconnected
    • False
    • None
    • False
    • Green
    • To Do
    • ACM-3446 - RFE - have an option in UI console to add URL to internal OVA image
    • ACM-3446RFE - have an option in UI console to add URL to internal OVA image
    • 0% To Do, 0% In Progress, 100% Done

      OCP/Telco Definition of Done
      https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
      Epic Template descriptions and documentation.
      https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
      ACM-wide Product Requirements (Top-level Epics)
      https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit

      *<--- Cut-n-Paste the entire contents of this description into your new
      Epic --->*

      Epic Goal

      Allow customers to enter the cluster OS image for vSphere disconnected installations, either via the credentials or at deployment time in the wizard.

      Why is this important?

      This field is required for disconnected installations and customers should not need to manually edit the YAML editor contents.

      Scenarios

      1. Customer creates or edits a vSphere credential for disconnected installation and stores the Cluster OS image in it.
      2. Customer creates a vSphere disconnected cluster using a credential with the stored information.
      3. Customer creates a vSphere disconnected cluster, entering the cluster OS image in the wizard.

      Acceptance Criteria

      Customers can successfully deploy vSphere disconnected clusters without needing to edit install-config.yaml in the YAML editor.

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. ...

      Open questions:

      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 - Doc issue opened with a completed template. Separate doc issue
        opened for any deprecation, removal, or any current known
        issue/troubleshooting removal from the doc, if applicable.

              rh-ee-kcormier Kevin Cormier
              rh-ee-kcormier Kevin Cormier
              Atif Shafi Atif Shafi
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: