Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / bba6b5a88485e9101b83bf46b846509751d439be
commitbba6b5a88485e9101b83bf46b846509751d439be[log] [tgz]
authorEd Tanous <ed.tanous@intel.com>Mon Oct 15 09:13:46 2018 -0700
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Wed Nov 07 09:56:59 2018 -0500
tree5a591f3e623f2c656e7b45d456abbe5dda9e903c
parent02e13d40b310fb89717313c23e2fa74f03a5d2cf [diff]
meta-phosphor: Move to dbus-broker

Dbus-broker is an alternative implementation of the dbus-daemon that is
oriented around reducing abnormal conditions, and increasing the
performance of the dbus daemon process.

In practice, this seems to make a world of difference in performance.  A
testing of a smattering of user facing interfaces shows improvements
across the board:
1. 7 second improvement in boot time to BMC Ready change.
2. Dbus based ipmi sensor reading implementation gains a 120% speedup
(20 seconds down to 8)
3. Redfish thermal schema goes from 550ms time to first byte, to 400ms
time to first byte.

Negatives as they apply to OpenBMC
1. Debug: dbus-broker loses the ability to directly implement DBus over
TCP.  To my knowlege very few people use this for anything other than
debug, and even for debug, its usefulness is limited.  It's very likely
that an implementation of socat could bridge this gap.
2. Support.  Very few other linux implementations have moved to dbus
broker, so there is the possibility that we will find a critical flaw or
bug that others haven't hit get.  This seems relatively unlikely, given
the widespread usage of this project already.

Tested By: Booting system, and testing a variety of user facing
interfaces.  No issues found.

Requires Williams patch cherry picked ontop of oe-core:
http://cgit.openembedded.org/meta-openembedded/commit/meta-oe/recipes-core/dbus/dbus-broker_git.bb?id=e4baf298cd658b37fd90134dc54a92c75fd117d9

(From meta-phosphor rev: 72615f5614abba33a14d68afdb9010c93f3a1ea3)

Change-Id: Iabac84c93253aa96c7735db4f1e0755d37e6c3db
Signed-off-by: Ed Tanous <ed.tanous@intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
1 file changed
tree: 5a591f3e623f2c656e7b45d456abbe5dda9e903c
  1. meta-arm/
  2. meta-aspeed/
  3. meta-evb/
  4. meta-facebook/
  5. meta-google/
  6. meta-hxt/
  7. meta-ibm/
  8. meta-ingrasys/
  9. meta-intel/
  10. meta-inventec/
  11. meta-mellanox/
  12. meta-nuvoton/
  13. meta-openembedded/
  14. meta-openpower/
  15. meta-phosphor/
  16. meta-portwell/
  17. meta-qualcomm/
  18. meta-quanta/
  19. meta-raspberrypi/
  20. meta-security/
  21. meta-x86/
  22. meta-xilinx/
  23. poky/
  24. bitbake ⇨ poky/bitbake/
  25. LICENSE ⇨ poky/LICENSE
  26. meta ⇨ poky/meta
  27. meta-poky ⇨ poky/meta-poky/
  28. meta-skeleton ⇨ poky/meta-skeleton
  29. oe-init-build-env ⇨ poky/oe-init-build-env
  30. scripts ⇨ poky/scripts/
  31. .gitignore
  32. .gitreview
  33. .templateconf
  34. MAINTAINERS
  35. openbmc-env
  36. README.md
  37. 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
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

  • REST Management
  • IPMI
  • SSH based SOL
  • Power and Cooling Management
  • Event Logs
  • Zeroconf discoverable
  • Sensors
  • Inventory
  • LED Management
  • Host Watchdog
  • Simulation
  • Code Update Support for multiple BMC/BIOS images
  • POWER On Chip Controller (OCC) Support

Features In Progress

  • Full IPMI 2.0 Compliance with DCMI
  • Verified Boot
  • HTML5 Java Script Web User Interface
  • BMC RAS

Features Requested but need help

  • OpenCompute Redfish Compliance
  • OpenBMC performance monitoring
  • cgroup user management and policies
  • Remote KVM
  • Remote USB
  • OpenStack Ironic Integration
  • QEMU enhancements

Finding out more

Dive deeper in to OpenBMC by opening the docs repository.

Contact