PR for design is not yet merged, so the exact implementation may change.

Description

Background

• Doc impact
• What are we introducing to the customer with this epic? The ability to attach a generic, non-bootable ISO image to configure a bare metal host after provisioning.
• What is the use case? As an operator, I want to configure a bare metal host after installing the operating system, before first boot. If I have a pool of powered off, installed hosts, I want to be able to add one of these hosts to my cluster by attaching a configuration ISO image and then powering on the host.
• Does this apply only to a Telco use case or does it apply to other OCP/ACM use cases as well? All OCP cases as well.
• What is the support level status of this Epic (DP, TP, full support) in this release? Full support
• If this is new content for existing documentation, what are the changes? Feature description and short procedure describing how to use the new, optional `spec.dataImage` stanza in the BareMetalHost CR.
• What is the target release? 4.16

People

• SME: Dimitry Tantsur
• QE:  Steeve Goveas

Resources and Links

• Enhancement details:
  • Add non-bootable iso attach API to BareMetalHost design proposal (unmerged PR)
  •  [RFE] Allow non-bootable iso connection/disconnection for provisioned nodes
•  Code PR TBD (METAL-683 not yet assigned)

Release Note

• Yes

Docs structure

New procedure module for postinstallation configuration assembly: Attaching a non-bootable ISO image to a node

Procedure is still TBD. A `spec.dataImage` stanza will be added to the `BareMetalHost` CR. See the design doc after the PR is merged. (PR link in "Resources and links" section above).