| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | MessageRegistryFile.v1_1_5.json | 37 "description": "The location information for a registry file.",
38 … "longDescription": "This type shall contain the location information for a registry file.",
55 …"description": "If the service hosts the registry in an archive file, the name of the file within …
56 …cription": "This property shall contain the file name of the individual registry file within the a…
61 …"description": "If the registry is hosted on the service in an archive file, the link to the archi…
63 …registry file, which can be retrieved using the Redfish protocol and authentication methods. This…
68 "description": "The language code for the registry file.",
74 … "description": "The link to publicly available (canonical) URI for the registry.",
76 …specifies the canonical location of the registry file. This property shall be used for only indiv…
81 "description": "The link to locally available URI for the registry.",
[all …]
|
| H A D | MessageRegistry.v1_6_3.json | 37 …dicate the events, specified by message keys for other messages in this registry, that are cleared…
55 …dicates whether all logged events containing messages from this message registry are cleared when …
56 …ndicate whether all logged events containing messages from this message registry are cleared when …
86 …essage keys. This property shall contain message keys, without message registry names and version…
108 … "description": "This type represents how a message is defined within the message registry.",
109 … "longDescription": "The type shall represent how a message is defined within a message registry.",
153 …dicate the events, specified by message keys for other messages in this registry, that are cleared…
159 …sages are likely to be removed in a future major version of the message registry. The `ReplacedBy…
191 …geRegistryPrefix.MessageKey` formatted values that describe the message registry and message key u…
213 … the message. Services can replace the severity defined in the message registry with a value more…
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | MessageRegistryFile.v1_1_5.json | 37 "description": "The location information for a registry file.",
38 … "longDescription": "This type shall contain the location information for a registry file.",
55 …"description": "If the service hosts the registry in an archive file, the name of the file within …
56 …cription": "This property shall contain the file name of the individual registry file within the a…
61 …"description": "If the registry is hosted on the service in an archive file, the link to the archi…
63 …registry file, which can be retrieved using the Redfish protocol and authentication methods. This…
68 "description": "The language code for the registry file.",
74 … "description": "The link to publicly available (canonical) URI for the registry.",
76 …specifies the canonical location of the registry file. This property shall be used for only indiv…
81 "description": "The link to locally available URI for the registry.",
[all …]
|
| H A D | MessageRegistry.v1_6_3.json | 37 …dicate the events, specified by message keys for other messages in this registry, that are cleared…
55 …dicates whether all logged events containing messages from this message registry are cleared when …
56 …ndicate whether all logged events containing messages from this message registry are cleared when …
86 …essage keys. This property shall contain message keys, without message registry names and version…
108 … "description": "This type represents how a message is defined within the message registry.",
109 … "longDescription": "The type shall represent how a message is defined within a message registry.",
153 …dicate the events, specified by message keys for other messages in this registry, that are cleared…
159 …sages are likely to be removed in a future major version of the message registry. The `ReplacedBy…
191 …geRegistryPrefix.MessageKey` formatted values that describe the message registry and message key u…
213 … the message. Services can replace the severity defined in the message registry with a value more…
[all …]
|
| /openbmc/phosphor-webui/ |
| H A D | package-lock.json | 9 "resolved": "https://registry.npmjs.org/@babel/code-frame/-/code-frame-7.8.3.tgz",
18 "resolved": "https://registry.npmjs.org/@babel/compat-data/-/compat-data-7.9.0.tgz",
29 "resolved": "https://registry.npmjs.org/@babel/core/-/core-7.9.0.tgz",
53 … "resolved": "https://registry.npmjs.org/convert-source-map/-/convert-source-map-1.7.0.tgz",
62 "resolved": "https://registry.npmjs.org/json5/-/json5-2.1.3.tgz",
71 "resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz",
79 "resolved": "https://registry.npmjs.org/@babel/generator/-/generator-7.9.5.tgz",
91 …"resolved": "https://registry.npmjs.org/@babel/helper-annotate-as-pure/-/helper-annotate-as-pure-7…
100 …"resolved": "https://registry.npmjs.org/@babel/helper-builder-binary-assignment-operator-visitor/-…
110 …"resolved": "https://registry.npmjs.org/@babel/helper-compilation-targets/-/helper-compilation-tar…
[all …]
|
| /openbmc/openbmc/poky/meta/lib/oeqa/core/decorator/ |
| H A D | depends.py | 13 def _add_depends(registry, case, depends): argument
29 if not case_id in registry:
30 registry[case_id] = []
31 if not depend_id in registry[case_id]:
32 registry[case_id].append(depend_id)
83 def bind(self, registry, case): argument
84 super(OETestDepends, self).bind(registry, case)
85 if not registry.get('depends'):
86 registry['depends'] = {}
87 _add_depends(registry['depends'], case, self.depends)
[all …]
|
| /openbmc/phosphor-logging/extensions/openpower-pels/ |
| H A D | registry.hpp | 39 * @brief Represents the Documentation related fields in the message registry.
41 * an error is looked up in the registry.
67 * @brief Represents the SRC related fields in the message registry.
69 * an error is looked up in the registry.
103 * message registry: "AdditionalDataPropSource" and "Description"
133 * @brief Represents a message registry entry, which is used for creating a
226 * @class Registry
228 * This class wraps the message registry JSON data and allows one to find
229 * the message registry entry pertaining to the error name.
231 * So that new registry files can easily be tested, the code will look for
[all …]
|
| H A D | registry.cpp | 16 #include "registry.hpp"
49 lg2::error("Invalid subsystem name used in message registry: {SUBSYS}", in getSubsystem()
52 throw std::runtime_error("Invalid subsystem used in message registry"); in getSubsystem()
64 lg2::error("Invalid severity name used in message registry: {SEV}", in getSeverity()
67 throw std::runtime_error("Invalid severity used in message registry"); in getSeverity()
120 "Invalid action flag name used in message registry: {FLAG}", in getActionFlags()
124 "Invalid action flag used in message registry"); in getActionFlags()
138 lg2::error("Invalid event type used in message registry: {TYPE}", in getEventType()
141 throw std::runtime_error("Invalid event type used in message registry"); in getEventType()
151 lg2::error("Invalid event scope used in registry: {SCOPE}", "SCOPE", in getEventScope()
[all …]
|
| H A D | src.hpp | 8 #include "registry.hpp"
92 * Creates the section with data from the PEL message registry entry for
96 * @param[in] regEntry - The message registry entry for this event log
109 * Creates the section with data from the PEL message registry entry for
113 * @param[in] regEntry - The message registry entry for this event log
230 * This comes from a field in the message registry for BMC
259 * @param[in] registry - Registry object reference
264 std::optional<std::string> getJSON(message::Registry& registry,
270 * @param[in] registry - Registry object
272 * @param[in] toCache - boolean to cache registry in memory, default=false
[all …]
|
| H A D | setup.py | 6 # Builds the message registry and other data files into a python package
8 # Copy the msg registry and comp IDs files into the subdir with
10 # ../site-packages/pel_registry/ instead of site-packages/registry.
14 os.path.join(this_dir, "registry/message_registry.json"), target_dir
17 os.path.join(this_dir, "registry/O_component_ids.json"), target_dir
20 os.path.join(this_dir, "registry/B_component_ids.json"), target_dir
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | MessageRegistryFile_v1.xml | 34 …registry file locator resource. This referenced registry file can be any type of registry, such a…
35 …<Annotation Term="OData.LongDescription" String="This resource shall represent the registry file l…
70 <Property Name="Registry" Type="Edm.String" Nullable="false">
72 …registry name and its major and minor versions. This registry can be any type of registry, such a…
73 …registry name and it major and minor versions, as defined by the Redfish Specification. This regi…
77 … <Annotation Term="OData.Description" String="The location information for this registry file."/>
78 …escription" String="This property shall contain the location information for this registry file."/>
85 … <Annotation Term="OData.Description" String="The location information for a registry file."/>
86 …a.LongDescription" String="This type shall contain the location information for a registry file."/>
89 <Annotation Term="OData.Description" String="The language code for the registry file."/>
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/installed/ |
| H A D | MessageRegistryFile_v1.xml | 34 …registry file locator resource. This referenced registry file can be any type of registry, such a…
35 …<Annotation Term="OData.LongDescription" String="This resource shall represent the registry file l…
70 <Property Name="Registry" Type="Edm.String" Nullable="false">
72 …registry name and its major and minor versions. This registry can be any type of registry, such a…
73 …registry name and it major and minor versions, as defined by the Redfish Specification. This regi…
77 … <Annotation Term="OData.Description" String="The location information for this registry file."/>
78 …escription" String="This property shall contain the location information for this registry file."/>
85 … <Annotation Term="OData.Description" String="The location information for a registry file."/>
86 …a.LongDescription" String="This type shall contain the location information for a registry file."/>
89 <Annotation Term="OData.Description" String="The language code for the registry file."/>
[all …]
|
| /openbmc/openbmc/poky/meta/lib/oe/ |
| H A D | classutils.py | 8 """Give each ClassRegistry their own registry"""
10 cls.registry = {}
14 """Maintain a registry of classes, indexed by name.
19 The name in the registry can be overridden via the 'name' attribute of the
24 control over whether the class will be added to the registry (e.g. to keep
25 abstract base classes out of the registry)."""
39 cls.registry[cls.name] = cls
43 return sorted(list(tcls.registry.values()),
47 for key in cls.registry.keys():
48 if cls.registry[key] is cls:
[all …]
|
| /openbmc/webui-vue/ |
| H A D | package-lock.json | 81 "resolved": "https://registry.npmjs.org/@achrinza/node-ipc/-/node-ipc-9.2.9.tgz",
106 "resolved": "https://registry.npmjs.org/@babel/code-frame/-/code-frame-7.24.7.tgz",
118 "resolved": "https://registry.npmjs.org/@babel/compat-data/-/compat-data-7.24.7.tgz",
154 "resolved": "https://registry.npmjs.org/@babel/generator/-/generator-7.24.7.tgz",
168 …"resolved": "https://registry.npmjs.org/@babel/helper-annotate-as-pure/-/helper-annotate-as-pure-7…
180 …"resolved": "https://registry.npmjs.org/@babel/helper-builder-binary-assignment-operator-visitor/-…
193 …"resolved": "https://registry.npmjs.org/@babel/helper-compilation-targets/-/helper-compilation-tar…
208 …"resolved": "https://registry.npmjs.org/@babel/helper-create-class-features-plugin/-/helper-create…
231 …"resolved": "https://registry.npmjs.org/@babel/helper-create-regexp-features-plugin/-/helper-creat…
248 …"resolved": "https://registry.npmjs.org/@babel/helper-define-polyfill-provider/-/helper-define-pol…
[all …]
|
| /openbmc/phosphor-logging/extensions/openpower-pels/registry/tools/ |
| H A D | validate_registry.py | 8 Validates the PEL message registry JSON, which includes checking it against
16 Check that there aren't any message registry entries with the same
20 registry_json: The message registry JSON
33 Check that there aren't any message registry entries with the same
36 registry_json: The message registry JSON
57 registry_json: The message registry JSON
87 registry_json: The message registry JSON
113 def validate_schema(registry, schema): argument
117 registry: Path of the file containing the registry JSON
122 with open(registry) as registry_handle:
[all …]
|
| /openbmc/qemu/rust/ |
| H A D | Cargo.lock | 8 source = "registry+https://github.com/rust-lang/crates.io-index"
14 source = "registry+https://github.com/rust-lang/crates.io-index"
24 source = "registry+https://github.com/rust-lang/crates.io-index"
37 source = "registry+https://github.com/rust-lang/crates.io-index"
43 source = "registry+https://github.com/rust-lang/crates.io-index"
62 source = "registry+https://github.com/rust-lang/crates.io-index"
74 source = "registry+https://github.com/rust-lang/crates.io-index"
85 source = "registry+https://github.com/rust-lang/crates.io-index"
111 source = "registry+https://github.com/rust-lang/crates.io-index"
120 source = "registry+https://github.com/rust-lang/crates.io-index"
[all …]
|
| /openbmc/bmcweb/redfish-core/lib/ |
| H A D | message_registries.hpp | 77 const std::string& registry) in handleMessageRoutesMessageRegistryFileGet() argument
85 registries::getRegistryHeaderAndUrlFromPrefix(registry); in handleMessageRoutesMessageRegistryFileGet()
90 registry); in handleMessageRoutesMessageRegistryFileGet()
93 if (registry == "OpenBMC") in handleMessageRoutesMessageRegistryFileGet()
101 boost::urls::format("/redfish/v1/Registries/{}", registry); in handleMessageRoutesMessageRegistryFileGet()
104 asyncResp->res.jsonValue["Name"] = registry + " Message Registry File"; in handleMessageRoutesMessageRegistryFileGet()
106 dmtf + registry + " Message Registry File Location"; in handleMessageRoutesMessageRegistryFileGet()
108 asyncResp->res.jsonValue["Registry"] = in handleMessageRoutesMessageRegistryFileGet()
118 location["Uri"] = "/redfish/v1/Registries/" + registry + "/" + registry; in handleMessageRoutesMessageRegistryFileGet()
140 const std::string& registry, const std::string& registryMatch) in handleMessageRegistryGet() argument
[all …]
|
| /openbmc/docs/designs/ |
| H A D | event-logging.md | 22 ### Redfish LogEntry and Message Registry
42 versioning, Redfish has Message Registries. A message registry is a versioned
45 reference][Registry-Example] from the DMTF gives this example:
79 `MessageArgs` to the placeholders from the `Message` field in the registry.
80 System management software can rely on the message registry (referenced from the
89 with the [message registry][registry-example] advertised by `bmcweb`. Some
99 [Registry-Example]:
105 [registry-example]:
168 Registry. This makes the events of limited utility for consumption by system
185 Message Registry and the reporting application. It also requires every
[all …]
|
| /openbmc/bmcweb/scripts/ |
| H A D | parse_registries.py | 19 * DO NOT modify this registry outside of running the
22 * should be first pushed to the relevant registry in the DMTF
96 with open(file, "w") as registry:
99 registry.write(REGISTRY_HEADER.format(namespace))
100 # Parse the Registry header info
101 registry.write(
117 "constexpr std::array registry =\n"
127 registry.write(
142 registry.write(
145 registry.write("\n },\n")
[all …]
|
| /openbmc/bmcweb/redfish-core/include/ |
| H A D | event_matches_filter.hpp | 75 std::string registry; in eventMatchesFilter() local
77 getRegistryAndMessageKey(*messageId, registry, messageKey); in eventMatchesFilter()
79 auto obj = std::ranges::find(userSub.registryPrefixes, registry); in eventMatchesFilter()
129 std::string registry; in eventMatchesFilter() local
131 getRegistryAndMessageKey(*messageId, registry, messageKey); in eventMatchesFilter()
133 BMCWEB_LOG_DEBUG("extracted registry {}", registry); in eventMatchesFilter()
137 userSub.registryMsgIds, std::format("{}.{}", registry, messageKey)); in eventMatchesFilter()
140 BMCWEB_LOG_DEBUG("did not find registry {} in registryMsgIds", in eventMatchesFilter()
141 registry); in eventMatchesFilter()
|
| H A D | registries_selector.hpp | 59 return {base::registry}; in getRegistryFromPrefix()
63 return {heartbeat_event::registry}; in getRegistryFromPrefix()
67 return {openbmc::registry}; in getRegistryFromPrefix()
71 return {resource_event::registry}; in getRegistryFromPrefix()
75 return {task_event::registry}; in getRegistryFromPrefix()
79 return {telemetry::registry}; in getRegistryFromPrefix()
81 return {openbmc::registry}; in getRegistryFromPrefix()
|
| /openbmc/phosphor-logging/test/openpower-pels/ |
| H A D | registry_test.cpp | 16 #include "extensions/openpower-pels/registry.hpp"
200 fs::path path = regDir / "registry.json"; in writeData()
214 Registry registry{path}; in TEST_F() local
216 auto entry = registry.lookup("foo", LookupType::name); in TEST_F()
223 Registry registry{path}; in TEST_F() local
225 auto entry = registry.lookup("xyz.openbmc_project.Power.OverVoltage", in TEST_F()
284 entry = registry.lookup("0x2333", LookupType::reasonCode); in TEST_F()
288 entry = registry.lookup("org.open_power.PHAL.Info.ClockDailyLog", in TEST_F()
299 Registry registry{path}; in TEST_F() local
302 registry.lookup("xyz.openbmc_project.Power.Fault", LookupType::name); in TEST_F()
[all …]
|
| /openbmc/phosphor-logging/extensions/openpower-pels/registry/ |
| H A D | README.md | 1 # Platform Event Log Message Registry
4 phosphor-logging using a message registry that provides the PEL related fields.
5 The message registry is a JSON file.
10 - [Message Registry](#message-registry-fields)
26 Component IDs are specified in the message registry either as the upper byte of
37 ## Message Registry Fields
39 The message registry schema is [here](schema/schema.json), and the message
40 registry itself is [here](message_registry.json). The schema will be validated
43 In the message registry, there are fields for specifying:
47 This is the key into the message registry, and is the Message property of the
[all …]
|
| /openbmc/openbmc-test-automation/redfish/account_service/ |
| H A D | test_redfish_privilege_registry.robot | 2 Documentation Script to test Redfish privilege registry with various users
31 Verify Redfish Privilege Registry Properties
32 [Documentation] Verify the Redfish Privilege Registry properties.
37 # Get the complete Privilege Registry URL
38 ${url}= Get Redfish Privilege Registry json URL
42 # Verify the Privilege Registry Resource.
62 Verify Redfish Privilege Registry Mappings Properties For Account Service
63 [Documentation] Verify Privilege Registry Account Service Mappings resource properties.
66 # Below is the mapping for Redfish Privilege Registry property for
105 # Get the complete Privilege Registry URL.
[all …]
|
| /openbmc/openbmc/meta-ampere/meta-common/recipes-ampere/platform/ampere-utils/ |
| H A D | ampere_add_redfishevent.sh | 3 registry=$1
6 if [ -z "$registry" ]; then
8 echo " $0 <redfish registry> <argument>"
15 echo "logger does not support the journald option. Skip log events for $registry $msgarg"
24 REDFISH_MESSAGE_ID=$registry
|