Gitiles
Code Review Sign In
gerrit.openbmc.org / mdmillerii / openbmc / 54720438ff318a989666e29c426f864ad17d17bb
commit54720438ff318a989666e29c426f864ad17d17bb[log] [tgz]
authorAndrew Geissler <openbmcbump-github@yahoo.com>Tue Jun 28 20:19:13 2022 -0500
committerAndrew Geissler <andrew@geissonator.com>Wed Jun 29 20:27:25 2022 +0000
tree10a188ee40bc4c2e9d53e9d65458661dda502679
parent220d1a1d9dd9eb4e02b896c4c801f91b21299bf9 [diff]
bmcweb: srcrev bump ceeba4f968..69320d54ef

AppaRao Puli (1):
      Add missing Context type to MetricReport

Carson Labrado (1):
      HttpClient: Increase httpReadBodyLimit

Claire Weinan (1):
      LogService: Add support for Fault Log

Ed Tanous (5):
      Replace BMCWEB_ROUTES lambdas with functions
      Remove old MAINTAINERS file
      Rearrange forward_unauthorized
      Move AccountService to separate methods
      Fix shadowed variable issues

Jason M. Bills (6):
      Clean up firstEntry boolean checks
      Update handling of skipped log entries
      log_services: use nlohmann::json::object_t
      log_services: don't replace res.jsonValue
      log_services: remove brace initialization
      Use an enum to return message registry parsing status

Jiaqing Zhao (7):
      certificate: Use ObjectMapper in getCertificateLocations
      certificate: Add getCertificateList for get collections
      registry: Base: Upgrade 1.11.0 -> 1.13.0
      error_messages: Add PropertyValueOutOfRange error
      memory: Use dbus::utility::DBusPropertiesMap::value_type
      query_param_test: Update Positive cases for Delegate
      Encode service object path with sdbusplus

Nan Zhou (22):
      dbus_utility: iwyu
      openbmc_dbus_rest_test: fix headers
      multipart_test: fix headers
      multipart_test: add namespace
      multipart_test: use ASSERT_EQ correctly
      Add Nan Zhou as a reviewer
      log_service: make function static
      health: remove boost container header
      human_sort_test: fix headers
      human_sort_test: add namespace
      http: utility_test: fix headers
      http: utility_test: fix namespace
      http: router_test: fix headers
      http: router_test: fix namespace
      query_param: fix headers
      query_param_test: fix namespaces
      dbus_utility_test: add namespace
      dbus_utility_test: clean up headers
      http_utility_test: fix headers
      clients.md: fix headers
      http_utility_test: add namespace
      http_utility_test: fix test case names

Tony Lee (1):
      Fix fail on get PostCode entry

Willy Tu (1):
      update_service: Refactor getSoftwareVersion into a seperate function

nitroglycerine (1):
      sessions: iwyu

Change-Id: I98d98d649b99ecdb99e3099c9efbe518b85f300d
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
1 file changed
tree: 10a188ee40bc4c2e9d53e9d65458661dda502679
  1. .github/
  2. meta-amd/
  3. meta-ampere/
  4. meta-aspeed/
  5. meta-asrock/
  6. meta-bytedance/
  7. meta-evb/
  8. meta-facebook/
  9. meta-fii/
  10. meta-google/
  11. meta-hpe/
  12. meta-ibm/
  13. meta-ingrasys/
  14. meta-inspur/
  15. meta-intel-openbmc/
  16. meta-inventec/
  17. meta-nuvoton/
  18. meta-openembedded/
  19. meta-openpower/
  20. meta-phosphor/
  21. meta-qualcomm/
  22. meta-quanta/
  23. meta-raspberrypi/
  24. meta-security/
  25. meta-supermicro/
  26. meta-tyan/
  27. meta-wistron/
  28. meta-yadro/
  29. poky/
  30. bitbake ⇨ poky/bitbake/
  31. LICENSE ⇨ poky/LICENSE
  32. meta ⇨ poky/meta
  33. meta-poky ⇨ poky/meta-poky/
  34. meta-skeleton ⇨ poky/meta-skeleton
  35. oe-init-build-env ⇨ poky/oe-init-build-env
  36. scripts ⇨ poky/scripts/
  37. .eslintrc.json
  38. .gitignore
  39. .gitreview
  40. .templateconf
  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

See the Yocto documentation for the latest requirements

Ubuntu

$ sudo apt install git python3-distutils gcc g++ make file wget \
    gawk diffstat bzip2 cpio chrpath zstd lz4 bzip2

Fedora

$ sudo dnf install git python3 gcc g++ gawk which bzip2 chrpath cpio
hostname file diffutils diffstat lz4 wget zstd rpcgen patch

2) Download the source

git clone https://github.com/openbmc/openbmc
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:

bletchley               mihawk                  swift
dl360poc                mori                    tatlin-archive-x86
e3c246d4i               mtjade                  tiogapass
ethanolx                nicole                  transformers
evb-ast2500             olympus-nuvoton         vegman-n110
evb-ast2600             on5263m5                vegman-rx20
evb-npcm750             p10bmc                  vegman-sx20
f0b                     palmetto                witherspoon
fp5280g2                quanta-q71l             witherspoon-tacoma
g220a                   romulus                 x11spi
gbs                     s2600wf                 yosemitev2
gsj                     s6q                     zaius
kudo                    s7106
lannister               s8036

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

. setup romulus

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:

  • Roxanne Clarke, IBM
  • Nancy Yuen, Google
  • Sai Dasari, Facebook
  • Terry Duncan, Intel
  • Sagar Dharia, Microsoft
  • Samer El-Haj-Mahmoud, Arm

Contact