obmc-yadro-cli: srcrev bump 29768c2fb7..76743c3706

Alexander Amelkin (27):
      install: Beautify the output
      Move group-to-role conversion functions to clicmd
      clicmd: Hide restricted functions by role
      install: Prohibit sudo by default, no lecture
      Update command permissions
      user: Add `set mypassword`, fix `user create`
      Add copyright banners
      bmc info version: Refactor
      bmc: Fix help for ifconfig and datetime ntpconfig
      help: Restrict top-level commands
      Update permissions per design document
      vegman: power: Add `reboot`, fix `off`
      health logs show: Add help
      bmc: Refix f2ff3222ada5f627a322e920e616c978
      bmc datetime show: Fix help message
      bmc syslog reset: Fix typo in help message
      Fix error handling in local variable assignments
      Fix assignments from external commands
      Add a basic github workflow for shellcheck
      bmc datetime set: Fix format checking
      Fix issues found by shellcheck
      clicmd: Add a generic exec_tool function
      bmc datetime set: Add range sanity checks
      bmc ifconfig help: Fix command name display
      clicmd: Fix autocomplete for path arguments
      host: virtualmedia mount: Fix help formatting
      bmc: config syslog: Specify TCP proto in help

Alexander Filippov (16):
      bmc/datetime/ntpconfig: add interface support
      bmc/syslog: add implementation
      user: multiple deletion support
      health: logs: Use dreport instead of journalctl
      health: logs: export: remove obsolete bundles
      health: logs: fix error on show hostlogger
      Fix misspelling
      Fix 2-level subcommands execution
      vegman: bmc datetime set: fix execution
      vegman: bmc power: use hostpwrctl
      Improve health logs clear command
      vegman: led: fix ID LED state determination
      vegman: datetime: Remove manual settings time
      vegman: datetime: Masquerade manual sync method
      health: log: journalcopy dreport plugin support
      health: logs: clean: fix cleaning order

Andrei Kartashev (1):
      show error when no groups match regexp

Igor Kononenko (6):
      vegman: Support virtual media and NBD client
      remotemedia: Add the NBD export name flag
      bmc: remoteimage: Remove CLI command
      host: Update the 'virtualmedia' command
      host: virtualmedia: Support the HTTP protocol
      bmc info version: Only show active versions

Ivan Mikhaylov (1):
      vegman: add audit logs for user actions

v.mitrofanov (3):
      host: Add 'config default' command
      Refactor help formatting
      host: Add 'nmi' command

Change-Id: Ic2dee1c43c1662c2355ad3bdd9b96451f3a9f212
Signed-off-by: Alexander Filippov <a.filippov@yadro.com>
1 file changed
tree: a43610e411ab34081f8c93dc946adcfc95192e37
  1. .github/
  2. meta-alibaba/
  3. meta-amd/
  4. meta-ampere/
  5. meta-arm/
  6. meta-aspeed/
  7. meta-asrock/
  8. meta-bytedance/
  9. meta-evb/
  10. meta-facebook/
  11. meta-fii/
  12. meta-google/
  13. meta-hpe/
  14. meta-hxt/
  15. meta-ibm/
  16. meta-ingrasys/
  17. meta-inspur/
  18. meta-intel-openbmc/
  19. meta-inventec/
  20. meta-lenovo/
  21. meta-microsoft/
  22. meta-nuvoton/
  23. meta-openembedded/
  24. meta-openpower/
  25. meta-phosphor/
  26. meta-portwell/
  27. meta-qualcomm/
  28. meta-quanta/
  29. meta-raspberrypi/
  30. meta-security/
  31. meta-supermicro/
  32. meta-wistron/
  33. meta-x86/
  34. meta-xilinx/
  35. meta-yadro/
  36. poky/
  37. .gitignore
  38. .gitreview
  39. .templateconf
  40. MAINTAINERS
  41. openbmc-env
  42. OWNERS
  43. README.md
  44. setup
README.md

OpenBMC

Build Status

OpenBMC is a Linux distribution for management controllers used in devices such as servers, top of rack switches or RAID appliances. It uses Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your 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 28
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"

2) Download the source

git clone git@github.com:openbmc/openbmc.git
cd openbmc

3) Target your hardware

Any build requires an environment set up according to your hardware target. There is a special script in the root of this repository that can be used to configure the environment as needed. The script is called setup and takes the name of your hardware target as an argument.

The script needs to be sourced while in the top directory of the OpenBMC repository clone, and, if run without arguments, will display the list of supported hardware targets, see the following example:

$ . setup <machine> [build_dir]
Target machine must be specified. Use one of:

centriq2400-rep         f0b                     fp5280g2
gsj                     hr630                   hr855xg2
lanyang                 mihawk                  msn
neptune                 nicole                  olympus
olympus-nuvoton         on5263m5                p10bmc
palmetto                qemuarm                 quanta-q71l
romulus                 s2600wf                 stardragon4800-rep2
swift                   tiogapass               vesnin
witherspoon             witherspoon-tacoma      yosemitev2
zaius

Once you know the target (e.g. romulus), source the setup script as follows:

. setup romulus

For evb-ast2500, please use the below command to specify the machine config, because the machine in meta-aspeed layer is in a BSP layer and does not build the openbmc image.

TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2500/conf . openbmc-env

4) Build

bitbake obmc-phosphor-image

Additional details can be found in the docs repository.

OpenBMC Development

The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here

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.

Questions

First, please do a search on the internet. There's a good chance your question has already been asked.

For general questions, please use the openbmc tag on Stack Overflow. Please review the discussion on Stack Overflow licensing before posting any code.

For technical discussions, please see contact info below for Discord and mailing list information. Please don't file an issue to ask a question. You'll get faster results by using the mailing list or Discord.

Features of OpenBMC

Feature List

  • Host management: Power, Cooling, LEDs, Inventory, Events, Watchdog
  • Full IPMI 2.0 Compliance with DCMI
  • Code Update Support for multiple BMC/BIOS images
  • Web-based user interface
  • REST interfaces
  • D-Bus based interfaces
  • SSH based SOL
  • Remote KVM
  • Hardware Simulation
  • Automated Testing
  • User management
  • Virtual media

Features In Progress

  • OpenCompute Redfish Compliance
  • Verified Boot

Features Requested but need help

  • OpenBMC performance monitoring

Finding out more

Dive deeper into OpenBMC by opening the docs repository.

Technical Steering Committee

The Technical Steering Committee (TSC) guides the project. Members are:

  • Brad Bishop (chair), IBM
  • Nancy Yuen, Google
  • Sai Dasari, Facebook
  • James Mihm, Intel
  • Sagar Dharia, Microsoft
  • Supreeth Venkatesh, Arm

Contact