Home
last modified time | relevance | path

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

123

/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Sensor/
H A DThreshold.events.yaml4 - name: InvalidSensorReading
8 - name: SensorName
12 redfish-mapping: SensorEvent.InvalidSensorReading
14 - name: ReadingAboveLowerCriticalThreshold
18 - name: SensorName
22 - name: ReadingValue
26 - name: Units
30 - name: ThresholdValue
34 redfish-mapping: SensorEvent.ReadingAboveLowerCriticalThreshold
36 - name: ReadingAboveLowerSoftShutdownThreshold
[all …]
/openbmc/docs/designs/
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 …]
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`
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
42 ### Redfish subsection
[all …]
H A Devent-logging.md3 Author: [Patrick Williams][patrick-email] `<stwcx>`
5 [patrick-email]: mailto:patrick@stwcx.xyz
13 There is currently not a consistent end-to-end error and event reporting design
15 primarily using phosphor-logging and one using rsyslog, both of which have gaps
17 end-to-end design handling both errors and tracing events which facilitate
22 ### Redfish LogEntry and Message Registry
24 In Redfish, the [`LogEntry` schema][LogEntry] is used for a range of items that
30 be "DIMM-A0 encountered an uncorrectable ECC error" or "System boot successful".
36 temperature threshold exceeded: ["temperature threshold exceeded"][HPE-Example]
37 and ["Temperature #0x30 Upper Critical going high"][Oracle-Example]. There is
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DPrivilegeRegistry.v1_1_5.json2 "$id": "http://redfish.dmtf.org/schemas/v1/PrivilegeRegistry.v1_1_5.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…
35 "Mapping": { object
37 …"description": "The mapping between a resource type and the relevant privileges that accesses the …
38 …"longDescription": "This type shall describe a mapping between a resource type and the relevant pr…
[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 DAccountService.v1_17_0.json2 "$id": "http://redfish.dmtf.org/schemas/v1/AccountService.v1_17_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 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 DStorage.v1_18_0.json2 "$id": "http://redfish.dmtf.org/schemas/v1/Storage.v1_18_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…
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.",
40 "description": "The available OEM-specific actions for this resource.",
41 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
55 "NonRAID": "Automatically create non-RAID volumes.",
66 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
67 "description": "This property shall specify a valid odata or Redfish property.",
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/
H A DPrivilegeRegistry_v1.xml1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ -->
4 <!--# Redfish Schema: PrivilegeRegistry v1.1.5 -->
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 DTask_v1.xml1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ -->
4 <!--# Redfish Schema: Task v1.7.4 -->
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 DAccountService_v1.xml1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ -->
4 <!--# Redfish Schema: AccountService v1.17.0 -->
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 DExternalAccountProvider_v1.xml1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ -->
4 <!--# Redfish Schema: ExternalAccountProvider v1.8.0 -->
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/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/Leak/
H A DDetector.events.yaml4 - name: LeakDetectedCritical
7 - name: DetectorName
12 redfish-mapping: Environmental.LeakDetectedCritical
14 - name: LeakDetectedWarning
17 - name: DetectorName
22 redfish-mapping: Environmental.LeakDetectedWarning
25 - name: LeakDetectedNormal
27 - name: DetectorName
31 redfish-mapping: Environmental.LeakDetectedNormal
/openbmc/openbmc-test-automation/redfish/account_service/
H A Dtest_redfish_privilege_registry.robot2 Documentation Script to test Redfish privilege registry with various users
11 Suite Teardown Delete Created Redfish Users Except Default Admin
12 Test Teardown Redfish.Logout
31 Verify Redfish Privilege Registry Properties
32 [Documentation] Verify the Redfish Privilege Registry properties.
35 Redfish.Login
38 ${url}= Get Redfish Privilege Registry json URL
39 ${resp}= Redfish.Get ${url}
45 # "Name": "Privilege Mapping array collection",
55 Should Be Equal As Strings ${resp.dict["Name"]} Privilege Mapping array collection
[all …]
/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/schema/oem/openbmc/
H A Dmeson.build1 # Mapping from option key name to schemas that should be installed if that option is enabled
3 'insecure-disable-auth': 'OpenBMCAccountService',
4 'redfish-oem-manager-fan-data': 'OpenBMCManager',
5 'redfish-provisioning-feature': 'OpenBMCComputerSystem',
6 #'vm-nbdproxy': 'OpenBMCVirtualMedia',
13 install_dir: 'share/www/redfish/v1/schema',
18 'json-schema/@0@.v1_0_0.json'.format(schema),
19 install_dir: 'share/www/redfish/v1/JsonSchemas',
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A DAccountService.v1_17_0.json2 "$id": "http://redfish.dmtf.org/schemas/v1/AccountService.v1_17_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 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/bmcweb/scripts/
H A Dparse_registries.py17 * This is an auto-generated header which contains definitions
18 * for Redfish DMTF defined messages.
28 ] = """// SPDX-License-Identifier: Apache-2.0
29 // SPDX-FileCopyrightText: Copyright OpenBMC Authors
37 // clang-format off
39 namespace redfish::registries::{}
48 os.path.join(SCRIPT_DIR, "..", "redfish-core", "include", "registries")
60 ) -> RegistryInfo:
61 url = "https://redfish.dmtf.org/registries/{}".format(dmtf_name)
69 def openbmc_local_getter() -> RegistryInfo:
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/installed/
H A DTask_v1.xml1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ -->
4 <!--# Redfish Schema: Task v1.7.4 -->
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 DAccountService_v1.xml1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ -->
4 <!-
[all...]
/openbmc/docs/architecture/
H A DLED-architecture.md4 OpenBMC [LED Architecture][led d-bus readme] document. LED group management is
8 ## D-Bus
29 curl -b cjar -k -X PUT -H "Content-Type: application/json" -d '{"data": 1}' \
33 ## REDFISH section in LED Support for OpenBMC
37 Starting with Redfish v2020.3, Redfish resources have
41 All applicable Inventory D-Bus objects would have a forward association mapping
42 to LED Group D-Bus object, namely:
45 - identify_led_group
48 All applicable LED Group D-Bus objects would have an association mapping to
49 inventory D-Bus object, namely:
[all …]
H A Duser-management.md1 # User Management - OpenBMC - Design document
6 user-management components. The implementation detail is beyond the scope of
11 1. Use common user-management (e.g. phosphor-user-manager) rather than
12 application-based user-management. Especially, avoid IPMI based
13 user-management.
14 2. For security reasons, avoid transmitting passwords over any D-Bus API.
17 relying on a D-Bus API-based approach.
20 13.19-13.33 inclusive for more details), new PAM module (e.g. pam-ipmi
22 pam-unix), which will store the password in encrypted form. Implementation
26 user-management (e.g. phosphor-user-manager), whereas individual user-related
[all …]

123