Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / c1662daa105d8c63671bb8d4ed8c610bb161fb41
commitc1662daa105d8c63671bb8d4ed8c610bb161fb41[log] [tgz]
authorAndrew Geissler <openbmcbump-github@yahoo.com>Fri Apr 05 15:12:25 2019 +0000
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Sun Apr 07 14:20:21 2019 -0400
treeb5dc53815f7add186c5429f868a681581a3e2cb5
parent9ac088835c722f34d59ae067d65c17e6c40fbd6f [diff]
phosphor-objmgr: srcrev bump 12025cdc6a..7f83837608

Andrew Geissler (20):
      unit-test: Introduce unit tests to phosphor-objmgr
      unit-test: Test need_to_introspect function
      unit-test: Add all required parameters to removeAssociation
      unit-test: Create initial associations file
      unit-test: Test removeAssociations interface
      unit-test: Move asio server to its own class
      unit-test: Move association create funcs to util
      unit-test: Request distinct name per test app
      unit-test: Test deleting entry on name change
      unit-test: Move removeAssociationEndpoints()
      unit-test: Utilize common code for endpoint remove
      unit-test: Move checkAssociationEndpointRemoves
      unit-test: Test checkAssociationEndpointRemoves()
      unit-test: Move associationChanged()
      unit-test: Add some doc on Association
      unit-test: Debug functions to dump data structures
      unit-test: Test associationChanged()
      unit-test: Fix bug when endpoint empty
      unit-test: Move processing of interfaces added
      unit-test: Test interfaces added function

(From meta-phosphor rev: 70bec1f018b3797d613653d35700bb0268bbdc72)

Change-Id: Iaa4d1d16f46484392049fc31d8d1904bcec7d309
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
1 file changed
tree: b5dc53815f7add186c5429f868a681581a3e2cb5
  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-mellanox/
  14. meta-nuvoton/
  15. meta-openembedded/
  16. meta-openpower/
  17. meta-phosphor/
  18. meta-portwell/
  19. meta-qualcomm/
  20. meta-quanta/
  21. meta-raspberrypi/
  22. meta-security/
  23. meta-x86/
  24. meta-xilinx/
  25. poky/
  26. bitbake ⇨ poky/bitbake/
  27. LICENSE ⇨ poky/LICENSE
  28. meta ⇨ poky/meta
  29. meta-poky ⇨ poky/meta-poky/
  30. meta-skeleton ⇨ poky/meta-skeleton
  31. oe-init-build-env ⇨ poky/oe-init-build-env
  32. scripts ⇨ poky/scripts/
  33. .gitignore
  34. .gitreview
  35. .templateconf
  36. MAINTAINERS
  37. openbmc-env
  38. README.md
  39. 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

  • 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