Gitiles
Code Review Sign In
gerrit.openbmc.org / stefanberger / openbmc / ee5dcddc3da722131aed493ebf20421eb498c042
commitee5dcddc3da722131aed493ebf20421eb498c042[log] [tgz]
authorAndrew Geissler <geissonator@yahoo.com>Mon Oct 19 13:35:38 2020 -0500
committerAndrew Geissler <geissonator@yahoo.com>Thu Oct 22 14:13:23 2020 -0500
tree10b46ad73911da591da493df9ba68a09e69ff6b5
parent657291878ae43f327a423ab2b3fb6235cd1f81d3 [diff]
autoreboot: define new one_time auto reboot prop

IBM has a use case where boots of a system can be done utilizing a debug
tool called istep. This tool does not utilize the normal systemd targets
to boot the system, but instead launches each individual step required
to boot the system. This allows fine grained control of the boot and the
ability to easily debug issues.

When booting a system using this tool, it is required that the automated
reboot policy be off. The issue is that istep can easily set AutoReboot
to false when it is used, but there is no way for it to know when to reset
it to true (i.e. when the user is done).

AutoReboot is a user setting and is something that must stay persistent
based on the users selection. It should not be moved back and forth by
software based on different debug modes.

The solution proposed here is to make a one-time AutoReboot property.
Boot debug tools like istep can utilize this temporary property and be
confident it will be reset whenever the user powers down their system or
stops their host.

Software will first look at this new one-time reboot property. If false
then auto reboots will be disabled. If the temporary reboot property is
true then software will look at the user-based AutoReboot property for
direction.

This new property will have no impact to existing software unless it
gets set and something looks at it. The thought is this could be useful
to more then IBM, so proposing it initially in meta-phosphor.

(From meta-phosphor rev: 7d29e7a2c135e91b222c57c66bb7ca61aae6398e)

Change-Id: I7c542469135061c5b5017b87cffc92aa6b8794c4
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
1 file changed
tree: 10b46ad73911da591da493df9ba68a09e69ff6b5
  1. .github/
  2. meta-amd/
  3. meta-arm/
  4. meta-aspeed/
  5. meta-bytedance/
  6. meta-evb/
  7. meta-facebook/
  8. meta-google/
  9. meta-hpe/
  10. meta-hxt/
  11. meta-ibm/
  12. meta-ingrasys/
  13. meta-inspur/
  14. meta-intel/
  15. meta-inventec/
  16. meta-lenovo/
  17. meta-mellanox/
  18. meta-microsoft/
  19. meta-nuvoton/
  20. meta-openembedded/
  21. meta-openpower/
  22. meta-phosphor/
  23. meta-portwell/
  24. meta-qualcomm/
  25. meta-quanta/
  26. meta-raspberrypi/
  27. meta-security/
  28. meta-x86/
  29. meta-xilinx/
  30. meta-yadro/
  31. poky/
  32. bitbake ⇨ poky/bitbake/
  33. LICENSE ⇨ poky/LICENSE
  34. meta ⇨ poky/meta
  35. meta-poky ⇨ poky/meta-poky/
  36. meta-skeleton ⇨ poky/meta-skeleton
  37. oe-init-build-env ⇨ poky/oe-init-build-env
  38. scripts ⇨ poky/scripts/
  39. .gitignore
  40. .gitreview
  41. .templateconf
  42. MAINTAINERS
  43. openbmc-env
  44. README.md
  45. 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 set up according to your hardware target. There is a special script in the root of this repository that can be used to configure the environment as needed. The script is called setup and takes the name of your hardware target as an argument.

The script needs to be sourced while in the top directory of the OpenBMC repository clone, and, if run without arguments, will display the list of supported hardware targets, see the following example:

$ . setup <machine> [build_dir]
Target machine must be specified. Use one of:

centriq2400-rep         nicole                     stardragon4800-rep2
f0b                     olympus                    swift
fp5280g2                olympus-nuvoton            tiogapass
gsj                     on5263m5                   vesnin
hr630                   palmetto                   witherspoon
hr855xg2                qemuarm                    witherspoon-128
lanyang                 quanta-q71l                witherspoon-tacoma
mihawk                  rainier                    yosemitev2
msn                     romulus                    zaius
neptune                 s2600wf

Once you know the target (e.g. romulus), source the setup script as follows:

. setup romulus build

For evb-ast2500, please use the below command to specify the machine config, because the machine in meta-aspeed layer is in a BSP layer and does not build the openbmc image.

TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2500/conf . openbmc-env

4) Build

bitbake obmc-phosphor-image

Additional details can be found in the docs repository.

OpenBMC Development

The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here

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.

Questions

First, please do a search on the internet. There's a good chance your question has already been asked.

For general questions, please use the openbmc tag on Stack Overflow. Please review the discussion on Stack Overflow licensing before posting any code.

For technical discussions, please see contact info below for IRC and mailing list information. Please don't file an issue to ask a question. You'll get faster results by using the mailing list or IRC.

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
  • User management
  • Virtual media

Features In Progress

  • OpenCompute Redfish Compliance
  • Verified Boot

Features Requested but need help

  • OpenBMC performance monitoring

Finding out more

Dive deeper into OpenBMC by opening the docs repository.

Technical Steering Committee

The Technical Steering Committee (TSC) guides the project. Members are:

  • Brad Bishop (chair), IBM
  • Nancy Yuen, Google
  • Sai Dasari, Facebook
  • James Mihm, Intel
  • Sagar Dharia, Microsoft
  • Supreeth Venkatesh, Arm

Contact