|author||Brad Bishop <email@example.com>||Sun Jun 09 16:55:57 2019 -0400|
|committer||Brad Bishop <firstname.lastname@example.org>||Thu Jun 13 10:38:54 2019 -0400|
meta-ibm: romulus: new YAML config recipe YAML configuration files exist scattered throughout the OpenBMC tree and how they are used is controlled with layers dependencies of virtuals and preferred providers. Most of the time the above scheme is very difficult to comprehend. This patch continues a re-thinking of that approach towards a more centralized scheme. Specifically this patch implements a single YAML config recipe for the Romulus systems. The logic contained in the recipe was pulled from all over the OpenBMC tree - the ability to comprehend how the different YAML files are generated and consumed should be greatly eased. One notable detail - unlike the upstream recipes, romulus-yaml-config is a target recipe and as such enables MACHINE based overrides. YAML files were copied from different locations in the tree, and run through a styling application (pyyaml dump(load(yaml))): romulus-ipmi-fru-properties-native:extra-properties.yaml -> romulus-yaml-config:romulus-ipmi-fru-properties.yaml romulus-ipmi-fru-read-inventory-native:config.yaml -> romulus-yaml-config:romulus-ipmi-fru.yaml romulus-ipmi-fru-read-bmc-inventory-native:bmc-fru-config.yaml -> romulus-yaml-config:romulus-ipmi-fru-properties.yaml romulus-ipmi-inventory-sel-native:sel-config.yaml -> romulus-yaml-config:romulus-ipmi-inventory-sensors.yaml romulus-ipmi-sensor-inventory-native:config.yaml -> romulus-yaml-config:romulus-ipmi-sensors.yaml (From meta-ibm rev: 67b17f7aa658b71908de47aa0b0814530da36259) Change-Id: I3953274db23f9ccf8cb74d3962e797bf935d61a8 Signed-off-by: Brad Bishop <email@example.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 firstname.lastname@example.org: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
As an example target Palmetto
. 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.
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.
Features In Progress
Features Requested but need help
Dive deeper into OpenBMC by opening the docs repository.