summaryrefslogtreecommitdiffstats
path: root/scripts
Commit message (Collapse)AuthorAgeFilesLines
* Move to 2019.3Gunnar Mills2020-02-101-7/+3
| | | | | | | | | | | | | | | | | | | | | | | Make changes to update_schemas.py needed for the move and run update_schemas.py. old path (2019.2) DSP8010_2019.2/DSP8010_2019.2/json-schema/MemoryMetrics.v1_1_2.json DSP8010_2019.2/DSP8010_2019.2/openapi/Memory.v1_0_3.yaml DSP8010_2019.2/DSP8010_2019.2/csdl/AccelerationFunction_v1.xml new path (2019.3) DSP8010_2019.3/csdl/Memory_v1.xml DSP8010_2019.3/json-schema/UpdateService.v1_1_2.json DSP8010_2019.3/openapi/Zone.v1_3_1.yaml To see an overview of 2019.3 see https://www.dmtf.org/sites/default/files/Redfish_Release_2019.3_Overview.pdf Tested: Built bmcweb, loaded on a Witherspoon, and ran the validator. No errors. Change-Id: I0deaf88b884d65fffa31fcf66183ed61a930a073 Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
* Update update_schemas.py with new OemGunnar Mills2020-02-071-1/+24
| | | | | | | | | | | | | | | | | | | | | | Several Oem schemas have been added but the update_schemas.py has not been updated. Added them to the update_schemas.py so the static/redfish/v1/$metadata/index.xml is correctly built by update_schemas.py. This is needed to move us to 2019.3 and eventually 2019.4. Ideally, we would not just have a bunch of metadata_index.write to write the Oem schemas to $metadata/index.xml but this will do for now. https://github.com/openbmc/bmcweb/issues/32 is to improve this. Tested: Ran update_schemas.py and loaded that image on a Witherspoon and ran the validator. No errors. Change-Id: Iade028e690c31e25a72503d9352bc75eb7ee58dc Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
* Update Redfish schemas to 2019.2Ed Tanous2019-10-111-16/+32
| | | | | | | | | | | | | Note, the DMTF changed the format of the schema file pack yet again, so the script changes now to compensate for that. Tested: Ran schema validator. One unrelated failure in LogEntry, and 4 new warnings in PCIe devices (we're using a deprecated property). All other endpoints pass. Signed-off-by: Ed Tanous <ed.tanous@intel.com> Change-Id: I81c030a7c5a6a32cc12a5e7e02a9441b7891bc5d
* Fix a bunch of warningsEd Tanous2019-10-101-17/+17
| | | | | | | | | | | | | | | using the list of warnings from here: https://github.com/lefticus/cppbestpractices/blob/e73393f25a85f83fed7399d8b65cb117d00b2231/02-Use_the_Tools_Available.md#L100 Seems like a good place to start, and would improve things a bit type-wise. This patchset attempts to correct all the issues in one shot. Tested: It builds. Will test various subsystems that have been touched Signed-off-by: Ed Tanous <ed.tanous@intel.com> Change-Id: I588c26440e5a97f718a0f0ea74cc84107d53aa1e
* Update websocket test scriptEd Tanous2019-10-101-20/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit reworks the websocket test script to be more usable without editing it. Namely it: 1. Moves the script to the websockets library, as it seems to be in more use 2. Implements an argument parser, so the script doesn't require modification of host and username/password variables to use. 3. Moves to basic auth, which doesn't require a secondary login 4. implements better parsing of the result rather than simply printing the json scructure directly. Tested: Ran ./websocket_test.py --host <myhostname> Observed streaming sensor values in the form: System_Airflow 72.00 CFM Fan_1 6153.00 RPM System_Airflow 72.22 CFM Fan_6 6048.00 RPM System_Airflow 72.24 CFM Baseboard_12Volt 12.21 Volts P105_PCH_AUX 1.05 Volts PSU1_Input_Power 94.62 Watts PSU2_Output_Current 6.72 Amps Signed-off-by: Ed Tanous <ed.tanous@intel.com> Change-Id: I617f73a5b70f61a391e9c61638f0bcf4437bf6ce
* Redfish: fix warning in validatorEd Tanous2019-05-091-1/+1
| | | | | | | | | | | | | | | | The validator gives warnings like: URI acquired ends in slash: /redfish/v1/JsonSchemas/Zone These warnings don't actually result in warnings, because the trailing slash has always been a question in the spec, but we might as well do it correctly, even if most of the tools don't take an issue with it. Tested: Ran service validator, saw no new failures, and observed no errors mentioned above. Signed-off-by: Ed Tanous <ed.tanous@intel.com> Change-Id: I184422d7a14838339253c945d7a0c91878093e17
* Parse Message Registry header info from the fileJason M. Bills2019-05-081-2/+15
| | | | | | | | | | | | This extends the Message Registry parsing to include header details that are part of the redfish resource. Tested: Verified that the MessageRegistry info all returns correctly in the redfish response. Change-Id: I6179c07f4067cd4520fce3e774d18530fede0a95 Signed-off-by: Jason M. Bills <jason.m.bills@linux.intel.com>
* Remove the static Base Message Registry fileJason M. Bills2019-05-081-0/+85
| | | | | | | | | | | | | | | | This change removes the static Base Message Registry file and replaces it with a compile-time structure. A script is used to pull the Base Message Registry file from the DMTF and parse it into the .hpp structure. Tested: Verified that after running the script, I can get the same Redfish data back from the existing endpoints without using the static files. Change-Id: Ide3c61ecff62801c06619d5c3edc2229c945d8e7 Signed-off-by: Jason M. Bills <jason.m.bills@linux.intel.com>
* Redfish: Fix incorrect reference tag added as part of update_schemas.py scriptMarri Devender Rao2019-03-111-1/+1
| | | | | Change-Id: I763534d54b7630aec30883d04e02b4f478c10ab4 Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
* Fix bad link in Redfish JsonSchemas IDEd Tanous2019-02-061-2/+2
| | | | | Change-Id: I993ae392d87a19acd51fe093f8244a9c781dd339 Signed-off-by: Ed Tanous <ed.tanous@intel.com>
* Redfish: Update schema files to 2018.3Marri Devender Rao2019-02-021-26/+30
| | | | | | | | | | | | Redfish schema 2018.3 was released on January 11th, 2019. While there aren't any plans to utilize any of the new services, it makes sense to keep up to date with the latest static data. This commit was largely done automatically using the update_schemas.py script. Change-Id: I74c6fac08d21629ca976ff8694fce011b5247e34 Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
* Update schema files to 2018.2Ed Tanous2019-01-071-2/+2
| | | | | | | | | | | | Redfish schema 2018.2 was released on September 20th, 2018. While there aren't any plans to utilize any of the new services, it makes sense to keep up to date with the latest static data. This commit was largely done automatically using the update_schemas.py script. Change-Id: Ieaa9f1ab2a47244ef201cfe9a064744d7d156745 Signed-off-by: Ed Tanous <ed.tanous@intel.com>
* [scripts] Avoid deleting Oem Schemas During UpdateJames Feist2018-10-291-1/+4
| | | | | | | Don't delete Oem json and xml files. Change-Id: I2e4e2a49c776442c5d5e9d85400d3f6dba1f1d5a Signed-off-by: James Feist <james.feist@linux.intel.com>
* Fix JsonSchema indexesEd Tanous2018-10-161-11/+82
| | | | | | | | | | | JsonSchema was throwing errors in the validator, so implement changes to the update script to add the appropiate indexes. Tested by: Schema validator passes on the JsonSchema Fields Change-Id: I6cb2737901b55c1089aef744d3ce3c3dfe13f17f Signed-off-by: Ed Tanous <ed.tanous@intel.com>
* Implement JsonSchema endpointEd Tanous2018-09-171-0/+92
| | | | | | | | | | This patchset implements JsonSchema support, and automates our update of the XML metadata, and Json schema files in the future by way of a python script. Change-Id: Iec6f580d10736678149db18d87be2f140b535be9 Signed-off-by: Ed Tanous <ed.tanous@intel.com> Signed-off-by: James Feist <james.feist@linux.intel.com>
* Make dbus monitor compatible with phosphor-restEd Tanous2018-08-241-0/+21
| | | | | | | | | | | | | | | | | | | | This patchset makes the dbus monitor compatible with the upstream dbus monitor, which should help adoption. Performance seems greatly improved compared to the python implementation. The example given in the documentation of watching for sensors and state changes is checked in as a test script websocket_test.py, and seems to consume less of the CPU than the actual sensors that get produced (about 4% CPU on my ast2500) when producing 30 sensor updates per second. This can likely be improved in the future by batching change events, but it seems to be performant enough for the moment. Tested: Used test script checked in, and verified webui can register state change events properly. Change-Id: I7d4c61d0259b7773eb46df0f59f8fea1c7796450 Signed-off-by: Ed Tanous <ed.tanous@intel.com>
* Remove VScode specific scriptEd Tanous2018-08-151-29/+0
| | | | | | | | Latest version of vscode CMake plugin does this automatically, so this script has no reason to exist anymore. Change-Id: I917822c4359b85bd7afca610b25145377a07606b Signed-off-by: Ed Tanous <ed.tanous@intel.com>
* Remove hunter and submodulesEd tanous2018-04-242-422/+0
| | | | | | | And use external project instead. This should make it easier to keep our systems up to date with yocto. Change-Id: Id2c9f3e474eebf2194eaf58b0c572f7a1421def6
* Large updates to webserverEd Tanous2017-10-111-236/+108
| | | | | | Do not merge yet Change-Id: I38c56844c1b0e3e8e5493c2705e62e6db7ee2102
* incrementalEd Tanous2017-06-061-31/+35
|
* IncrementalEd Tanous2017-05-231-2/+4
|
* inrementalEd Tanous2017-05-121-1/+1
|
* incrementalEd Tanous2017-05-111-2/+2
|
* incrementalEd Tanous2017-04-241-3/+26
|
* incrementalEd Tanous2017-04-181-1/+5
|
* Make app middlewares not require specific instances of appEd Tanous2017-04-053-1/+435
|
* Add route printerEd Tanous2017-04-041-112/+130
|
* incrementalEd Tanous2017-04-031-10/+7
|
* incrementalEd Tanous2017-03-241-42/+120
|
* incrementalEd Tanous2017-03-211-49/+87
|
* incrementalEd Tanous2017-03-131-25/+109
|
* incrementalEd Tanous2017-03-071-5/+5
|
* incremetnalEd Tanous2017-03-031-1/+6
|
* incrementalEd Tanous2017-03-022-29/+81
|
* incrementalEd Tanous2017-02-281-0/+29
|
* incrementalEd Tanous2017-02-281-1/+2
|
* update start and add vscode scriptEd Tanous2017-02-281-0/+28
OpenPOWER on IntegriCloud