Gitiles
Code Review Sign In
gerrit.openbmc.org / mdmillerii / openbmc / aad617f2cef143937204e78ee7b10da5d197420b
commitaad617f2cef143937204e78ee7b10da5d197420b[log] [tgz]
authorAndrew Geissler <geissonator@yahoo.com>Fri Jul 20 09:13:15 2018 -0700
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Fri Jul 20 20:01:35 2018 +0000
tree454ba97a01f3dcaae17c8907004181d83017650d
parent494894d69c88cf4909993227af2dd8f2ca938752 [diff]
Add explicit dependency between mapper and sdbus

Mapper has an implicit dependency on dbus.socket but
not on dbus.service. It appears an explicit dependency
is required to ensure the shutdown happens correctly.

Testing: Prior to this commit you would see this on a reboot:
Jul 20 15:01:34 witherspoon systemd[1]: Stopping D-Bus System MessageBus...
Jul 20 15:01:36 witherspoon systemd[1]: Stopped D-Bus System MessageBus.
Jul 20 15:01:37 witherspoon systemd[1]: xyz.openbmc_project.ObjectMapper.service: Main process exited,code=exited, status=1/FAILURE
Jul 20 15:01:37 witherspoon systemd[1]: xyz.openbmc_project.ObjectMapper.service: Failed with result'exit-code'.
Jul 20 15:01:41 witherspoon systemd[1]: Closed D-Bus System Message Bus Socket.

This shows the dbus.service stopping before the ObjectMapper

With this fix, this is now seen:
Jul 20 17:38:20 witherspoon systemd[1]: Stopping Phosphor DBus Service Discovery Manager...
Jul 20 17:38:21 witherspoon systemd[1]: Stopped Phosphor DBus Service Discovery Manager.
Jul 20 17:38:21 witherspoon systemd[1]: Stopping D-Bus System Message Bus...
Jul 20 17:38:21 witherspoon systemd[1]: Stopped D-Bus System Message Bus.
Jul 20 17:38:21 witherspoon systemd[1]: Closed D-Bus System Message Bus Socket.

This shows ObjectMapper stopping prior to dbus.service

Resolves openbmc/openbmc#3319

Change-Id: I466ec45f4582b3242688e8308d156961bb79cdc1
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
1 file changed
tree: 454ba97a01f3dcaae17c8907004181d83017650d
  1. import-layers/
  2. meta-openbmc-bsp/
  3. meta-openbmc-machines/
  4. meta-phosphor/
  5. bitbake ⇨ import-layers/yocto-poky/bitbake
  6. documentation ⇨ import-layers/yocto-poky/documentation
  7. LICENSE ⇨ import-layers/yocto-poky/LICENSE
  8. meta ⇨ import-layers/yocto-poky/meta
  9. meta-poky ⇨ import-layers/yocto-poky/meta-poky
  10. meta-selftest ⇨ import-layers/yocto-poky/meta-selftest
  11. meta-skeleton ⇨ import-layers/yocto-poky/meta-skeleton
  12. meta-yocto-bsp ⇨ import-layers/yocto-poky/meta-yocto-bsp
  13. oe-init-build-env ⇨ import-layers/yocto-poky/oe-init-build-env
  14. scripts ⇨ import-layers/yocto-poky/scripts
  15. .gitignore
  16. .gitreview
  17. .templateconf
  18. MAINTAINERS
  19. openbmc-env
  20. README.md
  21. 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 23
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake
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. OpenBMC has placed all known hardware targets in a standard directory structure meta-openbmc-machines/meta-[architecture]/meta-[company]/meta-[target]. You can see all of the known targets with find meta-openbmc-machines -type d -name conf. Choose the hardware target and then move to the next step. Additional examples can be found in the OpenBMC Cheatsheet

MachineTEMPLATECONF
Palmettometa-openbmc-machines/meta-openpower/meta-ibm/meta-palmetto/conf
Zaiusmeta-openbmc-machines/meta-openpower/meta-ingrasys/meta-zaius/conf
Witherspoonmeta-openbmc-machines/meta-openpower/meta-ibm/meta-witherspoon/conf

As an example target Palmetto

export TEMPLATECONF=meta-openbmc-machines/meta-openpower/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