Update symlinks for 2024.1Wrote a quick bash script to update these symlinks.These are versioned out in json schema directory[1].The symlinks don't work without this update.[1]: https://githu
Update symlinks for 2024.1Wrote a quick bash script to update these symlinks.These are versioned out in json schema directory[1].The symlinks don't work without this update.[1]: https://github.com/openbmc/bmcweb/tree/master/redfish-core/schema/dmtf/json-schemaBefore:cat static/redfish/v1/JsonSchemas/redfish-error/redfish-error.jsoncat: static/redfish/v1/JsonSchemas/redfish-error/redfish-error.json: Nosuch file or directoryf2a8e57ede74a8252100b2281e3f4d170aa69391 pulled in 2024.1 but did notupdate these links. Long term update_schemas.py should do this. Ifigured fix it first, then add update_schemas.py support.Tested: Cat a few of these links. They appear to work.Change-Id: Ibe55ab453775476b7a3d5e2fe79b3faaf0d45533Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
show more ...
Add symlinks to folderNow that we have the schemas moved, add symlinks back to the schemasthat we use, so that they will be installed correctly.The meson option of follow_symlinks: true is added
Add symlinks to folderNow that we have the schemas moved, add symlinks back to the schemasthat we use, so that they will be installed correctly.The meson option of follow_symlinks: true is added to suppress awarning about potential change in behavior in meson in the future.Change-Id: Ie24536ca04038d8137818c201d9411b95361b14fSigned-off-by: Ed Tanous <ed@tanous.net>
Move existing schemas into foldersReorganize the existing schemas into folders under redfish core.The existing schema system has some problems:1. It's hard to add new schemas2. We have to rerun
Move existing schemas into foldersReorganize the existing schemas into folders under redfish core.The existing schema system has some problems:1. It's hard to add new schemas2. We have to rerun the script any time we want to change what schemas we use.3. Adding schemas optionally takes effortIn an effort to combat this, this patchset moves all the existingschemas into folders that represent their namespace namesdmtf/csdl represents the CSDL that dmtf publishesoem/openbmc represents the CSDL that OpenBMC publishesIn theory, this means that in the future we can relax OEM_SCHEMAS.md,and allow folks to possibly implement their own schemas in a way thatdoesn't have to effect all other systems.This also has the advantage of not requiring changes toupdate_schemas.py when we want to add, remove, or modify what version ofa schema we use. "current" schemas are just symlinks, so they can beupdated using git, and not necessarily have merge conflicts with oneanother.Tested: Redfish service validator passes.Change-Id: I6d4a130bba4cb874ef00a06ed579cc67f53dc7aeSigned-off-by: Ed Tanous <ed@tanous.net>
Move the JsonSchemas to be generated at runtimeGenerating all of these index files at compile time is kind of wasteful,considering that it's really not that much code to generate them. Thiscommi
Move the JsonSchemas to be generated at runtimeGenerating all of these index files at compile time is kind of wasteful,considering that it's really not that much code to generate them. Thiscommit modifies the update_schemas script to generate a C++ version ofthe schemas that can then be used to generate a route. This allowsdeleting a LOT of fixed files, for a very small incremental binary sizeincrease.This change will cause two impacts that a user could possibly notice.Expand will now work properly on JsonSchemas tree.Keys on the JsonSchema schemas will now be sorted alphabetically, as wedo elsewhere.All other things should remain the same.Tested:Redfish service validator passes.curl --insecure --user root:0penBmc https://192.168.7.2/redfish/v1/JsonSchemas/TriggersReturns the same object as before with changes above.This adds 2512 bytes to the bmcweb binary size, and interestingly, adds3764 bytes to the overall rootfs size, despite the level of file deletion seen in the patch. While this is debatably "worse" than what we had before in this regard, making JsonSchemas work similar to how the rest of the Redfish tree operates, is worth the minor increase in code size.Signed-off-by: Ed Tanous <edtanous@google.com>Change-Id: Ic0d568112a3784821aa6867f7bcf50705dc586db
Move to 2021.1Update the script to point at 2021.1 and run it.Since we have an exclude list, this only brings in new versions ofschemas bmcweb already uses.Overview of 2021.1:https://www.dmtf
Move to 2021.1Update the script to point at 2021.1 and run it.Since we have an exclude list, this only brings in new versions ofschemas bmcweb already uses.Overview of 2021.1:https://www.dmtf.org/sites/default/files/Redfish_Release_2021.1_Overview.pdfFeatures IBM plans to use:Resource, Action, Enum, and Property Deprecated MessagesBoot Progress: Setup EnteredSystem: Stop Boot On FaultChassis: Spare Part NumberEnabled for Memory, ProcessorLog Entry: AutomatedServiceNotify, ResolutionPower ModesEnable/Disable USBTested: Clean run of the validator passes.Change-Id: Ib22e5ea314c41ae354930b2c5857fe9512859507Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
Move to 2020.42020.4 contains a lot of new schemas.New feature include: new power and thermal schemas, conditions,and new account types.For more information, see:https://www.dmtf.org/sites/def
Move to 2020.42020.4 contains a lot of new schemas.New feature include: new power and thermal schemas, conditions,and new account types.For more information, see:https://www.dmtf.org/sites/default/files/Redfish_Release_2020.4_Overview.pdfTested: Validator passes. Able to see new schemas.Change-Id: I7fb860c84fa4cff80698dcb26a463b155e6faba7Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
Move to 2020.1Make changes to update_schemas.py needed for the move and runupdate_schemas.py.Need 1.3.6 or later version of Redfish-Service-Validator.CI uses the master branch of Redfish-Servic
Move to 2020.1Make changes to update_schemas.py needed for the move and runupdate_schemas.py.Need 1.3.6 or later version of Redfish-Service-Validator.CI uses the master branch of Redfish-Service-Validator, which hasthis fix.Redfish-Service-Validators before 1.3.6 will incorrectly throw errors inmessage registries like (Task Event Message Registry)/redfish/v1/Registries/TaskEvent/TaskEvent and (Base Message Registry)/redfish/v1/Registries/Base/Base.For more information:https://redfishforum.com/thread/323/validator-errors-when-moving-releaseThis does introduce some "warnDeprecated" due to "Severity" becomingDeprecated in MessageRegistry v1_4_0. Since all bmcweb Registries are<v1_4_0, not a real problem. Redfish has no Base Message Registry andTask Event Message Registry available to move to something thatuses MessageRegistry v1_4_0. Will take up with Redfish.2020.1 includes new features like AutoRebot (Boot -> AutomaticRetry),factory reset (ResetToDefaults action), and Modified Event Log propertywhich are in OpenBMC's D-Bus interfaces today.Tested: Built bmcweb, loaded on a Witherspoon, and ran the validator. Validator passed.See new schemas:curl -k https://${bmc}/redfish/v1/JsonSchemas/SecureBootDatabase{ "@odata.context": "/redfish/v1/$metadata#JsonSchemaFile.JsonSchemaFile", "@odata.id": "/redfish/v1/JsonSchemas/SecureBootDatabase", "@odata.type": "#JsonSchemaFile.v1_0_2.JsonSchemaFile", "Name": "SecureBootDatabase Schema File",Change-Id: If30fcc50276aea44d8a77ed547ee0cbd72e4cf1aSigned-off-by: Gunnar Mills <gmills@us.ibm.com>
Update Redfish schemas to 2019.2Note, the DMTF changed the format of the schema file pack yet again, sothe script changes now to compensate for that.Tested:Ran schema validator. One unrelated
Update Redfish schemas to 2019.2Note, the DMTF changed the format of the schema file pack yet again, sothe script changes now to compensate for that.Tested:Ran schema validator. One unrelated failure in LogEntry, and 4 newwarnings in PCIe devices (we're using a deprecated property). All otherendpoints pass.Signed-off-by: Ed Tanous <ed.tanous@intel.com>Change-Id: I81c030a7c5a6a32cc12a5e7e02a9441b7891bc5d
Fix bad link in Redfish JsonSchemas IDChange-Id: I993ae392d87a19acd51fe093f8244a9c781dd339Signed-off-by: Ed Tanous <ed.tanous@intel.com>
Update schema files to 2018.2Redfish schema 2018.2 was released on September 20th, 2018. While therearen't any plans to utilize any of the new services, it makes sense tokeep up to date with the
Update schema files to 2018.2Redfish schema 2018.2 was released on September 20th, 2018. While therearen't any plans to utilize any of the new services, it makes sense tokeep up to date with the latest static data.This commit was largely done automatically using the update_schemas.pyscript.Change-Id: Ieaa9f1ab2a47244ef201cfe9a064744d7d156745Signed-off-by: Ed Tanous <ed.tanous@intel.com>
Fix JsonSchema indexesJsonSchema was throwing errors in the validator, so implement changes tothe update script to add the appropiate indexes.Tested by:Schema validator passes on the JsonSchema
Fix JsonSchema indexesJsonSchema was throwing errors in the validator, so implement changes tothe update script to add the appropiate indexes.Tested by:Schema validator passes on the JsonSchema FieldsChange-Id: I6cb2737901b55c1089aef744d3ce3c3dfe13f17fSigned-off-by: Ed Tanous <ed.tanous@intel.com>
Implement JsonSchema endpointThis patchset implements JsonSchema support, and automates our updateof the XML metadata, and Json schema files in the future by way of apython script.Change-Id: Ie
Implement JsonSchema endpointThis patchset implements JsonSchema support, and automates our updateof the XML metadata, and Json schema files in the future by way of apython script.Change-Id: Iec6f580d10736678149db18d87be2f140b535be9Signed-off-by: Ed Tanous <ed.tanous@intel.com>Signed-off-by: James Feist <james.feist@linux.intel.com>