Gitiles
Code Review Sign In
gerrit.openbmc.org / stefanberger / openbmc / 1baa4da706692781e9bef68fbbe72b576ba1c7e8
commit1baa4da706692781e9bef68fbbe72b576ba1c7e8[log] [tgz]
authorRatan Gupta <ratagupt@in.ibm.com>Tue Apr 24 18:10:36 2018 +0530
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Wed Aug 08 13:51:52 2018 +0000
treed9ebff506ca927ff1678e0af070ebb3aee25b768
parent58fe5aab88b16f42f05efe81b1718a5da5749cca [diff]
Add recipe for phosphor-snmp

Phosphor-snmp provides the D-Bus service named network-snmp-conf
which is used to configure the snmp manager details.

Phosphor-snmp also provides the lib which is used by the client
to send the snmp trap.

Phosphor-snmp uses the net-snmp libs to send the trap.

net-snmp provides the following packages
net-snmp-libs,net-snmp-server, net-snmp-client,
net-snmp-server-snmpd-netsnmp-server-snmptrapd.

To send a trap we are interested only in the net-snmp-libs.
By default the net-snmp-libs is having the code enabled for server
sepcific functions which makes the libs heavy.

This commit adds the recipe for phosphor-snmp and the service file
for D-Bus service(network-snmp-conf) and disables those features
from net-snmp which are specfic for MIB parsing,snmpd and snmptrapd.

However this features may be required if we start using
the snmp agent functionality.

Change-Id: I6ff36fcd378db2f506b0621569693d66d7de79e9
Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
3 files changed
tree: d9ebff506ca927ff1678e0af070ebb3aee25b768
  1. import-layers/
  2. meta-openbmc-bsp/
  3. meta-openbmc-machines/
  4. meta-phosphor/
  5. bitbake ⇨ import-layers/yocto-poky/bitbake
  6. documentation ⇨ import-layers/yocto-poky/documentation
  7. LICENSE ⇨ import-layers/yocto-poky/LICENSE
  8. meta ⇨ import-layers/yocto-poky/meta
  9. meta-poky ⇨ import-layers/yocto-poky/meta-poky
  10. meta-selftest ⇨ import-layers/yocto-poky/meta-selftest
  11. meta-skeleton ⇨ import-layers/yocto-poky/meta-skeleton
  12. meta-yocto-bsp ⇨ import-layers/yocto-poky/meta-yocto-bsp
  13. oe-init-build-env ⇨ import-layers/yocto-poky/oe-init-build-env
  14. scripts ⇨ import-layers/yocto-poky/scripts
  15. .gitignore
  16. .gitreview
  17. .templateconf
  18. MAINTAINERS
  19. openbmc-env
  20. README.md
  21. 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. OpenBMC has placed all known hardware targets in a standard directory structure meta-openbmc-machines/meta-[architecture]/meta-[company]/meta-[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

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

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