XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • None
    • Minimal ISO
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-883 - Agent Minimal ISO Support
    • OCPSTRAT-883Agent Minimal ISO Support
    • 75% To Do, 25% In Progress, 0% Done

      Epic Goal

      • Allow the user to create the Agent ISO image as a minimal ISO (sans rootfs). We already support/require this for the external platform; we should make it possible on any platform.

      Why is this important?

      • Some BMCs do not support images as large as the 1GB CoreOS ISO when using virtualmedia. By generating a minimal ISO, we unlock use of the agent installer on these servers

      Scenarios

      1. User in a connected environment generates a minimal ISO; rootfs is automatically downloaded from mirror.openshift.com.
      2. User in a disconnected environment generates a minimal ISO and rootfs, then uploads the rootfs to the bootArtifactsBaseURL they specified in agent-config.yaml.
      3. By default users continue to generate a fully self-contained ISO (except on the external platform).

      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. ...

      Previous Work (Optional):

      1. AGENT-656 implemented minimal ISO support in the agent-based installer, including support for minimal ISOs in disconnected environments, for the external platform only. There is no UI to select this, as the external platform is assumed to always require a minimal ISO.

      Open questions::

      1. How the user should request a minimal ISO. Perhaps openshift-install agent create minimal-image?

      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
            zabitter Zane Bitter
            pawan pinjarkar
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: