commit | 4094c1b70ea460fa298b7bcff49ca63e0a645f72 | [log] [tgz] |
---|---|---|
author | Matt Spinler <spinler@us.ibm.com> | Fri May 03 13:46:28 2019 -0500 |
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Wed May 08 19:43:30 2019 -0400 |
tree | 8b699c041dd9fbadca2893d519b2940721cfdd51 | |
parent | 6c55f1f83476cd230abe07222462ed92364ec673 [diff] |
wspoon: Update inventory associations Make the follow updates to the associations that PIM will create: Make a new association iface on /system/chassis that contains every sensor in that chassis, with some exceptions. The forward association type is 'sensors', and the reverse type is 'chassis'. The power supply sensors are not included in this new association list, as the power supplies also now have a new 'sensors' <-> 'chassis' association that associates power supplies to their sensors, as bmcweb treats a power supply as a chassis. Also not included in the new chassis associations are any remaining power sensors, as bmcweb currently makes fake power supply responses out of them and we want to avoid that. The final change is to change the association type of the associations that point to the sensors on their inventory item from 'sensors' to 'child_sensors', as 'sensors' is required to be used in bmcweb's chassis handling as mentioned above. (From meta-ibm rev: 5a4a28582beb2f854d2724e192873536363943da) Change-Id: Iebd15c4b5a97a16bb614d757ce7621f087777622 Signed-off-by: Matt Spinler <spinler@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
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.
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
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 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
Machine | TEMPLATECONF |
---|---|
Palmetto | meta-ibm/meta-palmetto/conf |
Zaius | meta-ingrasys/meta-zaius/conf |
Witherspoon | meta-ibm/meta-witherspoon/conf |
Romulus | meta-ibm/meta-romulus/conf |
As an example target Palmetto
export TEMPLATECONF=meta-ibm/meta-palmetto/conf
. openbmc-env bitbake obmc-phosphor-image
Additional details can be found in the docs repository.
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.
Feature List
Features In Progress
Features Requested but need help
Dive deeper into OpenBMC by opening the docs repository.