| commit | 238f3a78a059b7307525cbd60e1bc764ef2bb429 | [log] [tgz] |
|---|---|---|
| author | Andrew Geissler <andrewg@us.ibm.com> | Thu Mar 23 12:48:06 2017 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Apr 07 17:46:10 2017 +0000 |
| tree | fdbbef1ff3eb23b2c79024a586df836d09948df7 | |
| parent | 08d3acf7f04a9b51adc58f636170a8fbbf6a3383 [diff] |
Add in new targets to handle bmc resets while host running The point of this new target is to support getting the systemd targets which boot the host into the running state (without actually running the associated services) when the BMC is rebooted and the host is up and running. This will ensure that systemd and its targets match with the state of the system without affecting the running host. This commit will run the new target but nothing will happen yet due to the discovery service being a noop. Once the application is in for the service to call, it will be added to the service which will enable this new host running with bmc reset support. Change-Id: Ia29e53de58ea7530941341b0e515e4d8fa49be6c Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
- meta-phosphor/common/recipes-core/systemd/obmc-targets.bb[diff]
- meta-phosphor/common/recipes-core/systemd/obmc-targets/obmc-host-reset-running@.target[Added - diff]
- meta-phosphor/common/recipes-core/systemd/obmc-targets/obmc-host-reset@.target[Added - diff]
- meta-phosphor/common/recipes-phosphor/host/obmc-op-control-host.bb[diff]
- meta-phosphor/common/recipes-phosphor/host/obmc-op-control-host/op-reset-host-check@.service[Added - diff]
- meta-phosphor/common/recipes-phosphor/host/obmc-op-control-host/op-reset-host-running@.service[Added - diff]
- import-layers/
- meta-openbmc-bsp/
- meta-openbmc-machines/
- meta-phosphor/
- bitbake ⇨ import-layers/yocto-poky/bitbake
- documentation ⇨ import-layers/yocto-poky/documentation
- LICENSE ⇨ import-layers/yocto-poky/LICENSE
- meta ⇨ import-layers/yocto-poky/meta
- meta-poky ⇨ import-layers/yocto-poky/meta-poky
- meta-selftest ⇨ import-layers/yocto-poky/meta-selftest
- meta-skeleton ⇨ import-layers/yocto-poky/meta-skeleton
- meta-yocto-bsp ⇨ import-layers/yocto-poky/meta-yocto-bsp
- oe-init-build-env ⇨ import-layers/yocto-poky/oe-init-build-env
- oe-init-build-env-memres ⇨ import-layers/yocto-poky/oe-init-build-env-memres
- scripts ⇨ import-layers/yocto-poky/scripts
- .gitignore
- .gitreview
- .templateconf
- openbmc-env
- README.md
OpenBMC
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, Open-Embedded, Systemd and DBus 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 23
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake 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. OpenBMC has placed all known hardware targets in a standard directory structure meta-openbmc-machines/meta-openpower/[company]/[target]. You can see all of the known targets with find meta-openbmc-machines -type d -name conf. Choose the hardware target and then move to the next step. Additional examples can be found in the OpenBMC Cheatsheet
| Machine | TEMPLATECONF |
|---|---|
| Palmetto | meta-openbmc-machines/meta-openpower/meta-ibm/meta-palmetto/conf |
| Barreleye | meta-openbmc-machines/meta-openpower/meta-rackspace/meta-barreleye/conf |
| Zaius | meta-openbmc-machines/meta-openpower/meta-ingrasys/meta-zaius/conf |
| Witherspoon | meta-openbmc-machines/meta-openpower/meta-ibm/meta-witherspoon/conf |
As an example target Palmetto
export TEMPLATECONF=meta-openbmc-machines/meta-openpower/meta-ibm/meta-palmetto/conf
3) 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 a 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.
Finding out more
Dive deeper in to OpenBMC by opening the docs repository
Contact
- Mail: openbmc@lists.ozlabs.org https://lists.ozlabs.org/listinfo/openbmc
- IRC: #openbmc on freenode.net
- Riot: #openbmc:matrix.org