Use HTTP code 307 for redirects
Changed HTTP redirect code from 302 to 307 to ensure the original HTTP method is left intact. Otherwise some clients may change PUT/POST to GET on redirect and effectively fail to perform the change they intended. Change-Id: I32613e1ebb4a2eaba33c5884ddbd3ec7cf77d6fd Story: 2005370 Task: 30346
|1 month ago|
|doc/source||3 weeks ago|
|releasenotes||3 weeks ago|
|sushy_tools||3 weeks ago|
|zuul.d||3 months ago|
|.coveragerc||2 years ago|
|.gitignore||9 months ago|
|.gitreview||1 month ago|
|.mailmap||2 years ago|
|.stestr.conf||9 months ago|
|CONTRIBUTING.rst||2 years ago|
|HACKING.rst||8 months ago|
|LICENSE||2 years ago|
|README.rst||3 weeks ago|
|lower-constraints.txt||1 month ago|
|requirements.txt||6 months ago|
|setup.cfg||4 months ago|
|setup.py||1 year ago|
|test-requirements.txt||1 month ago|
|tox.ini||3 weeks ago|
This is a set of simple simulation tools aiming at supporting the development and testing of the Redfish protocol implementations and, in particular, Sushy library (https://docs.openstack.org/sushy/).
The package ships two simulators - static Redfish responder and virtual Redfish BMC that is backed by libvirt or OpenStack cloud.
The static Redfish responder is a simple REST API server which responds the same things to client queries. It is effectively read-only.
The virtual Redfish BMC resembles the real Redfish-controlled bare-metal machine to some extent. Some client queries are translated to commands that actually control VM instances simulating bare metal hardware. However some of the Redfish commands just return static content never touching the virtualization backend and, for that matter, virtual Redfish BMC is similar to the static Redfish responser.