airship
/
airshipctl
Code Issues Proposed changes
airshipctl/manifests/function/hardwareprofile-example
History
Sean Eagan a65a7e155b Externalize KRM function versions 
Relates-To: #524
Signed-off-by: Sean Eagan <seaneagan1@gmail.com>
Change-Id: I7e811835ae1e5ab2cab65c398c53126f3a632405
 		2021-05-26 20:18:49 +00: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 Remove document plugin subcommand 2020-11-11 14:59:14 +04: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.