commit | e1900161124ebd6c7ff8d21ab977e5d506afb846 | [log] [tgz] |
---|---|---|
author | Andrew Geissler <openbmcbump-github@yahoo.com> | Fri Mar 25 16:10:13 2022 +0000 |
committer | Andrew Geissler <andrew@geissonator.com> | Fri Apr 08 18:39:14 2022 +0000 |
tree | d4405c271c841edb1d93a515fc17b5cc85e6cdb0 | |
parent | de0582f0e7de86eaf8c8d90d86ed313273a73774 [diff] |
phosphor-state-manager: bump and multi host/chassis support phosphor-state-manager: srcrev bump 1ab2b6cea6..211d972d75 Adriana Kobylak (1): chassis: Monitor the PowerSystemInputs for power status Allen.Wang (2): host-state-manager: Add multi-host support chassis-state-manager: Correct poweroff state Unit Andrew Geissler (2): ensure bmc-state-manager stays in quiesce state generate bmc dump on monitored systemd target fail Brandon Wyman (1): Correct pinhole reset logic for chassis state Mike Capps (1): Set Critical severity for Blackout errors Patrick Williams (7): filesystem: use non-experimental version meson: remove stdc++fs dependency meson: add subproject wraps for current dependencies sdbusplus: object: don't use 'bool' argument constructor meson: add missing dependencies and wraps crit-service: update defaults for templated Host/Chassis sched-host-tran: support multi-host Potin Lai (3): chassis-state-manager: Add multi-chassis support discover-system-state: add multi-host support host-state-manager: fix host0 failure with reading wrong object path shamim ali (1): power-on-hours: ensure not incremented when system off Some commits went into phosphor-state-manager support that starts the framework to support multiple chassis and hosts within a system. This commit templates both the host and chassis services. Change-Id: I19764aa0c625d4d28d8d0e672658f1a3910335af Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com> Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
OpenBMC is a Linux distribution for management controllers used in devices such as servers, top of rack switches or RAID appliances. It uses Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your platform.
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat \ zstd pigz
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"
git clone git@github.com:openbmc/openbmc.git cd openbmc
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: bletchley gsj romulus dl360poc kudo s2600wf e3c246d4i mihawk swift ethanolx mtjade tiogapass evb-ast2500 nicole transformers evb-ast2600 olympus-nuvoton witherspoon evb-npcm750 on5263m5 witherspoon-tacoma f0b p10bmc x11spi fp5280g2 palmetto yosemitev2 g220a qemuarm zaius gbs quanta-q71l
Once you know the target (e.g. romulus), source the setup
script as follows:
. setup romulus
bitbake obmc-phosphor-image
Additional details can be found in the docs repository.
The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here
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.
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.
Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.
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 Discord 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 Discord.
Feature List
Features In Progress
Features Requested but need help
Dive deeper into OpenBMC by opening the docs repository.
The Technical Steering Committee (TSC) guides the project. Members are: