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

Ensure interoperability with ZTP

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • None
    • ZTP Interop
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • To Do
    • 91% To Do, 9% In Progress, 0% Done

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

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

      Agent installer interoperability with ZTP

      • Ensure that manifests generated by agent create cluster-manifests are sufficient (when combined with appropriate BareMetalHost resources) to stand up a cluster using ZTP.
      • Ensure that manifests generated by SiteConfig can be added to the cluster-manifests directory and used to generate an appropriate agent ISO using agent create image.

      Why is this important?

      • Previously, the install-config and SiteConfig/ZTP have been two parallel but unrelated paths to creating a cluster automatically. The agent installer provides an opportunity to tell a story about how they are related, and allows users to select different installation methods depending on their needs while starting from the same configuration.

      Scenarios

      1. User generates ZTP manifests from an install-config using the agent create cluster-manifests command, then applies them to a MCE cluster with oc apply to create a cluster.
      2. User generates ZTP manifests from a SiteConfig and copies them to the cluster-manifests directory, then generates an agent ISO with agent create image and manually boots the ISOs to install.

      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):

      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 - Downstream documentation merged: <link to meaningful PR>

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

              Created:
              Updated: