| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Dumps are disabled by default. This commit enables
the dump feature for ibm based systems.
Tested By:
* Dump flag enabled:
GET https://${bmc}/redfish/v1/Managers/bmc/LogServices
{
"@odata.id": "/redfish/v1/Managers/bmc/LogServices",
"@odata.type": "#LogServiceCollection.LogServiceCollection",
"Description": "Collection of LogServices for this Manager",
"Members": [
{
"@odata.id": "/redfish/v1/Managers/bmc/LogServices/Dump"
}
],
"Members@odata.count": 1,
"Name": "Open BMC Log Services Collection"
}
* Dump flag disabled:
GET https://${bmc}/redfish/v1/Managers/bmc/LogServices
{
"@odata.id": "/redfish/v1/Managers/bmc/LogServices",
"@odata.type": "#LogServiceCollection.LogServiceCollection",
"Description": "Collection of LogServices for this Manager",
"Members": [],
"Members@odata.count": 0,
"Name": "Open BMC Log Services Collection"
}
Signed-off-by: Asmitha Karunanithi <asmitk01@in.ibm.com>
Change-Id: Iad5a364ac46b5bf62bc2186eb29786454f650802
|
|
After over a year of discussion, Redfish released new power and thermal
schemas as part of the Redfish 2020.4 release.
These new powersubsystem, thermalsubsystem, fan, powersupply, etc
schemas can co-exist with the old power and thermal schemas.
The old schemas and the new schemas are controlled by different options.
The current plan for bmcweb is:
1. Until the new schemas are all in and tested, as a default, enable the
old schemas and disable the new.
2. After the new have been in and tested, enable them. This means the
old and new will co-exist if running the defaults. The sensor
collection behavior will reflect the new schemas, that is all sensors
can be found under the sensor collection.
3. After an OpenBMC release, at a later time, disable the old and add
appropriate deprecation.
This change here, enabling the new schemas, jumps meta-ibm to #2.
This reflects our desire for our Redfish clients to start using the new
schemas.
Some reasons why the ThermalSubsystem/PowerSubsystem are an improvement
on the existing Thermal/Power schemas:
1. They include the latest properties like LocationIndicatorActive.
2. Fans, PowerSupplies, Temperatures were arrays in the old schemas.
This was cumbersome and could hit limits of JSON arrays.
3. Large amount of static data mixed with sensor readings, which hurt
performance in certain cases.
4. Inconsistent definitions of properties vs newer schemas like Processor
and Memory schemas.
Reference:
https://www.dmtf.org/sites/default/files/standards/documents/DSP0268_2020.4.pdf
Tested: Built bmcweb. See the new sensor behavior.
Change-Id: I9a698cbc162a331c21c7dc5138000faac6247f9b
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
In the spirit of consistency with the new upstream override
syntax, change phosphor-discovery-service.bbclass to use it
and make tree-wide changes as appropriate.
After the change checked on Witherspoon on QEMU:
```
root@witherspoon:/etc/avahi/services# ls
obmc_console.service obmc_redfish.service obmc_rest.service
```
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ib1fe3cce57a0130378af789abd83b457e0c3a318
|
|
Change-Id: I9116ed7260e369136acb39eec15075db2d4dbeba
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
- This commit would enable the ibm-management-console compile-time
option for all the ibm machines.
(From meta-ibm rev: 9831b3a45141d4dc08b2624f07059299d65a9d7f)
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I69abd87d28903d27d2390f20153d730f658f8068
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
- This commit would switch the bmcweb options to meson
(From meta-ibm rev: fea636a8486e20e8ccd865670f56d34c9700a043)
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: Ieda83403ff381c616664170462915198fdf30507
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
- meta-phosphor has bmcweb bitbake file under interfaces,so
moving the append files accordingly.
(From meta-ibm rev: b7952717a7c74b0ebda2d7971f75b1b060f8911c)
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I86ba09396f109f0987220bcdd070a0fff8e1e972
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The metadata common to all IBM systems is confusingly split between
meta-ibm and meta-witherspoon. Move everything to meta-ibm.
The meta-ibm README is re-written to more accurately reflect the scope
of the layer.
Allow the configuration samples (bblayers.conf.sample,
local.conf.sample) to be sourced from either meta-ibm or
meta-witherspoon until such a time that any workflows and tooling have
had the opportunity to move to meta-ibm.
(From meta-ibm rev: 6e05ef2e90b214eaf4e43ee7027bbbb1d8d09442)
Change-Id: I3ec890d5300f9649c974ea6b9dca93a2e8a889ab
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Creating and Registering service files with additional
text data to uniquely identify IBM BMCs in a network.
(From meta-ibm rev: 2c2b286604e82f89edd973bc15aee78ecf4b9a7f)
Change-Id: I3b843684f5df6a9b2cbe8a3709ee1203fb44ce42
Signed-off-by: asmithakarun <asmithkr@in.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
