commit	c7d531ee8e587e058232df0ca6a9a7ba6a399fd8	[log] [tgz]
author	Andrew Geissler <openbmcbump-github@yahoo.com>	Mon Dec 05 15:50:38 2022 -0600
committer	Andrew Geissler <andrew@geissonator.com>	Mon Dec 05 23:16:29 2022 +0000
tree	b4c8644a4638fb04886a2279ef94a0c2736e2f0c
parent	1cb61b71e86d3c3705395e09f02edac7e5cc7e95 [diff]

phosphor-networkd: srcrev bump 9f621f3e89..9bc50f5e6b

Patrick Williams (1):
      sdbusplus: use shorter type aliases

William A. Kennington III (50):
      ethernet_interface: Fix vlan return object
      rtnetlink_server: Avoid refreshing for gateway changes
      rtnetlink: Migrate IP functions
      rtnetlink_server: Don't refresh for addresses
      ethernet_interface: Reduce error spam for addrs
      rtnetlink: Migrate neighbor functions
      rtnetlink_server: Don't refresh for neighbors
      rtnetlink: Handle parsing errors more gracefully
      ethernet_interface: DHCP settings don't require refresh
      types: Migrate all of the Info types
      network_manager_main: Make sure errors sync to journal
      rtnetlink: Return neighbor even if addr is missing
      network_manager: Async query all interface states
      network_manager: Absorb all state change functions
      test/rtnetlink_server: Remove
      network_manager: Standardize add/remove interface
      network_manager: Support queueing additional interface data
      network_manager: Move interface validation
      rtnetlink: Add public interface parser
      rtnetlink_server: Add interfaces dynamically
      network_manager: Add addresses to undiscovered interfaces
      network_manager: Add neighbors to undiscovered interfaces
      network_manager: Add gateways to undiscovered interfaces
      rtnetlink_server: Dump all netlink data at startup
      ethernet_interface: Remove all other refreshes
      config_parser: Add support for checking file existence
      util: Reduce error messages for config options
      dhcp_configuration: Don't depend on interface queries
      ethernet_interface: Fix updating neighbor
      ethernet_interface: Update ethtool for interface updates
      network_manager: Don't log errors for ignored interfaces
      treewide: Completely remove global refresh
      routing_table: Remove obsolete code
      ethernet_interface: Fix updating sub objects
      ethernet_interface: Remove optional signal emission
      network_manager: Keep interface info around
      network_manager: Implement interface rename
      ethernet_interface: Migrate object creation from network_manager
      treewide: Cleanup signal emission
      system_configuration: Fix new hostname updates
      network_manager: Remove unhandled exception
      network_manager: Add reload post hooks
      system_queries: Add netlink based delete
      ethernet_interface: Fix updates without interface idx
      ethernet_interface: Fix VLAN delete
      ethernet_interface: Remove spurious reloads
      inventory_mac: Migrate code out of other places
      util: Remove charconv
      test/util: Simplify
      treewide: Move timers out of networkd lib scope

Change-Id: Ifa1400170ef24e0f926fa652b681c93028583f08
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>

meta-phosphor/recipes-phosphor/network/phosphor-network_git.bb[diff]

1 file changed

tree: b4c8644a4638fb04886a2279ef94a0c2736e2f0c

README.md

OpenBMC

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               mori                    s8036
dl360poc                mtjade                  swift
e3c246d4i               mtmitchell              tatlin-archive-x86
ethanolx                nicole                  tiogapass
evb-ast2500             olympus-nuvoton         transformers
evb-ast2600             on5263m5                vegman-n110
evb-npcm750             p10bmc                  vegman-rx20
f0b                     palmetto                vegman-sx20
fp5280g2                qcom-dc-scm-v1          witherspoon
g220a                   quanta-q71l             witherspoon-tacoma
gbs                     romed8hm3               x11spi
greatlakes              romulus                 yosemitev2
gsj                     s2600wf                 zaius
kudo                    s6q
lannister               s7106

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

Mail: openbmc@lists.ozlabs.org https://lists.ozlabs.org/listinfo/openbmc
Discord: https://discord.gg/69Km47zH98