Home
last modified time | relevance | path

Searched +full:json +full:- +full:schema (Results 1 – 25 of 815) sorted by relevance

12345678910>>...33

/openbmc/linux/Documentation/devicetree/bindings/
H A Dwriting-schema.rst1 .. SPDX-License-Identifier: GPL-2.0
3 Writing Devicetree Bindings in json-schema
6 Devicetree bindings are written using json-schema vocabulary. Schema files are
7 written in a JSON-compatible subset of YAML. YAML is used instead of JSON as it
11 Also see :ref:`example-schema`.
13 Schema Contents
14 ---------------
16 Each schema doc is a structured json-schema which is defined by a set of
17 top-level properties. Generally, there is one binding defined per file. The
18 top-level json-schema properties used are:
[all …]
/openbmc/phosphor-logging/extensions/openpower-pels/registry/tools/
H A Dvalidate_registry.py4 import json
8 Validates the PEL message registry JSON, which includes checking it against
9 a JSON schema using the jsonschema module as well as doing some extra checks
10 that can't be encoded in the schema.
20 registry_json: The message registry JSON
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
115 Validates the passed in JSON against the passed in schema JSON
[all …]
/openbmc/bmcweb/redfish-core/lib/
H A Dredfish_v1.hpp1 // SPDX-License-Identifier: Apache-2.0
2 // SPDX-FileCopyrightText: Copyright OpenBMC Authors
42 asyncResp->res.jsonValue["v1"] = "/redfish/v1/"; in redfishGet()
49 asyncResp->res.addHeader(boost::beast::http::field::allow, ""); in redfish404()
64 messages::resourceNotFound(asyncResp->res, "", name); in redfish404()
79 asyncResp->res.result(boost::beast::http::status::method_not_allowed); in redfish405()
82 messages::resourceCannotBeDeleted(asyncResp->res); in redfish405()
86 messages::operationNotAllowed(asyncResp->re in redfish405()
97 nlohmann::json& json = asyncResp->res.jsonValue; jsonSchemaIndexGet() local
133 jsonSchemaGet(App & app,const crow::Request & req,const std::shared_ptr<bmcweb::AsyncResp> & asyncResp,const std::string & schema) jsonSchemaGet() argument
163 nlohmann::json& json = asyncResp->res.jsonValue; jsonSchemaGet() local
197 jsonSchemaGetFile(const crow::Request &,const std::shared_ptr<bmcweb::AsyncResp> & asyncResp,const std::string & schema,const std::string & schemaFile) jsonSchemaGetFile() argument
[all...]
/openbmc/qemu/storage-daemon/qapi/
H A Dqapi-schema.json1 # -*- Mode: Python -*-
4 # Note that modules are shared with the QEMU main schema under the assumption
5 # that the storage daemon schema is a subset of the main schema. For the shared
7 # from the main schema.
9 # If you wish to extend the storage daemon schema to contain things that are
10 # not in the main schema, be aware that array types of types defined in shared
12 # in the main schema. Therefore, if you use such arrays, you may need to define
13 # the array type in the main schema, even if it is unused outside of the
22 # For locating a particular item, please see the `qapi-qsd-index`.
26 # .. qmp-example::
[all …]
/openbmc/entity-manager/src/entity_manager/
H A Dconfiguration.cpp4 #include "phosphor-logging/lg2.hpp"
7 #include <nlohmann/json.hpp>
9 #include <valijson/schema.hpp>
23 bool writeJsonFiles(const nlohmann::json& systemConfiguration) in writeJsonFiles()
36 // reads json files out of the filesystem in loadConfigurations()
37 bool loadConfigurations(std::list<nlohmann::json>& configurations) in loadConfigurations()
46 R"(.*\.json)", jsonPaths)) in loadConfigurations()
58 << "Cannot open schema file, cannot validate JSON, exiting\n\n"; in loadConfigurations()
62 nlohmann::json schem in loadConfigurations()
59 nlohmann::json schema = loadConfigurations() local
129 valijson::Schema schema; validateJson() local
[all...]
/openbmc/entity-manager/schemas/
H A Dexposes_record.json2 "$schema": "http://json-schema.org/draft-07/schema#",
7 "$ref": "ibm.json#/$defs/PowerModeProperties"
10 "$ref": "ibm.json#/$defs/IBMCompatibleSystem"
13 "$ref": "ibm.json#/$defs/IBMCFFPSConnector"
16 "$ref": "intel.json#/$defs/IntelFanConnector"
19 "$ref": "mctp.json#/$defs/MCTPI2CTarget"
22 "$ref": "mctp.json#/$defs/MCTPI3CTarget"
25 "$ref": "pid.json#/$defs/Pid"
28 "$ref": "pid_zone.json#/$defs/PidZone"
31 "$ref": "satellite_controller.json#/$defs/SatelliteController"
[all …]
H A Dglobal.json2 "$schema": "http://json-schema.org/draft-07/schema#",
6 …"description": "The schema for an entity manager configuration. An entity manager configuration de…
14 …"description": "The schema for the exposes property. The exposes property must be an array where e…
17 "$ref": "exposes_record.json#/$defs/EMExposesElement"
24 …"description": "The schema for the name property. The name property identifies the configuration.…
28 …"description": "The schema for an entity manager probe statement. Probes can be a single string or…
43 …"description": "The schema for the type property. The type property identifies the type of the con…
54 "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Common/UUID"
57 "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Inventory/Decorator/Asset"
60 … "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Inventory/Decorator/AssetTag"
[all …]
H A DREADME.md1 # Entity manager configuration file schema
3 Entity manager configuration files are JSON documents and can be validated with
4 a [JSON schema][1]. This document provides an overview of the general structure
8 configurations. This provides flexibility for system designers - the
11 most schema describes a single object or an array of objects.
14 entity manager configuration file and schema file names must be
30 supported types, consult the schema (global.json).
37 interfaces listed in openbmc-dbus.json will be added on
49 Each exposes element has its own schema which is outlined by the subschemas in
50 the schemas directory. Each schema must require a type and name (not to be
[all …]
/openbmc/phosphor-power/phosphor-regulators/tools/
H A Dvalidate-regulators-config.py4 import json
11 Validates the phosphor-regulators configuration file. Checks it against a JSON
12 schema as well as doing some extra checks that can't be encoded in the schema.
22 Finds all occurrences of a key within the specified JSON element and its
24 To search the entire configuration file, pass the root JSON element
25 json_element: JSON element within the config file.
48 config_json: Configuration file JSON
59 config_json: Configuration file JSON
72 config_json: Configuration file JSON
110 config_json: Configuration file JSON
[all …]
/openbmc/openpower-hw-diags/test/
H A Dtest-util-data-file.cpp10 using json = nlohmann::json; typedef
18 auto regexPattern = R"(openpower\-hw\-diags\-.*)"; in TEST()
56 // The json object that is used as schema for other json objects. in TEST()
58 // ./analyzer/ras-data/schema/ras-data-schema-v01.json in TEST()
59 json schema_obj = R"({ in TEST()
60 "$schema": "https://json-schema.org/draft/2020-12/schema", in TEST()
61 "title": "RAS Data schema for openpower-hw-diags", in TEST()
69 "pattern": "^[0-9A-Fa-f]{8}$" in TEST()
78 // The json objects
80 // ./analyzer/ras-data/data/ras-data-p10-20.json
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A DJsonSchemaFile.v1_1_5.json2 "$id": "http://redfish.dmtf.org/schemas/v1/JsonSchemaFile.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_]*$": {
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 …ription": "The `JsonSchemaFile` schema contains the properties that describe the locations, as URI…
38 …"longDescription": "This resource shall represent the schema file locator resource for a Redfish i…
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
55 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/context"
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DJsonSchemaFile.v1_1_5.json2 "$id": "http://redfish.dmtf.org/schemas/v1/JsonSchemaFile.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_]*$": {
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 …ription": "The `JsonSchemaFile` schema contains the properties that describe the locations, as URI…
38 …"longDescription": "This resource shall represent the schema file locator resource for a Redfish i…
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
55 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/context"
[all …]
H A DMediaControllerCollection.json2 "$id": "http://redfish.dmtf.org/schemas/v1/MediaControllerCollection.json",
4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
10 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/idRef"
17 … "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
32 … "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/context"
35 … "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/etag"
38 … "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/id"
41 … "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/type"
46 … "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Description"
[all …]
/openbmc/libcper/specification/json/
H A Dcper-json.json2 "$id": "cper-json",
3 "$schema": "https://json-schema.org/draft/2020-12/schema",
4 …"description": "JSON Schema for the CPER-JSON format, as described in the CPER-JSON specification …
7 { "$ref": "./cper-json-full-log.json" },
8 { "$ref": "./cper-json-section-log.json" }
H A Dcper-json-full-log.json2 "$id": "cper-json-full-log",
3 "$schema": "https://json-schema.org/draft/2020-12/schema",
5 … "A Common Platform Error Record as defined in UEFI Specification Appendix N represented as JSON.",
10 "$ref": "./cper-json-header.json"
16 "$ref": "./cper-json-section-descriptor.json"
29 "$ref": "./sections/cper-generic-processor.json"
32 "$ref": "./sections/cper-ia32x64-processor.json"
35 "$ref": "./sections/cper-arm-processor.json"
38 "$ref": "./sections/cper-memory.json"
41 "$ref": "./sections/cper-memory2.json"
[all …]
/openbmc/bmcweb/scripts/csdl-to-json-converter/
H A DREADME.md1 # Generating Json schema for OEM schemas
3 The config in this directory is for utilizing the DMTF json generation script
10 …-Tools/csdl-to-json-convertor/csdl-to-json.py --input ~/bmcweb/redfish-core/schema/oem/openbmc/csd…
14 https://github.com/DMTF/Redfish-Tools/blob/main/csdl-to-json-convertor/csdl-to-json.py
H A Dopenbmc-config.json3 "RedfishSchema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
4 "ODataSchema": "http://redfish.dmtf.org/schemas/v1/odata-v4.json",
5 …ion": "https://github.com/openbmc/bmcweb/tree/master/redfish-core/schema/oem/openbmc/json-schema/",
6 …ion": "https://github.com/openbmc/bmcweb/tree/master/redfish-core/schema/oem/openbmc/json-schema/",
/openbmc/qemu/docs/devel/
H A Dqapi-code-gen.rst7 Copyright (C) 2012-2016 Red Hat, Inc.
10 later. See the COPYING file in the top-level directory.
17 QAPI is a native C API within QEMU which provides management-level
19 users/processes, this interface is made available by a JSON-based wire
22 The remainder of this document uses "Client JSON Protocol" when
25 To map between Client JSON Protocol interfaces and the native C API,
26 we generate C code from a QAPI schema. This document describes the
27 QAPI schema language, and how it gets mapped to the Client JSON
29 Client JSON Protocol compatibility.
32 The QAPI schema language
[all …]
/openbmc/bmcweb/redfish-core/schema/oem/openbmc/json-schema/
H A DOpenBMCComputerSystem.v1_0_0.json2 …ub.com/openbmc/bmcweb/tree/master/redfish-core/schema/oem/openbmc/json-schema/OpenBMCComputerSyste…
3 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
10 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
27 …github.com/openbmc/bmcweb/tree/master/redfish-core/schema/oem/openbmc/json-schema/OpenBMCComputerS…
53 …"ProvisionedAndLocked": "Platform firmware is provisioned and locked. So re-provisioning is not al…
54 …"ProvisionedButNotLocked": "Platform firmware is provisioned but not locked. So re-provisioning is…
62 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
79 …github.com/openbmc/bmcweb/tree/master/redfish-core/schema/oem/openbmc/json-schema/OpenBMCComputerS…
93 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
/openbmc/openpower-hw-diags/analyzer/ras-data/
H A Dmeson.build5 'data/ras-data-explorer-11.json',
6 'data/ras-data-explorer-20.json',
7 'data/ras-data-odyssey-10.json',
8 'data/ras-data-p10-10.json',
9 'data/ras-data-p10-20.json',
12 install_data(ras_data_files, install_dir: join_paths(package_dir, 'ras-data'))
14 # Install the RAS data schema
16 ras_data_schema = files('schema/ras-data-schema-v02.json')
18 install_data(ras_data_schema, install_dir: join_paths(package_dir, 'schema'))
/openbmc/qemu/tests/qapi-schema/
H A Dmeson.build3 test_env.set('PYTHONIOENCODING', 'utf-8')
6 'alternate-any.json',
7 'alternate-array.json',
8 'alternate-base.json',
9 'alternate-branch-if-invalid.json',
10 'alternate-clash.json',
11 'alternate-conflict-dict.json',
12 'alternate-conflict-enum-bool.json',
13 'alternate-conflict-enum-int.json',
14 'alternate-conflict-lists.json',
[all …]
/openbmc/phosphor-logging/tools/
H A Dgen-eventfilter.py4 import json
13 # Determine the script's directory to find the schema file relative to it.
16 SCRIPT_DIR, "phosphor-logging", "schemas", "eventfilter.schema.yaml"
19 SCRIPT_DIR, "phosphor-logging", "templates", "event-filter.cpp.mako"
23 def main() -> int:
25 Validates a JSON filter file against the eventfilter schema.
28 description="Validate an event filter JSON file against the schema."
33 help="Path to the JSON filter file to validate.",
38 filter_data = json.load(f)
43 jsonschema.validate(instance=filter_data, schema=schema_data)
/openbmc/phosphor-logging/extensions/openpower-pels/registry/
H A DREADME.md4 phosphor-logging using a message registry that provides the PEL related fields.
5 The message registry is a JSON file.
9 - [Component IDs](#component-ids)
10 - [Message Registry](#message-registry-fields)
11 - [Modifying and Testing](#modifying-and-testing)
30 Component IDs will be unique on a per-repository basis for errors unique to that
33 [available](O_component_ids.json). That file can used by PEL parsers to display
39 The [message registry schema](schema/schema.json) and the
40 [message registry](message_registry.json) is available. The schema will be
51 ```json
[all …]
/openbmc/openbmc/meta-phosphor/recipes-phosphor/interfaces/
H A Dredfish-schema-pack_2024.4.bb1 LICENSE = "BSD-3-Clause"
4 SRC_URI = "git://github.com/DMTF/Redfish-Publications;branch=main;protocol=https"
15 cat > ${WORKDIR}/redfish-schema-pack.pc <<EOF
17 schema_dir=${DOLLAR}{prefix}/share/redfish-schema-pack
19 Name: redfish-schema-pack
20 Description: DMTF Redfish Schema Pack
26 install -d ${D}${datadir}/redfish-schema-pack/
27 for f in csdl:xml openapi:yaml json-schema:json registries:json; do
30 install -d ${D}${datadir}/redfish-schema-pack/$PATHSEG
31 cp -R --no-dereference --preserve=mode,links -v ${S}/$PATHSEG/*.$FILETYPE \
[all …]
/openbmc/libcper/specification/json/sections/
H A Dcper-generic-dmar.json2 "$schema": "https://json-schema.org/draft/2020-12/schema",
43 "$ref": "./common/cper-json-nvp.json"
48 "$ref": "./common/cper-json-nvp.json"
52 "description": "Either VT-d or IOMMU",
53 "$ref": "./common/cper-json-nvp.json"
57 "description": "The 64-bit device virtual address in the faulted DMA request"

12345678910>>...33