Gitiles
Code Review Sign In
gerrit.openbmc.org / mdmillerii / openbmc / b36f3148561a6abf306deb69e1d5a59f900a344f
commitb36f3148561a6abf306deb69e1d5a59f900a344f[log] [tgz]
authorManojkiran Eda <manojkiran.eda@gmail.com>Sat May 26 10:37:52 2018 +0530
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Wed Sep 12 14:56:47 2018 -0400
tree9755b32ad378279e4843f4268d3254f679b4e772
parent2a6fedf819da8331ed62391bdfa0acdb10202847 [diff]
Remove hidden-files in coredump(dir) during boot

It is observed that systemd-coredump has the capability to remove
the older dumps which are having the naming style mentioned in
/proc/sys/kernel/core_pattern, But will not remove any other files
present in the coredump directory.

It can happen that, while processing a dump the BMC Crashes and there
by leaving the partial dumps in the coredump directory and these will
be hidden and will not be removed by systemd-coredump service.These
files can get piled up and the BMC can run into OOM condition.So idea
of this commit is to make sure that , we remove all the temporary
hidden files in the coredump directory during the next BMC boot.

- Made a rule and placed it in /usr/lib/tmpfiles.d/*.conf which will
  be used by systemd-tmpfiles to remove the hidden files in coredump
  directory during boot.

Partially Resolves openbmc/openbmc#2826

(From meta-phosphor rev: 9fe03c666476de51ab75904f008f45f8485ac9b2)

Change-Id: Iff96b3880ebdeccb842e6aa7ff9807fcd451fb5a
Signed-off-by: manojeda <manojeda@in.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2 files changed
tree: 9755b32ad378279e4843f4268d3254f679b4e772
  1. meta-arm/
  2. meta-aspeed/
  3. meta-evb/
  4. meta-ibm/
  5. meta-ingrasys/
  6. meta-intel/
  7. meta-inventec/
  8. meta-mellanox/
  9. meta-nuvoton/
  10. meta-openembedded/
  11. meta-openpower/
  12. meta-phosphor/
  13. meta-portwell/
  14. meta-qualcomm/
  15. meta-quanta/
  16. meta-raspberrypi/
  17. meta-security/
  18. meta-x86/
  19. poky/
  20. bitbake ⇨ poky/bitbake/
  21. LICENSE ⇨ poky/LICENSE
  22. meta ⇨ poky/meta
  23. meta-poky ⇨ poky/meta-poky/
  24. oe-init-build-env ⇨ poky/oe-init-build-env
  25. scripts ⇨ poky/scripts/
  26. .gitignore
  27. .gitreview
  28. .templateconf
  29. MAINTAINERS
  30. openbmc-env
  31. README.md
  32. setup
README.md

OpenBMC

Build Status

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

MachineTEMPLATECONF
Palmettometa-ibm/meta-palmetto/conf
Zaiusmeta-ingrasys/meta-zaius/conf
Witherspoonmeta-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