Home
last modified time | relevance | path

Searched +full:redfish +full:- +full:map (Results 1 – 25 of 78) sorted by relevance

1234

/openbmc/sdbusplus/tools/sdbusplus/schemas/
H A Devents.schema.yaml1 $id: https://openbmc-project.xyz/sdbusplus/events.schema.yaml
2 $schema: https://json-schema.org/draft/2020-12/schema
6 base-event:
13 class and Redfish Message ID.
16 pattern: "^[0-9]+\\.[0-9]+\\.[0-9]+$"
20 exist for generation in the Redfish Message Registry. The
30 pattern: "^[A-Z][A-Z0-9a-z]*$"
46 to be part of the Redfish `MessageArgs` (and not
49 - name
50 - description
[all …]
/openbmc/bmcweb/redfish-core/src/
H A Ddbus_log_watcher.cpp22 namespace redfish namespace
26 const dbus::utility::DBusPropertiesMap& map, EventLogObjectsType& event) in eventLogObjectFromDBus() argument
29 fillDbusEventLogEntryFromPropertyMap(map); in eventLogObjectFromDBus()
39 event.timestamp = redfish::time_utils::getDateTimeUintMs(entry.Timestamp); in eventLogObjectFromDBus()
41 // This dbus property is not documented to contain the Redfish Message Id, in eventLogObjectFromDBus()
47 // experimental-redfish-dbus-log-subscription is stabilized in eventLogObjectFromDBus()
52 // to map to the message args. Leaving this branch here for it to be in eventLogObjectFromDBus()
59 const dbus::utility::DBusPropertiesMap& map) in dbusEventLogMatchHandlerSingleEntry() argument
63 bool success = DbusEventLogMonitor::eventLogObjectFromDBus(map, event); in dbusEventLogMatchHandlerSingleEntry()
89 const dbus::utility::DBusPropertiesMap& map = pair.second; in onDbusEventLogCreated() local
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DAttributeRegistry.v1_3_9.json2 "$id": "http://redfish.dmtf.org/schemas/v1/AttributeRegistry.v1_3_9.json",
4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
13 "description": "This property shall specify a valid odata or Redfish property.",
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
37 …"description": "The `AttributeRegistry` schema contains a set of key-value pairs that represent th…
38 …"longDescription": "This resource shall represent an attribute registry for a Redfish implementati…
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
[all …]
H A DExternalAccountProvider.v1_8_0.json2 "$id": "http://redfish.dmtf.org/schemas/v1/ExternalAccountProvider.v1_8_0.json",
4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
20 "OEM": "An OEM-specific external authentication or directory service.",
21 "RedfishService": "An external Redfish service.",
25 …count provider shall be a Microsoft Active Directory Technical Specification-conformant service. …
26 …l account provider shall be an RFC4511-conformant service. The `ServiceAddresses` property shall …
27 …-conformant service. The `ServiceAddresses` property shall contain RFC3986-defined URIs that corr…
28 …Redfish Specification-conformant service. The `ServiceAddresses` property shall contain URIs to `…
29 …l account provider shall be an RFC8907-conformant service. The `ServiceAddresses` property shall …
[all …]
H A DMemoryRegion.v1_0_3.json2 "$id": "http://redfish.dmtf.org/schemas/v1/MemoryRegion.v1_0_3.json",
4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
13 "description": "This property shall specify a valid odata or Redfish property.",
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
39 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
40 "description": "This property shall specify a valid odata or Redfish property.",
54 … "$ref": "http://redfish.dmtf.org/schemas/v1/MemoryChunks.json#/definitions/MemoryChunks",
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A DAttributeRegistry.v1_3_9.json2 "$id": "http://redfish.dmtf.org/schemas/v1/AttributeRegistry.v1_3_9.json",
4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
13 "description": "This property shall specify a valid odata or Redfish property.",
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
37 …"description": "The `AttributeRegistry` schema contains a set of key-value pairs that represent th…
38 …"longDescription": "This resource shall represent an attribute registry for a Redfish implementati…
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
[all …]
/openbmc/docs/designs/
H A Dstate-management-and-external-interfaces.md11 As OpenBMC moves to fully supporting the Redfish protocol, it's important to
17 instance: `redfish/v1/Systems/system/Actions/ComputerSystem.Reset`
19 This support will also map to the existing IPMI Chassis Control command.
23 [phoshor-state-manager][2] implements the xyz.openbmc_project.State.\*
27 and front end Redfish interface, then maps commands to the ResetType object to
28 the appropriate xyz.openbmc_project.State.\* D-Bus interface.
31 interfaces to support more of the Redfish ResetType. Specifically this design is
35 Currently phosphor-state-manager supports the following:
37 - Chassis: On/Off
38 - Host: On/Off/Reboot
[all …]
H A Dredfish-authorization.md1 # Dynamic Redfish Authorization
9 The Redfish authorization subsystem controls which authenticated users have
13 enhance the current implementation in BMCWeb Redfish interface so that OpenBMC
15 Redfish service restart.
19 ### Redfish Authorization Model
21 The Redfish authorization model consists of the privilege model and the
22 operation-to-privilege mapping.
24 In the privilege model, there are fixed set of standard Redfish roles and each
26 `ConfigureManager`, etc). A service may define custom OEM roles (read-only). A
27 service may even allow custom client-defined roles to be created, modified, and
[all …]
H A Dboot-progress.md12 phosphor D-Bus properties, IPMI sensors, PLDM sensors, and Redfish properties to
18 [phosphor-state-manager][1] implements D-Bus properties which track the state of
28 phosphor-state-manager implements some other D-Bus properties that represent the
31 - [xyz.openbmc_project.State.Boot.Progress][3]
32 - [xyz.openbmc_project.State.OperatingSystem.Status][4]
34 These two D-Bus properties are very IPMI-centric. They were defined based on two
41 Redfish represents system state in a variety of ways. The BMC, Chassis, and
43 `State` options which are applicable to Redfish objects. OpenBMC has the
44 following mapping for phosphor-state-manager to the Redfish System
47 - `xyz.openbmc_project.State.Host.HostState.Running` : `Enabled`
[all …]
/openbmc/bmcweb/scripts/
H A Dgenerate_schema_collections.py4 # Parses the Redfish schema to determine what are the top level collection URIs
6 # a map of URIs that contain a top level collection as part of their subtree.
8 # unordered_map. These URIs are need by Redfish Aggregation
16 * This is an auto-generated header which contains definitions
17 * for Redfish DMTF defined schemas.
28 SCRIPT_DIR, "..", "redfish-core", "include", "aggregation_utils.hpp"
34 EDMX = "{http://docs.oasis-open.org/odata/ns/edmx}"
35 EDM = "{http://docs.oasis-open.org/odata/ns/edm}"
42 os.path.join(SCRIPT_DIR, "..", "redfish-core", "schema")
56 # Map xml URIs to their associated namespace
[all …]
/openbmc/bmcweb/redfish-core/lib/
H A Dmetric_report_definition.hpp1 // SPDX-License-Identifier: Apache-2.0
2 // SPDX-FileCopyrightText: Copyright OpenBMC Authors
24 #include <asm-generic/errno.h>
25 #include <systemd/sd-bus.h>
46 #include <map>
57 namespace redfish namespace
267 boost::urls::format("/redfish/v1/TelemetryService/Triggers/{}", id); in getLinkedTriggers()
297 messages::internalError(asyncResp->res); in fillReportDefinition()
306 messages::internalError(asyncResp->res); in fillReportDefinition()
310 asyncResp->res.jsonValue["MetricReportDefinitionType"] = in fillReportDefinition()
[all …]
H A Dsensors.hpp1 // SPDX-License-Identifier: Apache-2.0
2 // SPDX-FileCopyrightText: Copyright OpenBMC Authors
3 // SPDX-FileCopyrightText: Copyright 2018 Intel Corporation
25 #include <asm-generic/errno.h>
43 #include <map>
56 namespace redfish namespace
62 // clang-format off
102 // clang-format on
131 const std::map<std::string, std::string>& uriToDbus)>;
171 if (asyncResp->res.result() == in ~SensorsAsyncResp()
[all …]
H A Dcable.hpp1 // SPDX-License-Identifier: Apache-2.0
2 // SPDX-FileCopyrightText: Copyright OpenBMC Authors
19 #include <asm-generic/errno.h>
34 namespace redfish namespace
93 * @param[in] serviceMap A map to hold Service and corresponding
115 fillCableProperties(asyncResp->res, ec, properties); in getCableProperties()
131 messages::internalError(asyncResp->res); in getCableProperties()
138 asyncResp->res.jsonValue["Status"]["State"] = in getCableProperties()
152 BMCWEB_ROUTE(app, "/redfish/v1/Cables/<str>/") in requestRoutesCable()
153 .privileges(redfish::privileges::getCable) in requestRoutesCable()
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/installed/
H A DAttributeRegistry_v1.xml1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ -->
4 <!--# Redfish Schema: AttributeRegistry v1.3.9 -->
5 <!--# -->
6 <!--# For a detailed change log, see the README file contained in the DSP8010 bundle, -->
7 <!--# available at http://www.dmtf.org/standards/redfish -->
8 <!--# Copyright 2014-2024 DMTF. -->
9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright -->
10 <!--################################################################################ -->
[all …]
H A DPrivileges_v1.xml1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ -->
4 <!--# Redfish Schema: Privileges v1.0.6 -->
5 <!--# -->
6 <!--# For a detailed change log, see the README file contained in the DSP8010 bundle, -->
7 <!--# available at http://www.dmtf.org/standards/redfish -->
8 <!--# Copyright 2014-2024 DMTF. -->
9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright -->
10 <!--################################################################################ -->
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/
H A DAttributeRegistry_v1.xml1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ -->
4 <!--# Redfish Schema: AttributeRegistry v1.3.9 -->
5 <!--# -->
6 <!--# For a detailed change log, see the README file contained in the DSP8010 bundle, -->
7 <!--# available at http://www.dmtf.org/standards/redfish -->
8 <!--# Copyright 2014-2024 DMTF. -->
9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright -->
10 <!--################################################################################ -->
[all …]
H A DPrivileges_v1.xml1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ -->
4 <!--# Redfish Schema: Privileges v1.0.6 -->
5 <!--# -->
6 <!--# For a detailed change log, see the README file contained in the DSP8010 bundle, -->
7 <!--# available at http://www.dmtf.org/standards/redfish -->
8 <!--# Copyright 2014-2024 DMTF. -->
9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright -->
10 <!--################################################################################ -->
[all …]
/openbmc/webui-vue/src/store/modules/SecurityAndAccess/
H A DCertificatesStore.js46 location: '/redfish/v1/AccountService/LDAP/Certificates/',
65 .get('/redfish/v1/CertificateService/CertificateLocations')
71 }) => Certificates.map((certificate) => certificate['@odata.id']),
74 const promises = certificateLocations.map((location) =>
79 const certificates = responses.map(({ data }) => {
104 .map((certificate) => certificate.type)
120 headers: { 'Content-Type': 'application/x-pem-file' },
151 '/redfish/v1/CertificateService/Actions/CertificateService.ReplaceCertificate',
232 '/redfish/v1/CertificateService/Actions/CertificateService.GenerateCSR',
/openbmc/smbios-mdr/tools/
H A Dsst-compare-redfish-os.py4 # the BMC (Redfish) and from the linux driver, and compares them to catch any
6 # Redfish session.
12 # * DMTF's redfish python library. This is available in pip.
13 # * intel-speed-select tool from the kernel source tree
14 # (tools/power/x86/intel-speed-select), and available in the PATH.
22 import redfish
29 # For TPMI-based CPUs, we only care about powerdomain-0
32 match = re.search("powerdomain-(\\d+)", proc)
41 "intel-speed-select",
42 "--debug",
[all …]
/openbmc/intel-ipmi-oem/include/
H A Dme_to_redfish_hooks.hpp8 // http://www.apache.org/licenses/LICENSE-2.0
38 // Maps event byte to human-readable message
46 * @param[in] map - maps EventData2 byte of IPMI Platform Event to decoder
47 * @param[in] selData - IPMI Platform Event
48 * @param[out] eventId - resulting Redfish Event ID
49 * @param[out] args - resulting Redfish Event Parameters
57 std::optional<std::variant<ParserFunc, MessageMap>>>>& map, in genericMessageHook() argument
61 const auto match = map.find(selData.eventData2); in genericMessageHook()
62 if (match == map.end()) in genericMessageHook()
67 eventId = match->second.first; in genericMessageHook()
[all …]
/openbmc/bmcweb/redfish-core/include/utils/
H A Dsensor_utils.hpp1 // SPDX-License-Identifier: Apache-2.0
2 // SPDX-FileCopyrightText: Copyright OpenBMC Authors
37 namespace redfish namespace
111 * D-Bus inventory item associated with one or more sensors.
132 int powerSupplyEfficiencyPercent = -1;
262 * @brief Returns the Redfish State value for the specified inventory item.
263 * @param inventoryItem D-Bus inventory item associated with a sensor.
264 * @param sensorAvailable Boolean representing if D-Bus sensor is marked as
271 if ((inventoryItem != nullptr) && !(inventoryItem->isPresent)) in getState()
285 * @brief Returns the Redfish Health value for the specified sensor.
[all …]
/openbmc/docs/designs/oem/google/
H A Droot_of_trust.md1 # Google Specific APIs - A New Service Root for Google
11 Redfish API does not have a resource type that is similar to Google's Root of
12 Trust (RoT) chips. Google needs APIs that are not in the Redfish standard yet.
13 There are working groups dedicated to bring RoT chips support to the Redfish
23 [SPDM protocol](https://www.dmtf.org/sites/default/files/PMCI_Security-Architecture_12-11-2019.pdf).
29 - Create a new service root of Google specific APIs.
30 - Create a schema for a RootOfTrust resource.
31 - Be able to execute RoT actions (attestation etc) from the API.
39 - Chip type string
40 - Unique Hardware id string
[all …]
/openbmc/intel-ipmi-oem/docs/
H A DIntel_IPMI_Platform_Events.md3 In many cases Manufacturers-specific IPMI Platfrom Events are stored in binary
8 events originating from Intel Management Engine (ME) is used as a case-study.
9 General design of the solution is followed by tailored-down implementation for
14 - **IPMI** - Intelligent Platform Management Interface; standarized binary
16 - **Platform Event** - specific type of IPMI binary payload, used for encoding
17 and sending asynchronous one-way messages to recipient `[1]-29.3`
18 - **ME** - Intel Management Engine, autonomous subsystem used for remote
20 - **Redfish** - modern datacenter management protocol, built around REST
22 - **OpenBMC** - open-source BMC implementation with Redfish-oriented interface
28 between entities in data-center. Recipient is responsible to receive data,
[all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Telemetry/
H A DTrigger.interface.yaml7 - name: Discrete
13 - const
14 - name: TriggerActions
19 - const
20 - name: Persistent
23 - name: Reports
29 - name: Sensors
32 Map of sensors that is monitored within trigger. D-Bus sensor path is
33 used as map's key. Its value is a metadata that is used to store user
34 data about sensor. In Redfish, metadata will be set to endpoint
[all …]
/openbmc/bmcweb/
H A Dmeson.options20 'vm-websocket',
29 'redfish-use-3-digit-messageid',
36 removed Q2-2025''',
47 # 'vm-nbdproxy',
58 description: '''Enable Phosphor REST (D-Bus) APIs. Paths directly map
59 Phosphor D-Bus object paths, for example,
61 https://github.com/openbmc/docs/blob/master/rest-api.md.''',
66 'redfish',
69 description: '''Enable Redfish APIs. Paths are under /redfish/v1/. See
70 https://github.com/openbmc/bmcweb/blob/master/DEVELOPING.md#redfish.''',
[all …]

1234