commit	3f0c2a2e042f698b01c2f3c181650cac7e4c445c	[log] [tgz]
author	Joel Stanley <joel@jms.id.au>	Wed Aug 22 11:32:27 2018 +0930
committer	Brad Bishop <bradleyb@fuzziesquirrel.com>	Tue Aug 28 09:43:40 2018 +0000
tree	dc2f2fcb6921d48f330555a1d2939e955b241bd7
parent	8f731c09c9fd8028b56e25189e883c91a40a7a2e [diff]

meta-openbmc-machines: Remove Barreleye

Barreleye was the first machine to be designed and built for the IBM
OpenBMC project.

It no longer builds and no one has stepped forward to maintain it, so
this removes it from the tree.

Resolves: openbmc/openbmc#2777
Change-Id: I4b2fd53f1a72fe5a5b7ed700dd451b98cebfa445
Signed-off-by: Joel Stanley <joel@jms.id.au>

36 files changed

tree: dc2f2fcb6921d48f330555a1d2939e955b241bd7

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, 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 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. 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`

As an example target Palmetto

export TEMPLATECONF=meta-ibm/meta-palmetto/conf

4) 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 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.

Features of OpenBMC

Feature List

REST Management
IPMI
SSH based SOL
Power and Cooling Management
Event Logs
Zeroconf discoverable
Sensors
Inventory
LED Management
Host Watchdog
Simulation
Code Update Support for multiple BMC/BIOS images
POWER On Chip Controller (OCC) Support

Features In Progress

Full IPMI 2.0 Compliance with DCMI
Verified Boot
HTML5 Java Script Web User Interface
BMC RAS

Features Requested but need help

OpenCompute Redfish Compliance
OpenBMC performance monitoring
cgroup user management and policies
Remote KVM
Remote USB
OpenStack Ironic Integration
QEMU enhancements

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