Uploaded image for project: 'OCMUI - OpenShift Cluster Manager UI'
  1. OCMUI - OpenShift Cluster Manager UI
  2. OCMUI-1882

Simplify metal installer decision flow

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Core UI
    • True
    • Hide

      Needs PM and UX decisions around flow and usability.

      Show
      Needs PM and UX decisions around flow and usability.
    • True
    • OCPSTRAT-1312 - Create a RHEL9 build for FIPS-enabled OpenShift installations
    • OCMUI Core Sprint 256, OCMUI Core Sprint 257

      As noted in OCMUI-1881, prior to OCP 4.16 users wanting to install a cluster on baremetal needed to decide which installation method to use (IPI, UPI, or Agent) prior to downloading the installer, because IPI required a different method of obtaining the installer binary. This decision happens on the page https://console.redhat.com/openshift/install/metal

      Starting with OCP 4.16, the method of downloading the installer can be the same in each of the 3 cases. This offers us an opportunity to simplify the flow. At the https://console.redhat.com/openshift/install/metal stage, the user need only to choose whether to use the interactive assisted installation or to run from the command line. If they pick the latter then they can proceed to downloading the installer binary.

      Only after that do we need to direct them to choosing an installation method and following the relevant documentation for that method.

       

      Acceptance Criteria

      • Work with UX on new wording on Instructions page.
      • Remove intermediate 'card view' with multiple options, and go directly to new Instructions page.

          1.
          		 DOD: Training materials supplied to Support/SRE Sub-task Closed Undefined Unassigned
          2.
          		 DOD: Docs verified by QE Sub-task Closed Undefined Unassigned
          3.
          		 DOD: Docs completed and merged Sub-task Closed Undefined Unassigned
          4.
          		 DOD: All known issues captured and blockers resolved Sub-task Closed Undefined Unassigned
          5.
          		 DOD: All work items belonging to this Epic are complete Sub-task Closed Undefined Unassigned
          6.
          		 DOD: Code merged for regular build/release testing in the HAC Common CI/CD framework Sub-task Closed Undefined Unassigned
          7.
          		 DOD: CI runs successfully with test automation Sub-task Closed Undefined Unassigned
          8.
          		 DOD: Automated/Integrated tests complete Sub-task Closed Undefined Unassigned
          9.
          		 DOD: Architectural artifacts completed, reviewed and stored Sub-task Closed Undefined Unassigned
          10.
          		 DOD: Product Manager and UX signed off on solution Sub-task Closed Undefined Unassigned
          11.
          		 DOD: Acceptance criteria related to this Epic has been identified and met Sub-task Closed Undefined Unassigned

              Unassigned Unassigned
              zabitter Zane Bitter
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: