Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / 9c5d7faa38873025141e211212f33aab00fa0eb0
commit9c5d7faa38873025141e211212f33aab00fa0eb0[log] [tgz]
authorWilliam A. Kennington III <wak@google.com>Fri Jul 08 14:39:13 2022 -0700
committerWilliam A. Kennington III <wak@google.com>Fri Jul 08 15:03:12 2022 -0700
tree91e65e78a0f1761cb993a431ab00c4953013d3d3
parent5f98f6d52c4cbb6852e88f0814fc6449ef44ef18 [diff]
glome: Bump 02f7d272..978ad9fb

Copybara-Service (1):
      Merge pull request #108 from l9i:l9i-fix-pylint

Markus Rudy (6):
      Enforce some code standards when compiling C. (#110)
      Merge pull request #112 from vvidic/ini-parser
      Merge pull request #114 from vvidic/docker
      Merge pull request #111 from vvidic/login-pam
      Correctly free the message buffer in case of an snprintf error
      Merge pull request #118 from vvidic/newline

Philipp Kern (10):
      Merge pull request #106 from vvidic/cli-login
      Merge pull request #113 from vvidic/addrinfo-free
      Merge pull request #119 from vvidic/option-tests
      Support compilation with both old and new pam_wrapper
      Run the C compilation presubmit on Debian stable and testing
      Merge pull request #123 from pkern/pamtest-fix
      Merge pull request #124 from pkern/debian-presubmit
      Merge pull request #128 from google/l9i/fakepassword
      Merge pull request #129 from vvidic/getopt-long
      Merge pull request #130 from vvidic/pam-options

Piotr Lewandowski (7):
      pyglome: more consise exception messages
      Fix the tag length check exception message
      Use comma, not semicolon for intervals notation
      pam_glome: support fake passwords from OpenSSH
      Apply clang-format
      Apply clang-format, Google style
      Use an error message matching the rest of the file

Valentin Vidic (9):
      Add login command to glome CLI (#91)
      Free struct addrinfo allocated by getaddrinfo
      Implement a simple INI parser for config files
      Create a Docker container for testing glome-login and PAM module
      Use the same auth function for PAM and login binary
      Make tests optional using a global meson option
      Fix handling of long authorization codes
      Add support for long and config options
      Sync PAM config options names with the rest of the code.

Change-Id: I07674f198f1a00ae7bff4feb99a01db940e7d7ad
Signed-off-by: William A. Kennington III <wak@google.com>
1 file changed
tree: 91e65e78a0f1761cb993a431ab00c4953013d3d3
  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