airship
/
airshipctl
Code Issues Proposed changes
airshipctl/manifests/function/hardwareprofile-example
History
SirishaGopigiri ad555d4d24 Integrate capi v0.4.2 and capm3 v0.5.0 
The below manifest changes integrates capi v0.4.2 with capm3
v0.5.0 version. It changes the required manifests files
in the airshipctl. It upgrades capi to v1alpha4 and capm3 to
v1alpha5.

Closes: #518 #560
Change-Id: Ia9ea82ad8052e55f0e70f1038497a919ac7b9270
 		2021-10-13 13:30:52 -05:00
..
replacements Externalize KRM function versions 2021-05-26 20:18:49 +00:00
README.md Add RAID to example hardwareprofile 2020-10-01 05:17:15 +00:00
hardwareprofile.yaml Integrate capi v0.4.2 and capm3 v0.5.0 2021-10-13 13:30:52 -05:00
kustomization.yaml Add hardware profile / firmware plumbing 2020-08-06 09:14:12 -05:00

README.md

Function: hardwareprofile-example

This function defines a hardware profile that can be consumed by the hostgenerator-m3 function. It serves as an example for how other hardware profile functions can be created and consumed.

The example profile currently has fields for RAID and firmware configurations. This is to provide as a reference for utilizing all the supported RAID levels as well as all the supported firmware configurations.

For firmware configurations, the values from example profile are carried over to the default profile of hostgenerator-m3. That is because same defaults are exercised in metal3 baremetal-operator as well. See bios-config spec However, for RAID configurations, since there is no default profile, the template does not have any RAID fields. Nevertheless, all the supported RAID configurations have been listed in the hardwareprofile.yaml for your reference.

The /replacements kustomization contains a substitution rule that injects the profile into the hostgenerator BMH template. Please see the manifests/type/gating type and manifests/site/test-site site kustomization.yamls to see how a hardwareprofile function can be wired in.