<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bmcweb/scripts, branch master</title>
<subtitle>OpenBMC Web server</subtitle>
<id>https://git.raptorcs.com/git/bmcweb/atom?h=master</id>
<link rel='self' href='https://git.raptorcs.com/git/bmcweb/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/'/>
<updated>2020-02-10T18:34:00+00:00</updated>
<entry>
<title>Move to 2019.3</title>
<updated>2020-02-10T18:34:00+00:00</updated>
<author>
<name>Gunnar Mills</name>
<email>gmills@us.ibm.com</email>
</author>
<published>2020-02-06T22:50:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=6f44b7524f1d48d009ec87b1309481c7905b13b4'/>
<id>urn:sha1:6f44b7524f1d48d009ec87b1309481c7905b13b4</id>
<content type='text'>
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 &lt;gmills@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Update update_schemas.py with new Oem</title>
<updated>2020-02-07T19:07:33+00:00</updated>
<author>
<name>Gunnar Mills</name>
<email>gmills@us.ibm.com</email>
</author>
<published>2020-02-06T22:36:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=2077899f6d4534d98ca2cca3bc9020dbc6a4aef9'/>
<id>urn:sha1:2077899f6d4534d98ca2cca3bc9020dbc6a4aef9</id>
<content type='text'>
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 &lt;gmills@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Update Redfish schemas to 2019.2</title>
<updated>2019-10-11T21:13:05+00:00</updated>
<author>
<name>Ed Tanous</name>
<email>ed.tanous@intel.com</email>
</author>
<published>2019-10-08T18:34:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=cb103130e18689b9a8e15284f930606d512328cd'/>
<id>urn:sha1:cb103130e18689b9a8e15284f930606d512328cd</id>
<content type='text'>
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 &lt;ed.tanous@intel.com&gt;
Change-Id: I81c030a7c5a6a32cc12a5e7e02a9441b7891bc5d
</content>
</entry>
<entry>
<title>Fix a bunch of warnings</title>
<updated>2019-10-10T23:25:26+00:00</updated>
<author>
<name>Ed Tanous</name>
<email>ed.tanous@intel.com</email>
</author>
<published>2019-07-09T23:24:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=271584ab78b4c1926f766aa26ddfde7da329059f'/>
<id>urn:sha1:271584ab78b4c1926f766aa26ddfde7da329059f</id>
<content type='text'>
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 &lt;ed.tanous@intel.com&gt;
Change-Id: I588c26440e5a97f718a0f0ea74cc84107d53aa1e
</content>
</entry>
<entry>
<title>Update websocket test script</title>
<updated>2019-10-10T18:16:15+00:00</updated>
<author>
<name>Ed Tanous</name>
<email>ed.tanous@intel.com</email>
</author>
<published>2019-10-03T18:36:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=70ee8cbd4f3ec5b3e3c18967de221a9f3a70cd38'/>
<id>urn:sha1:70ee8cbd4f3ec5b3e3c18967de221a9f3a70cd38</id>
<content type='text'>
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 &lt;myhostname&gt;

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 &lt;ed.tanous@intel.com&gt;
Change-Id: I617f73a5b70f61a391e9c61638f0bcf4437bf6ce
</content>
</entry>
<entry>
<title>Redfish: fix warning in validator</title>
<updated>2019-05-09T21:13:23+00:00</updated>
<author>
<name>Ed Tanous</name>
<email>ed.tanous@intel.com</email>
</author>
<published>2019-05-04T00:15:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=6f56d0c24cc2413cf03069fdcfe0684f3b454d64'/>
<id>urn:sha1:6f56d0c24cc2413cf03069fdcfe0684f3b454d64</id>
<content type='text'>
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 &lt;ed.tanous@intel.com&gt;
Change-Id: I184422d7a14838339253c945d7a0c91878093e17
</content>
</entry>
<entry>
<title>Parse Message Registry header info from the file</title>
<updated>2019-05-08T19:08:00+00:00</updated>
<author>
<name>Jason M. Bills</name>
<email>jason.m.bills@linux.intel.com</email>
</author>
<published>2019-03-27T19:58:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=351d3063e86c5a6047c995ba72552bd82df86489'/>
<id>urn:sha1:351d3063e86c5a6047c995ba72552bd82df86489</id>
<content type='text'>
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 &lt;jason.m.bills@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Remove the static Base Message Registry file</title>
<updated>2019-05-08T19:08:00+00:00</updated>
<author>
<name>Jason M. Bills</name>
<email>jason.m.bills@linux.intel.com</email>
</author>
<published>2019-03-27T19:03:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=70304cb594859b3862eeecc0a16c8e6e9a126530'/>
<id>urn:sha1:70304cb594859b3862eeecc0a16c8e6e9a126530</id>
<content type='text'>
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 &lt;jason.m.bills@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Redfish: Fix incorrect reference tag added as part of update_schemas.py script</title>
<updated>2019-03-11T15:24:49+00:00</updated>
<author>
<name>Marri Devender Rao</name>
<email>devenrao@in.ibm.com</email>
</author>
<published>2019-03-01T08:14:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=c9ab1d509ec70f895f852532f6c5b3314cb4fe65'/>
<id>urn:sha1:c9ab1d509ec70f895f852532f6c5b3314cb4fe65</id>
<content type='text'>
Change-Id: I763534d54b7630aec30883d04e02b4f478c10ab4
Signed-off-by: Marri Devender Rao &lt;devenrao@in.ibm.com&gt;
</content>
</entry>
<entry>
<title>Fix bad link in Redfish JsonSchemas ID</title>
<updated>2019-02-06T21:30:13+00:00</updated>
<author>
<name>Ed Tanous</name>
<email>ed.tanous@intel.com</email>
</author>
<published>2019-01-03T22:09:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=63faafa51e36aee569af10cb40cbd32bafc68e33'/>
<id>urn:sha1:63faafa51e36aee569af10cb40cbd32bafc68e33</id>
<content type='text'>
Change-Id: I993ae392d87a19acd51fe093f8244a9c781dd339
Signed-off-by: Ed Tanous &lt;ed.tanous@intel.com&gt;
</content>
</entry>
</feed>
