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

InstallConfig + agentConfig input

XMLWordPrintable

    • Support user input consisting of just InstallConfig and AgentConfig
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • Done
    • OCPPLAN-8150 - Agent-Based Installer GA
    • Impediment
    • OCPPLAN-8150Agent-Based Installer GA
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      The Agent-based installation supports two input modes:
      Preferred:
      * `install-config.yaml` file
      * `agent-config.yaml` file
       Optional:
      * Zero Touch Provisioning(ZTP) manifests
      With the preferred mode, you can configure the `install-config.yaml` file and specify Agent-based specific settings in the `agent-config.yaml` file.
      For more information, see xref:../../installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.adocl#about-the-agent-based-installer[About the Agent-based Installer].

      Show
      The Agent-based installation supports two input modes: Preferred: * `install-config.yaml` file * `agent-config.yaml` file  Optional: * Zero Touch Provisioning(ZTP) manifests With the preferred mode, you can configure the `install-config.yaml` file and specify Agent-based specific settings in the `agent-config.yaml` file. For more information, see xref:../../installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.adocl#about-the-agent-based-installer[About the Agent-based Installer].
    • Feature
    • Done

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

      Support user input consisting of just InstallConfig and AgentConfig

      Epic Goal

      • Allow users to generate an ephemeral agent based installation ISO from just installConfig and AgentConfig

      Why is this important?

      • While Zero Touch Provisioning Input is very amenable to automation, it is a more complex input for the user manually setting up a cluster.
      • InstallConfig is the canonical start point for OpenShift Installer installation
      • Some settings in ZTP are only available in BMH. InstallConfig and AgentConfig will allow customers that do not (or can't) use BMH/BMO to set the same things in their clusters

      Scenarios

      1. User writes InstallConfig with the general cluster config, AgentConfig with host specific config, then runs openshift-install agent create cluster-manifests, then openshift-install agent create image. After that, boots the target systems with the ISO and gets a successful first OCP cluster

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

      Open questions::

      1. Does openshift-install create cluster-manifests need to run explicitly?

      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>

          There are no Sub-Tasks for this issue.

              ppinjark@redhat.com pawan pinjarkar
              asegurap1@redhat.com Antoni Segura Puimedon
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: