airship/airshipctl
Code Issues Proposed changes
ce5ca13b61
airshipctl/manifests/function/hardwareprofile-example
History
Alexey Odinokov 70976860a9 Adding a place for external secrets to be stored on site level 
There will be another place to store that data: [1]
All previous appropriate phases will work for that,
e.g. secret-reencrypt all secret-show.
The documentation is updated accordinly.

[1]
manifests/site/test-site/target/encrypted/results/imported/secrets.yaml

Change-Id: Iaeeaae902420ef9158dcaba2a272e20459596ae5
2021-05-07 18:25:13 +00:00
..
replacements Pin krm function calls 2021-03-24 09:28:54 -05: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 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.