| 21892513 | 08-Jul-2023 |
Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> |
com.ibm: Add NotifyDump method
This commit introduces a new 'NotifyDump' method in a
new com.ibm.Dump.Notify interface to cater the specific
requirements of IBM OpenPOWER systems. This is
supplement
com.ibm: Add NotifyDump method
This commit introduces a new 'NotifyDump' method in a
new com.ibm.Dump.Notify interface to cater the specific
requirements of IBM OpenPOWER systems. This is
supplementing the general dbus 'Notify' method but
caters to the unique needs of IBM OpenPOWER systems.
The 'NotifyDump' method creates or updates a dump
entry based on parameters and specific dump type,
like 'System' or 'Resource'. The host provides a
source dump id, size, dump type and a 'token'. The
token helps identify user-initiated dump requests and
defaults to 0 if not valid.
Change-Id: Ic036b6ce30ccd0d12717c1ee314ba8aa4c4c74f3
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
show more ...
|
| 7193e55f | 25-Apr-2023 |
Kantesh Nagaradder <kantesh.nagaradder@ibm.com> |
Add a new dbus interface for VSBK record
This commit will add interface to support the new record(VSBK) and its
keywords to store the system backplane's critical data as backup.
The Bonnell BMC is
Add a new dbus interface for VSBK record
This commit will add interface to support the new record(VSBK) and its
keywords to store the system backplane's critical data as backup.
The Bonnell BMC is embedded in the system backplane, so if either
fails, the backplane should be replaced as a whole. Thus, we must
backup the system backplane critical keywords on the VSBK record on the
operator panel base EEPROM. Hence VSBK interface being added.
Below is the introspect for VSBK:
busctl introspect xyz.openbmc_project.Inventory.Manager
/xyz/openbmc_project/inventory/system/chassis/motherboard/
base_op_panel_blyth com.ibm.ipzvpd.VSBK
NAME TYPE SIGNATURE RESULT/VALUE FLAGS
.BR property ay 2 83 48 emits-change writable
.D0 property ay 1 1 emits-change writable
.ES property ay 7 66 90 83 48 48 48 51 emits-change writable
.F5 property ay 16 32 32 32 32 32 32 32 32 32 32 32 3... emits-change writable
.F6 property ay 0 emits-change writable
.FC property ay 8 50 69 52 65 45 48 48 49 emits-change writable
.FV property ay 32 32 32 32 32 32 32 32 32 32 32 32 3... emits-change writable
.LX property ay 8 49 0 4 1 0 48 0 123 emits-change writable
.RB property ay 4 49 32 32 32 emits-change writable
.RG property ay 4 0 0 0 0 emits-change writable
.RT property ay 4 86 83 66 75 emits-change writable
.SE property ay 7 66 48 48 48 48 48 51 emits-change writable
.SU property ay 6 0 4 172 31 28 19 emits-change writable
.TM property ay 8 57 48 50 56 45 50 49 66 emits-change writable
.VZ property ay 2 48 50 emits-change writable
.WN property ay 12 67 48 53 48 55 54 48 67 52 56 57 66 emits-change writable
Change-Id: I333001f4317aa954dfd700dfa153133e179c4785
Signed-off-by: Kantesh Nagaradder <kantesh.nagaradder@ibm.com>
show more ...
|
| df32eb57 | 26-Apr-2023 |
Myung Bae <myungbae@us.ibm.com> |
Add association between FabricAdapter and Port
As a course of implementing PortCollection and Port schemas,
this commit adds a new association to describe the links
between FabricAdapter and Port.
Add association between FabricAdapter and Port
As a course of implementing PortCollection and Port schemas,
this commit adds a new association to describe the links
between FabricAdapter and Port.
- FabricAdapter may be "connected_to" one or more ports,
- A port may also be "connecting" one or more items.
The generic associations of 'containing' and 'contained_by'
are considered, but they are for the physically "containing" items.
Related schemas are:
- https://redfish.dmtf.org/schemas/v1/Port.v1_8_0.json
```
"Links": {
"description": "The links to other resources that are related to this resource.",
"properties": {
"AssociatedEndpoints": {
"description": "An array of links to the endpoints at the other end of the link.",
"items": {
"$ref": "http://redfish.dmtf.org/schemas/v1/Endpoint.json#/definitions/Endpoint"
},
"longDescription": "This property shall contain an array of links to resources of type Endpoint that represent the endpoints to which this port is connected.",
"readonly": true,
"type": "array"
},
"AssociatedEndpoints@odata.count": {
"$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/count"
},
```
- https://redfish.dmtf.org/schemas/v1/FabricAdapter.v1_5_0.json
```
"Ports": {
"$ref": "http://redfish.dmtf.org/schemas/v1/PortCollection.json#/definitions/PortCollection",
"description": "The link to the collection of ports that exist on the fabric adapter.",
"longDescription": "This property shall contain a link to a Resource Collection of type PortCollection.",
"readonly": true
},
```
Change-Id: I2cc8caf0128bf1cfa619312e689fe02039977e44
Signed-off-by: Myung Bae <myungbae@us.ibm.com>
show more ...
|
| 927d0930 | 06-Mar-2023 |
Ninad Palsule <ninadpalsule@us.ibm.com> |
Add a new dbus interface to get list of consoles
The "xyz.openbmc_project.Console.Access" interface will provide a
single property containing the name of the abstract socket for the
object hosting t
Add a new dbus interface to get list of consoles
The "xyz.openbmc_project.Console.Access" interface will provide a
single property containing the name of the abstract socket for the
object hosting the interface. The caller can use mapper function to
find the list of registered consoles. The bmcweb can exploit this
interface by putting console for each console object.
The SocketName attribute provides unix abstract socket name and it's
first character is always null, the attribute type is an array of bytes
types instead of string type. The byte array does not include a null
terminator.
For example, object path and property exposed for host console is as
follows:
Object:
/xyz/openbmc_project/console/host
Property:
SocketName -> "\0obmc-console.host"
The tree for console0:
$ busctl tree xyz.openbmc_project.Console.console0
`-/xyz
`-/xyz/openbmc_project
`-/xyz/openbmc_project/console
`-/xyz/openbmc_project/console/console0
The introspect for console0:
busctl introspect xyz.openbmc_project.Console.console0 /xyz/openbmc_project/console/console0
NAME TYPE SIGNATURE RESULT/VALUE FLAGS
org.freedesktop.DBus.Introspectable interface - - -
.Introspect method - s -
org.freedesktop.DBus.Peer interface - - -
.GetMachineId method - s -
.Ping method - - -
org.freedesktop.DBus.Properties interface - - -
.Get method ss v -
.GetAll method s a{sv} -
.Set method ssv - -
.PropertiesChanged signal sa{sv}as - -
xyz.openbmc_project.Console.Access interface - - -
.SocketName property ay 22 0 111 98 109 99 45 99 111 110 115 ... -
Related commits:
1) phosphor-dbus-interface: https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/61486
2) obmc-console: https://gerrit.openbmc.org/c/openbmc/obmc-console/+/62496
3) bmcweb: https://gerrit.openbmc.org/c/openbmc/bmcweb/+/62525
Change-Id: Ic50d311b327d9a4d917e4656af3ebeebfe95b5c9
Signed-off-by: Ninad Palsule <ninadpalsule@us.ibm.com>
show more ...
|
| 33b9a7f8 | 07-Feb-2022 |
Matt Spinler <spinler@us.ibm.com> |
inventory.decorator: Add slot number interface
This interface provides a slot number property for an inventory item.
The initial use case is to hang this on certain
phosphor-inventory-manager paths
inventory.decorator: Add slot number interface
This interface provides a slot number property for an inventory item.
The initial use case is to hang this on certain
phosphor-inventory-manager paths so that when entity-manager probes on
them it can have $SlotNumber available as a variable to give a stable
sensor name, such as 'PCIe Card $SlotNumber Temp'.
Without this, if say the $index variable is used instead, and then there
is no guarantee which device will have which sensor name, especially for
cards that can be added in any order when the BMC is running.
Stable sensor names are important in the
phosphor-inventory-manager/entity-manager hybrid model where PIM is used
for inventory and EM is just used for config.
There is a LocationCode property already that could possibly be used on
some systems, but on IBM systems at least it contains the system serial
number so would vary from system to system which isn't desired either.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Iea95d7ad123672909799244b0d80f564cb40d425
show more ...
|
| ae1cf7b0 | 11-Apr-2022 |
Paul Fertser <fercerpav@gmail.com> |
Syslog: introduce interfaces for e-mail sending
Interfaces to configure multiple e-mail destinations, each with an
individual threshold for the priority level of the syslog messages.
The idea is to
Syslog: introduce interfaces for e-mail sending
Interfaces to configure multiple e-mail destinations, each with an
individual threshold for the priority level of the syslog messages.
The idea is to provide facilities to implement a minimally useful subset
of Redfish Event Destinations for e-mail with ability to add additional
properties if the need arises.
D-Bus object path for each destination contains 8 digits of a mailto
hash, so Level can be changed later but for another URI a new object
needs to be created.
Current set of properties is made on assumption that organisation has an
SMTP smarthost (that BMC is allowed to use without authentication) which
takes care of dispatching messages; rsyslog's ommail module is
considered for the initial implementation.
Example session:
root@qemuarm:~# busctl tree xyz.openbmc_project.Syslog.Config
└─/xyz
└─/xyz/openbmc_project
└─/xyz/openbmc_project/logging
└─/xyz/openbmc_project/logging/config
├─/xyz/openbmc_project/logging/config/mail
│ ├─/xyz/openbmc_project/logging/config/mail/2dc1e699
│ ├─/xyz/openbmc_project/logging/config/mail/5d43d672
│ ├─/xyz/openbmc_project/logging/config/mail/b4dc9055
│ ├─/xyz/openbmc_project/logging/config/mail/d5d4db03
│ └─/xyz/openbmc_project/logging/config/mail/e0974603
└─/xyz/openbmc_project/logging/config/remote
root@qemuarm:~# busctl introspect xyz.openbmc_project.Syslog.Config /xyz/openbmc_project/logging/config/mail
NAME TYPE SIGNATURE RESULT/VALUE FLAGS
org.freedesktop.DBus.Introspectable interface - - -
.Introspect method - s -
org.freedesktop.DBus.Peer interface - - -
.GetMachineId method - s -
.Ping method - - -
org.freedesktop.DBus.Properties interface - - -
.Get method ss v -
.GetAll method s a{sv} -
.Set method ssv - -
.PropertiesChanged signal sa{sv}as - -
xyz.openbmc_project.Collection.DeleteAll interface - - -
.DeleteAll method - - -
xyz.openbmc_project.Logging.Syslog.Destination.Mail interface - - -
.From property s "from@some.domain" emits-change writable
xyz.openbmc_project.Logging.Syslog.Destination.Mail.Create interface - - -
.Create method ss o -
xyz.openbmc_project.Network.Client interface - - -
.Address property s "smarthost.lan" emits-change writable
.Port property q 25 emits-change writable
xyz.openbmc_project.Object.Enable interface - - -
.Enabled property b true emits-change writable
root@qemuarm:~# busctl introspect xyz.openbmc_project.Syslog.Config /xyz/openbmc_project/logging/config/mail/d5d4db03
NAME TYPE SIGNATURE RESULT/VALUE FLAGS
org.freedesktop.DBus.Introspectable interface - - -
.Introspect method - s -
org.freedesktop.DBus.Peer interface - - -
.GetMachineId method - s -
.Ping method - - -
org.freedesktop.DBus.Properties interface - - -
.Get method ss v -
.GetAll method s a{sv} -
.Set method ssv - -
.PropertiesChanged signal sa{sv}as - -
xyz.openbmc_project.Logging.Syslog.Destination.Mail.Entry interface - - -
.Level property s "xyz.openbmc_project.Logging.Entry.Leve… emits-change writable
.Mailto property s "mailto://someone2@otherdomain.test" emits-change
xyz.openbmc_project.Object.Delete interface - - -
.Delete method - - -
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
Change-Id: Ic78fc2bf3608c1dd7ec0c962412e69062dde48d4
show more ...
|
| 05cf6954 | 17-Feb-2022 |
Patrick Williams <patrick@stwcx.xyz> |
run-ci: ensure old generated content is removed
Remove the old generated directories before re-running the generate
script in order to detect if spurious files are left in place.
See I9dcc51fd23f2d
run-ci: ensure old generated content is removed
Remove the old generated directories before re-running the generate
script in order to detect if spurious files are left in place.
See I9dcc51fd23f2dac56b7b8efca57ca789e3075309 as an example of spurious
files previously being identified.
Tested: Pushed this change to Gerrit in front of I9dcc51f and confirmed
the CI failure that is fixed by that commit.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ia27fbe11f8ef6399da05bbeb741e818e77d859cf
show more ...
|
| 4f40f2f3 | 17-Feb-2022 |
Patrick Williams <patrick@stwcx.xyz> |
gen: remove spurious files
Removing the generated subdirectories and regenerating results in
old meson.build being cleaned out which are no longer applicable.
Commit the cleanup of them.
Signed-off
gen: remove spurious files
Removing the generated subdirectories and regenerating results in
old meson.build being cleaned out which are no longer applicable.
Commit the cleanup of them.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I9dcc51fd23f2dac56b7b8efca57ca789e3075309
show more ...
|