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

Load data files using regular installer code

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Normal
    • None
    • None
    • None
    • None
    • Agent Sprint 219, Agent Sprint 220

    Description

      Using code from the installer (not code from fleeting), populate the Ignition asset with the data built in to the installer binary.

      Currently we use a separate embed.FS (inherited from fleeting) to load the data files to go into the ignition. We should get rid of this and use the same method as the rest of the installer. We should also use the installer's code to e.g. do templating and convert to ignition format and throw away the fleeting code.

      Attachments

        Issue Links

          is blocked by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. AGENT-131 create image installer asset

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. AGENT-203 Create clusterimageset asset

          • Undefined - Priority not specified.
          • Closed
          is related to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. AGENT-132 Copy code/data from fleeting into installer

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          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
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. AGENT-131 create image installer asset

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          links to

          GitHub openshift/installer#5944: AGENT-133: Export addStorageFiles and addSystemdUnits as functions

          GitHub openshift/installer#5945: AGENT-133: Move Ignition generation from fleeting code to asset

          GitHub openshift/installer#5977: AGENT-133: Remove double embedding of agent data

          Activity

            People

              rwsu1@redhat.com Richard Su
              zabitter Zane Bitter
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 6 minutes
                  6m