Files

Mahnoor Asghar 73b3d4e83f Add physicalDisks and controller fields to RAID

This adds physicalDisks and controller fields to the the hardware profile guide,
and to the example hardwareprofile.

Relates-To: #499
Closes: #499
Change-Id: I6c3107b846d1a9c94abffe378a9a07a2f089ef99

2021-11-30 07:35:43 +00:00

replacements

Externalize KRM function versions

2021-05-26 20:18:49 +00:00

hardwareprofile.yaml

Add physicalDisks and controller fields to RAID

2021-11-30 07:35:43 +00:00

kustomization.yaml

Add hardware profile / firmware plumbing

2020-08-06 09:14:12 -05:00

README.md

Add RAID to example hardwareprofile

2020-10-01 05:17:15 +00: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.