History

Matt McEuen 910d296f6b Deduplicate airshipctl manifest networking

Deduplicate networking definitions inside of airshipctl functions,
and make the values driveable via a catalogue.

Changes:
* Removed BMO patches at site level; drive through catalogue instead.
* Added separate entrypoints for ephemeral & target site-level.
  catalogue/networking overrides. Ephemeral's kustomizes target's.
* Generalized the commonHostNetworking catalogue into a section in the
  overall networking catalogue.
* Cleaned up catalogue use in general.
* Got rid of some ill-formed Type-level phase definition.
  We should go back soon and define proper Type-level phases.

Change-Id: Iff96ccdcf7ebde4ae55e2b1a9d25dd1cdca0d2c8
Relates-To: https://github.com/airshipit/airshipctl/issues/315

2020-10-21 16:26:10 -05:00

replacements

Introduce Replacement Transformer plugin container

2020-10-16 16:00:56 +04:00

hardwareprofile.yaml

Deduplicate airshipctl manifest networking

2020-10-21 16:26:10 -05: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.