Gitiles
Code Review Sign In
gerrit.openbmc.org / stefanberger / openbmc / bae19af1075e34780c97bb352fc3fb318234902b
commitbae19af1075e34780c97bb352fc3fb318234902b[log] [tgz]
authorAndrew Geissler <openbmcbump-github@yahoo.com>Mon Jul 08 19:51:12 2019 +0000
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Mon Jul 08 22:23:52 2019 -0400
treeecea45e602609e92d7556206ce4d36ce290900c1
parent3f966dc22a5620c76e73b2a4ad601ccb1f0caaea [diff]
meta-phosphor: ipmi-flash: add systemd targets

phosphor-ipmi-flash installs three targets by default, this adds those
installations.  Each system that leverages phosphor-ipmi-flash will want
to define their services to be installed by these three targets.

The phosphor-ipmi-flash-bmc-prepare.target should have a service that
clears caches or any other steps to prepare to receive an update image.

The phosphor-ipmi-flash-bmc-verify.target should have a service that
verifies the image's contents against a hash value provided.

If a platform is using reboot-update, they don't need to provide an
additional service for phosphor-ipmi-flash-bmc-update.target.
Otherwise, this target should have service(s) that handle updating the
BMC's firmware.  This can mean, unpacking and installing the UBI
tarball, or anything required.

If the host is using phosphor-ipmi-flash to update the host bios, then
via the host-bios package configuration option, you are provided an
additional three targets:
 * phosphor-ipmi-flash-bios-prepare.target
 * phosphor-ipmi-flash-bios-verify.target
 * phosphor-ipmi-flash-bios-update.target

These three targets are effectively the same uses as the BMC targets,
but are triggered if one is sending data to the /flash/bios blob.

phosphor-ipmi-flash: srcrev bump 33311b47b3..c9792e7536

Patrick Venture (9):
      build: prevent enabling aspeed and nuvoton
      build: drop --enable-pci-bridge option
      build: drop --enable-lpc-bridge option
      build: prevent enabling both static and ubi tarball
      build: install three targets to handle bmc updates
      bmc: only add verifyBlobId if data sent for image
      bmc: add ActionPack notion to bundle actions
      build: add option --enable-host-bios
      tools: add bios support

(From meta-phosphor rev: a560e8e1f911f445500b42a5f3fd1c17adb37451)

Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: Idb35a05279468745260085182a466776d9fe7d61
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
1 file changed
tree: ecea45e602609e92d7556206ce4d36ce290900c1
  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-microsoft/
  16. meta-nuvoton/
  17. meta-openembedded/
  18. meta-openpower/
  19. meta-phosphor/
  20. meta-portwell/
  21. meta-qualcomm/
  22. meta-quanta/
  23. meta-raspberrypi/
  24. meta-security/
  25. meta-x86/
  26. meta-xilinx/
  27. meta-yadro/
  28. poky/
  29. bitbake ⇨ poky/bitbake/
  30. LICENSE ⇨ poky/LICENSE
  31. meta ⇨ poky/meta
  32. meta-poky ⇨ poky/meta-poky/
  33. meta-skeleton ⇨ poky/meta-skeleton
  34. oe-init-build-env ⇨ poky/oe-init-build-env
  35. scripts ⇨ poky/scripts/
  36. .gitignore
  37. .gitreview
  38. .templateconf
  39. MAINTAINERS
  40. openbmc-env
  41. README.md
  42. 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