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

Change-Id: I2a6b68d25dd8177c3d9592699b980fe5da37256c
Signed-off-by: Ed Tanous <ed.tanous@intel.com>
1 file changed
tree: d11daacb22f9897d1be6a6ad3126c5d9b491d533
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-phosphor/
  10. recipes-support/
  11. recipes-textproc/
  12. COPYING.apache-2.0
  13. COPYING.MIT
  14. LICENSE
  15. MAINTAINERS
  16. README.md
  17. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.