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

Convert the install-config to ZTP assets

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Critical
    • None
    • None
    • None
    • None
    • Agent Sprint 222

    Description

      Given an install-config, convert it to the ZTP manifests that are used to directly populate the Ignition.

      This document contains a list of fields and how they match up: https://docs.google.com/document/d/1S4OluK1c-CIma9hmEylPay9ugcqKrD64S7DgiYpufqE/edit

      Attachments

        Issue Links

          depends on

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. AGENT-136 Create a pseudo-asset to allow an optional dependency on the install-config

          • Undefined - Priority not specified.
          • Closed
          is blocked by

          Task - Represents a small unit of work that is not end-user facing. AGENT-282 Generate ClusterDeployment asset from install config

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is depended on by

          Task - Represents a small unit of work that is not end-user facing. AGENT-277 Test cluster-manifests with ZTP

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • To Do
          is related to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. AGENT-281 Generate the NMStateConfig manifests from the agent-config

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. AGENT-280 Generate the mirroring configs from install-config

          • Undefined - Priority not specified.
          • Closed
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. AGENT-134 Convert ZTP code to asset model

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. AGENT-135 Create a ZTP-level representation of the release payload location

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          links to

          GitHub openshift/installer#6114: AGENT-282: Create cluster deployment asset manifest from install config

          GitHub openshift/installer#6134: AGENT-137: Convert the install-config to ZTP assets

          Activity

            People

              ppinjark@redhat.com pawan pinjarkar
              zabitter Zane Bitter
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: