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

Above-the-sea UI integration with Below-the-sea UI

XMLWordPrintable

    • Above-the-sea UI integration with Below-the-sea UI
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • In Progress
    • OCPSTRAT-2348 - [Tech Preview - Ph 2] Agent Installer for OpenShift Virtualization
    • OCPSTRAT-2348[Tech Preview - Ph 2] Agent Installer for OpenShift Virtualization
    • 79% To Do, 7% In Progress, 14% Done
    • S
    • Hide

      13 Oct: Documented various possible approaches and held design discussions via a shared doc https://docs.google.com/document/d/1rnAUIKOaJLDhIOxIzQgk66oYaPUgpOdsno3_SgqDAg8/edit?tab=t.0#heading=h.onjx48w2uk3d 

       

      Successfully did a demo for the late binding POC which will be the way to proceed.

      Show
      13 Oct: Documented various possible approaches and held design discussions via a shared doc https://docs.google.com/document/d/1rnAUIKOaJLDhIOxIzQgk66oYaPUgpOdsno3_SgqDAg8/edit?tab=t.0#heading=h.onjx48w2uk3d     Successfully did a demo for the late binding POC which will be the way to proceed.

      Epic Goal

      • The user may provide a set of (optional) installation configs in the above-the-sea UI, before downloading the ISO. These info must be reused by the below-the-sea UI when started locally

      Why is this important?

      • Allows the user to customize the ISO with some specific customer installation details, so that every time a local installation is performed they will be provided automatically by the below-the-sea UI

      Scenarios

      1. ...

      Acceptance Criteria

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

      Dependencies (internal and external)

      1. https://issues.redhat.com/browse/MGMT-20830

      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>

              ppinjark@redhat.com pawan pinjarkar
              afasano@redhat.com Andrea Fasano
              Daniel Erez, Omer Vishlitzky, Rastislav Wagner
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: