Gitiles
Code Review Sign In
gerrit.openbmc.org / stefanberger / openbmc / 38384acde147c69982cfbf11550b17d0decb7150
commit38384acde147c69982cfbf11550b17d0decb7150[log] [tgz]
authorBrad Bishop <bradleyb@fuzziesquirrel.com>Sun Jun 09 15:49:54 2019 -0400
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Thu Jun 13 10:39:01 2019 -0400
tree09ac3ba7d78905c3c63489ec44fd1ba424276e94
parent6e56e3bd2a4acc56eb79a4276e5b637f247d91fb [diff]
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>
5 files changed
tree: 09ac3ba7d78905c3c63489ec44fd1ba424276e94
  1. .github/
  2. meta-arm/
  3. meta-aspeed/
  4. meta-evb/
  5. meta-facebook/
  6. meta-google/
  7. meta-hxt/
  8. meta-ibm/
  9. meta-ingrasys/
  10. meta-inspur/
  11. meta-intel/
  12. meta-inventec/
  13. meta-lenovo/
  14. meta-mellanox/
  15. meta-nuvoton/
  16. meta-openembedded/
  17. meta-openpower/
  18. meta-phosphor/
  19. meta-portwell/
  20. meta-qualcomm/
  21. meta-quanta/
  22. meta-raspberrypi/
  23. meta-security/
  24. meta-x86/
  25. meta-xilinx/
  26. poky/
  27. bitbake ⇨ poky/bitbake/
  28. LICENSE ⇨ poky/LICENSE
  29. meta ⇨ poky/meta
  30. meta-poky ⇨ poky/meta-poky/
  31. meta-skeleton ⇨ poky/meta-skeleton
  32. oe-init-build-env ⇨ poky/oe-init-build-env
  33. scripts ⇨ poky/scripts/
  34. .gitignore
  35. .gitreview
  36. .templateconf
  37. MAINTAINERS
  38. openbmc-env
  39. README.md
  40. setup
README.md

OpenBMC

Build Status

The OpenBMC project can be described as a Linux distribution for embedded devices that have a BMC; typically, but not limited to, things like servers, top of rack switches or RAID appliances. The OpenBMC stack uses technologies such as Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your server platform.

Setting up your OpenBMC project

1) Prerequisite

  • Ubuntu 14.04
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
  • Fedora 28
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake \
    rpcgen perl-Thread-Queue perl-bignum perl-Crypt-OpenSSL-Bignum
sudo dnf groupinstall "C Development Tools and Libraries"

2) Download the source

git clone git@github.com:openbmc/openbmc.git
cd openbmc

3) Target your hardware

Any build requires an environment variable known as TEMPLATECONF to be set to a hardware target. You can see all of the known targets with find meta-* -name local.conf.sample. Choose the hardware target and then move to the next step. Additional examples can be found in the OpenBMC Cheatsheet

MachineTEMPLATECONF
Palmettometa-ibm/meta-palmetto/conf
Zaiusmeta-ingrasys/meta-zaius/conf
Witherspoonmeta-ibm/meta-witherspoon/conf
Romulusmeta-ibm/meta-romulus/conf

As an example target Palmetto

export TEMPLATECONF=meta-ibm/meta-palmetto/conf

4) Build

. openbmc-env
bitbake obmc-phosphor-image

Additional details can be found in the docs repository.

Build Validation and Testing

Commits submitted by members of the OpenBMC GitHub community are compiled and tested via our Jenkins server. Commits are run through two levels of testing. At the repository level the makefile make check directive is run. At the system level, the commit is built into a firmware image and run with an arm-softmmu QEMU model against a barrage of CI tests.

Commits submitted by non-members do not automatically proceed through CI testing. After visual inspection of the commit, a CI run can be manually performed by the reviewer.

Automated testing against the QEMU model along with supported systems are performed. The OpenBMC project uses the Robot Framework for all automation. Our complete test repository can be found here.

Submitting Patches

Support of additional hardware and software packages is always welcome. Please follow the contributing guidelines when making a submission. It is expected that contributions contain test cases.

Bug Reporting

Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.

Features of OpenBMC

Feature List

  • Host management: Power, Cooling, LEDs, Inventory, Events, Watchdog
  • Full IPMI 2.0 Compliance with DCMI
  • Code Update Support for multiple BMC/BIOS images
  • Web-based user interface
  • REST interfaces
  • D-Bus based interfaces
  • SSH based SOL
  • Remote KVM
  • Hardware Simulation
  • Automated Testing

Features In Progress

  • OpenCompute Redfish Compliance
  • User management
  • Virtual media
  • Verified Boot

Features Requested but need help

  • OpenBMC performance monitoring

Finding out more

Dive deeper into OpenBMC by opening the docs repository.

Contact