tree 09ac3ba7d78905c3c63489ec44fd1ba424276e94
parent 6e56e3bd2a4acc56eb79a4276e5b637f247d91fb
author Brad Bishop <bradleyb@fuzziesquirrel.com> 1560109794 -0400
committer Brad Bishop <bradleyb@fuzziesquirrel.com> 1560436741 -0400

meta-openpower: new YAML configuration recipe

YAML configuration files exist scattered throughout the OpenBMC tree and
how they are used is controlled with layers dependencies of virtuals and
preferred providers.

Most of the time the above scheme is very difficult to comprehend.  This
patch begins a re-thinking of that approach towards a more centralized
scheme.

Specifically, a number of YAML files that can be shared across OpenPOWER
systems (in theory...in practice they are only used in the
ACx22/Witherspoon layer) are copied (and run through pyyaml
yaml.dump(yaml.load(fd)) for style purposes) to a single recipe:

  hostboot-inventory-config-native:config.yaml ->
    openpower-yaml-config:ipmi-hostboot-fru-mrw.yaml

  openpower-ipmi-oem-sensor-inventory-mrw:openpower-config.yaml ->
    openpower-yaml-config:ipmi-occ-active-sensor-mrw.yaml
    openpower-yaml-config:ipmi-hostboot-volatile-sensor-mrw.yaml

  phosphor-ipmi-fru-properties-mrw-native:config.yaml ->
    openpower-yaml-config:ipmi-fru-properties-mrw.yaml

Notably these YAML files are installed to the target sysroot rather than
the native sysroot, which enables MACHINE derived overrides.

This new recipe enables the deprecation of:
  hostboot-inventory-config-native
  openpower-ipmi-oem-sensor-inventory-mrw-native
  phosphor-ipmi-fru-properties-mrw-native

and all the virtuals and PREFERRED_PROVIDERS associated with those
recipes, once any layers using these YAML configuration files are
updated to obtain them via openpower-yaml-config.  That will greatly
reduce comprehensional complexity.

(From meta-openpower rev: 31f20185c231ccab0d9faaa80b2281195066b1e5)

Change-Id: I1fd0c64c03c77006a7858a4ed773b84e6b34c312
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>