| /openbmc/ |
| D | opengrok1.0.log | 4 2025-10-03 03:01:07.738-0500 FINE t1 Executor.exec: Executing command [/usr/local/bin/ctags --list-languages] in directory '/opengrok/src/openbmc' with environment: {PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin, LANGUAGE=en_US:, SHELL=/bin/sh, LOGNAME=opengrok, OLDPWD=/opengrok/src/openbmc/x86-power-control, PWD=/opengrok/src/openbmc, LANG=en_US, SHLVL=1, HOME=/home/opengrok, _=/usr/bin/java}
5 2025-10-03 03:01:07.759-0500 FINE t1 Statistics.logIt: Finished command [/usr/local/bin/ctags --list-languages] in directory '/opengrok/src/openbmc' with exit code 0 (took 19 ms)
6 2025-10-03 03:01:07.760-0500 FINE t1 Executor.exec: Finished command [/usr/local/bin/ctags --list-languages] in directory '/opengrok/src/openbmc' with exit code 0
7 2025-10-03 03:01:07.762-0500 FINE t1 Executor.exec: Executing command [/usr/local/bin/ctags --version] in directory '/opengrok/src/openbmc' with environment: {PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin, LANGUAGE=en_US:, SHELL=/bin/sh, LOGNAME=opengrok, OLDPWD=/opengrok/src/openbmc/x86-power-control, PWD=/opengrok/src/openbmc, LANG=en_US, SHLVL=1, HOME=/home/opengrok, _=/usr/bin/java}
8 2025-10-03 03:01:07.767-0500 FINE t1 Statistics.logIt: Finished command [/usr/local/bin/ctags --version] in directory '/opengrok/src/openbmc' with exit code 0 (took 4 ms)
9 2025-10-03 03:01:07.768-0500 FINE t1 Executor.exec: Finished command [/usr/local/bin/ctags --version] in directory '/opengrok/src/openbmc' wit
[all...] |
| D | opengrok2.0.log | 4 2025-10-02 03:01:10.289-0500 FINE t1 Executor.exec: Executing command [/usr/local/bin/ctags --list-languages] in directory '/opengrok/src/openbmc' with environment: {PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin, LANGUAGE=en_US:, SHELL=/bin/sh, LOGNAME=opengrok, OLDPWD=/opengrok/src/openbmc/x86-power-control, PWD=/opengrok/src/openbmc, LANG=en_US, SHLVL=1, HOME=/home/opengrok, _=/usr/bin/java}
5 2025-10-02 03:01:10.311-0500 FINE t1 Statistics.logIt: Finished command [/usr/local/bin/ctags --list-languages] in directory '/opengrok/src/openbmc' with exit code 0 (took 18 ms)
6 2025-10-02 03:01:10.311-0500 FINE t1 Executor.exec: Finished command [/usr/local/bin/ctags --list-languages] in directory '/opengrok/src/openbmc' with exit code 0
7 2025-10-02 03:01:10.313-0500 FINE t1 Executor.exec: Executing command [/usr/local/bin/ctags --version] in directory '/opengrok/src/openbmc' with environment: {PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin, LANGUAGE=en_US:, SHELL=/bin/sh, LOGNAME=opengrok, OLDPWD=/opengrok/src/openbmc/x86-power-control, PWD=/opengrok/src/openbmc, LANG=en_US, SHLVL=1, HOME=/home/opengrok, _=/usr/bin/java}
8 2025-10-02 03:01:10.319-0500 FINE t1 Statistics.logIt: Finished command [/usr/local/bin/ctags --version] in directory '/opengrok/src/openbmc' with exit code 0 (took 4 ms)
9 2025-10-02 03:01:10.319-0500 FINE t1 Executor.exec: Finished command [/usr/local/bin/ctags --version] in directory '/opengrok/src/openbmc' wit
[all...] |
| /openbmc/linux/ |
| D | opengrok0.0.log | |
| D | opengrok1.0.log | |
| /openbmc/docs/ |
| H A D | hw-vendor-repos-policy.md | 13 OpenBMC Github project is made. It starts with the requirements and then some
19 OpenBMC architecture (bitbake, d-bus, phosphor-dbus-interfaces, ...).
22 guidelines to be used by the OpenBMC TOF in their decision to approve or not
26 following requirements to be eligible for a repository under OpenBMC:
34 5. It is a feature that is believed to be generally useful to the OpenBMC
38 6. It has an active OpenBMC community member that is willing to be a maintainer
41 under OpenBMC (vs. a recipe in OpenBMC that points to an external repository).
43 A repository must be hosted under OpenBMC if:
45 1. The repository depends on other OpenBMC-hosted repositories
47 If someone wishes to create a recipe within OpenBMC to point to an external
[all …]
|
| H A D | README.md | 1 # OpenBMC documentation
3 The [OpenBMC project](https://www.openbmc.org/) is a Linux Foundation project
6 for OpenBMC as a whole. There may be component-specific documentation in the
14 - Mail: `openbmc@lists.ozlabs.org` <https://lists.ozlabs.org/listinfo/openbmc>
15 - List Archive: <https://lore.kernel.org/openbmc/>
18 ## OpenBMC Development
20 These documents contain details on developing OpenBMC code itself
25 - [CONTRIBUTING.md](CONTRIBUTING.md): Guidelines for contributing to OpenBMC
28 speed on OpenBMC development
33 ## OpenBMC Usage
[all …]
|
| H A D | features.md | 1 # OpenBMC Features
3 Follow links to learn more about OpenBMC features:
41 https://github.com/openbmc/openbmc-test-automation/blob/master/README.md
42 [bmcweb]: https://github.com/openbmc/bmcweb/blob/master/README.md
44 https://github.com/openbmc/bmcweb/blob/master/DEVELOPING.md#redfish
46 …https://github.com/openbmc/phosphor-dbus-interfaces/tree/master/yaml/xyz/openbmc_project/Certs/REA…
48 …https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Chassis/R…
50 https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/README.md
52 https://github.com/openbmc/docs/blob/master/architecture/object-mapper.md
54 https://github.com/openbmc/entity-manager/blob/master/README.md
[all …]
|
| H A D | meta-layer-guidelines.md | 1 # OpenBMC meta layer guidelines
10 ## Meta layers should not patch projects that exist within the openBMC tree
40 changes that OpenBMC stacks against Yocto recipes, the more unmaintainable it
42 the Yocto community is as responsive (sometimes much faster) than the OpenBMC
49 cherry-pick the commit into the OpenBMC tree, with a pointer to the review in
59 There are some OpenBMC projects that are utilized outside of OpenBMC. As such,
60 there are configuration items that are not intended to be used in OpenBMC, or
78 OpenBMC is an open source project, and is intended to be built from source, with
91 Without this guideline, a loophole is present that allows OpenBMC developers to
93 they control, but which OpenBMC has no input on the content of. This splits the
[all …]
|
| H A D | glossary.md | 5 - Include terms specific to the OpenBMC project, OpenBMC reference platforms
15 OpenBMC system. OpenBMC D-Bus APIs are documented in
16 `https://github.com/openbmc/phosphor-dbus-interfaces`. For example, see the tree
19 IPMI - Intelligent Platform Management Interface. OpenBMC implements a subset of
22 ODM - Original design manufacturer. In OpenBMC, ODM generally refers to the
25 OEM - Original equipment manufacturer. In OpenBMC, OEM generally refers to the
28 Phosphor - Informally designates OpenBMC software or APIs designed for use
32 OpenBMC provides Redfish REST APIs for platform management.
34 REST - Representational State Transfer. OpenBMC provides REST APIs.
|
| /openbmc/docs/security/ |
| H A D | obmc-security-response-team-guidelines.md | 3 These are the guidelines for OpenBMC security responders, including the security
7 Each project within OpenBMC works independently to resolve security
9 consistency within the OpenBMC project, and helps to get CVEs assigned.
26 and OpenBMC).
28 - Determine if the problem is in OpenBMC.
29 - If the problem is in a project that OpenBMC uses, re-route the problem to
31 - Note that the problem may be in a customized version of OpenBMC but not
32 in OpenBMC itself.
33 - Determine which OpenBMC areas should address the problem.
35 - The Ecosystem would normally be "OpenBMC" and the package name is
[all …]
|
| H A D | how-to-report-a-security-vulnerability.md | 3 This describes how you can report an OpenBMC security vulnerability privately to
14 To begin the process: Privately contact the OpenBMC security response team and
17 - Suggest sending an email. Use `openbmc-security at lists.ozlabs.org`.
22 - The version and configuration of OpenBMC the problem appears in.
27 Please note the OpenBMC project has multiple source code repositories. Each has
37 - The OpenBMC security response team.
42 - The OpenBMC [CVE Numbering Authority (CNA)][] (members of the OpenBMC security
45 Anyone brought onboard should be given a link to the OpenBMC [security
52 - At the agreed time, publish the OpenBMC security advisory, reveal the fix, and
62 - Join the OpenBMC community and fix the problem yourself.
[all …]
|
| /openbmc/openbmc-tools/tof-voters/config/ |
| H A D | rejected_patterns.yaml | 3 - openbmc/s2600wf-misc
4 - openbmc/witherspoon-pfault-analysis
8 - "openbmc/google-.*"
9 - "openbmc/ibm-.*"
10 - "openbmc/intel-.*"
11 - "openbmc/meta-.*"
32 openbmc/entity-manager:
35 openbmc/libmctp:
38 openbmc/openbmc:
42 openbmc/openbmc-test-automation:
[all …]
|
| /openbmc/skeleton/pystatemgr/ |
| H A D | discover_system_state.py | 7 "bus_name": "org.openbmc.control.Power",
8 "object_name": "/org/openbmc/control/power0",
9 "interface_name": "org.openbmc.control.Power",
12 "bus_name": "org.openbmc.Sensors",
13 "object_name": "/org/openbmc/sensors/host/cpu0/OccStatus",
14 "interface_name": "org.openbmc.SensorValue",
17 "bus_name": "org.openbmc.Sensors",
18 "object_name": "/org/openbmc/sensors/host/cpu1/OccStatus",
19 "interface_name": "org.openbmc.SensorValue",
22 "bus_name": "org.openbmc.Sensors",
[all …]
|
| /openbmc/openbmc-test-automation/ |
| H A D | README.md | 1 ## Features of OpenBMC Test Automation
8 - [Legacy REST](https://github.com/openbmc/openbmc-test-automation/releases/tag/v4.0-stable)
45 - Miscellaneous Packages required to be installed for OpenBmc Automation.
63 you'll find this file once your clone openbmc-test-automation repository.
66 the OpenBMC GUI Test Setup Guide. Note: GUI test cases under `gui/` will not
68 [OpenBMC GUI Test Setup Guide](https://github.com/openbmc/openbmc-test-automation/blob/master/docs/…
82 ## OpenBMC Test Development
84 These documents contain details on developing OpenBMC test code and debugging.
86 - [MAINTAINERS](OWNERS): OpenBMC test code maintainers information.
88 - [Code Check Tools](https://github.com/openbmc/openbmc-test-automation/blob/master/docs/code_stand…
[all …]
|
| /openbmc/openbmc/ |
| H A D | README.md | 1 # OpenBMC chapter
3 [](https://jenkins.o…
5 OpenBMC is a Linux distribution for management controllers used in devices such
13 ## Setting up your OpenBMC project
38 git clone https://github.com/openbmc/openbmc
39 cd openbmc
49 The script needs to be sourced while in the top directory of the OpenBMC
60 [meta-phosphor/docs](https://github.com/openbmc/openbmc/blob/master/meta-phosphor/docs/supported-ma…
74 Additional details can be found in the [docs](https://github.com/openbmc/docs)
77 ## OpenBMC Development
[all …]
|
| /openbmc/openbmc-test-automation/test_lists/ |
| H A D | skip_test_palmetto | 1 # https://github.com/openbmc/openbmc/issues/93
4 # https://github.com/openbmc/openbmc-test-automation/issues/207
6 # https://github.com/openbmc/openbmc-test-automation/issues/123
14 # https://github.com/openbmc/openbmc/issues/901
16 # https://github.com/openbmc/openbmc/issues/1142
18 # https://github.com/openbmc/openbmc-test-automation/issues/396
28 # https://github.com/openbmc/openbmc-test-automation/issues/546
38 # https://github.com/openbmc/openbmc-test-automation/issues/729
49 # https://github.com/openbmc/openbmc-test-automation/issues/1411
|
| /openbmc/openbmc-build-scripts/jenkins/ |
| H A D | run-meta-ci | 4 # This script is responsible for setting up a openbmc/openbmc build
10 # GERRIT_PROJECT: openbmc/meta-* layer under test (i.e. openbmc/meta-phosphor)
20 # git clone https://github.com/openbmc/openbmc-test-automation.git --branch ${GERRIT_BRANCH} --sing…
21 git clone https://github.com/openbmc/openbmc-test-automation.git --branch master --single-branch
29 # Remove openbmc dir in prep for full repo clone
30 rm -rf openbmc
32 # Clone openbmc/openbmc
33 git clone https://github.com/openbmc/openbmc.git --branch "${GERRIT_BRANCH}" --single-branch
36 mkdir -p ./openbmc/"$META_REPO"/
39 rm -rf ./openbmc/"$META_REPO"/*
[all …]
|
| /openbmc/openbmc/meta-phosphor/classes/ |
| H A D | obmc-phosphor-image.bbclass | 1 # Common code for generating Phosphor OpenBMC images.
3 # Additional IMAGE_FEATURES available with Phosphor OpenBMC:
5 # - obmc-bmc-state-mgmt - OpenBMC BMC state management
6 # - obmc-bmcweb - OpenBMC webserver
7 # - obmc-chassis-mgmt - OpenBMC chassis management
8 # - obmc-chassis-state-mgmt - OpenBMC chassis state management
9 # - obmc-console - OpenBMC serial over LAN
10 # - obmc-dbus-monitor - OpenBMC dbus monitoring
11 # - obmc-debug-collector - OpenBMC debug collector
12 # - obmc-devtools - OpenBMC development and debugging tools
[all …]
|
| /openbmc/docs/development/ |
| H A D | dev-environment.md | 1 # OpenBMC Development Environment
3 **Document Purpose:** How to set up an OpenBMC development environment
11 OpenBMC uses the [Yocto](https://www.yoctoproject.org/) Project as its
12 underlying building and distribution generation framework. The main OpenBMC
13 [README](https://github.com/openbmc/openbmc/blob/master/README.md) provides
14 information on getting up and going with Yocto and OpenBMC. This tutorial will
15 walk you through utilizing bitbake to build OpenBMC firmware and boot it in
18 Bitbake is the build engine used by Yocto and OpenBMC to build its custom Linux
20 OpenBMC images.
22 This doc walks through the recommended steps for setting up an OpenBMC
[all …]
|
| /openbmc/docs/testing/ |
| H A D | run-test-docker.md | 1 # Run OpenBMC Test Automation Using Docker
3 Running OpenBMC automation using Docker involves creating a Docker image and
18 3. Clone openbmc-build-scripts repository.
20 `git clone https://github.com/openbmc/openbmc-build-scripts`
22 4. Change directory to openbmc-build-scripts.
24 `cd openbmc-build-scripts`
28 "openbmc/ubuntu-robot-qemu". You can check images using "docker images"
46 2. Clone openbmc-test-automation repository.
48 `git clone https://github.com/openbmc/openbmc-test-automation`
60 --tty openbmc/ubuntu-robot-qemu python -m robot \
[all …]
|
| /openbmc/webui-vue/ |
| H A D | CONTRIBUTING.md | 5 The following is a set of guidelines for contributing to the OpenBMC Web UI.
21 The OpenBMC projects use Gerrit for code review. Use the
22 [OpenBMC Gerrit Setup/Integration guidelines](https://github.com/openbmc/docs/blob/master/developme…
31 1. Visit <https://gerrit.openbmc-project.xyz/admin/repos/openbmc/webui-vue>
75 [OpenBMC Code of Conduct](https://github.com/openbmc/docs/blob/master/code-of-conduct.md).
79 The OpenBMC communicates using a mail list and the Discord channel. Although you
83 - Mail: <openbmc@lists.ozlabs.org> <https://lists.ozlabs.org/listinfo/openbmc>
89 [existing GitHub issues](https://github.com/openbmc/webui-vue/issues) to see if
91 [Bug report template](https://github.com/openbmc/webui-vue/issues/new?assignees=&labels=&template=b…
95 [existing GitHub issues](https://github.com/openbmc/webui-vue/issues). If no one
[all …]
|
| /openbmc/entity-manager/schemas/ |
| H A D | global.json | 55 "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Common/UUID"
58 "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Inventory/Decorator/Asset"
61 … "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Inventory/Decorator/AssetTag"
64 "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Inventory/Decorator/Cable"
67 … "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Inventory/Decorator/Compatible"
70 … "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Inventory/Decorator/ManagedHost"
73 … "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Inventory/Decorator/Replaceable"
76 "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Inventory/Decorator/Slot"
79 … "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Inventory/Decorator/Revision"
82 … "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Inventory/Item/Board/Motherboard"
[all …]
|
| /openbmc/docs/architecture/code-update/ |
| H A D | firmware-update-over-redfish.md | 9 OpenBMC is moving to [Redfish][1] as its standard for out of band management.
15 OpenBMC's existing firmware update implementation over to Redfish.
19 The existing firmware update details for OpenBMC can be found in the
28 Some differences between the Redfish API and OpenBMC's existing API:
30 - Redfish has a single upload and update API. OpenBMC has a concept of uploading
33 same target. OpenBMC does have support for this concept (for example when a
36 - OpenBMC has the concept of a priority that allows a user to chose an image
43 image with the same command. OpenBMC does not support this currently.
46 Existing OpenBMC only has support for TFTP.
48 (Immediate, OnReset, AtMaintenanceWindowStart...). Existing OpenBMC firmware
[all …]
|
| /openbmc/bmcweb/docs/ |
| H A D | OEM_SCHEMAS.md | 13 and can be maintained forever. Within OpenBMC, we have no such group of
20 OpenBMC's external Redfish API aims to be as compatible between systems as
23 which are likely to overlap, which increases the amount of code overall. OpenBMC
33 implemented in projects that OpenBMC isn't aware of.
35 If a given feature eventually becomes standardized, OpenBMC OEM endpoints now
40 DMTF has many more Redfish experts than OpenBMC. While the bmcweb maintainers do
62 possible, message the new feature through the normal openbmc communications
63 channels to ensure OpenBMC is properly represented in the meeting/forum.
65 for change requests, and get your schema changes standardized; While OpenBMC
70 to OpenBMC", proceed to write an OpenBMC design document about the new
[all …]
|
| /openbmc/openbmc-test-automation/gui/lib/ |
| H A D | resource.robot | 2 Documentation This is a resource file of OpenBMC ASMI It contains the
42 Launch OpenBMC GUI Browser
43 [Documentation] Launch the OpenBMC GUI URL on a browser.
89 # URL Openbmc GUI URL to be open
90 # (e.g. https://openbmc-test.mybluemix.net/#/login).
100 Login OpenBMC GUI
124 # obmc_test_setup The OpenBMC required state.
127 Launch Browser And Login OpenBMC GUI
143 Reboot OpenBMC
146 Run Keywords Power On OpenBMC AND
[all …]
|