The handler for Bios/BiosRegistry doesn't match the path in bios_attribute_registry_file.json - it shouldn't have the identity. This is also now consistent with the actual response returned by vendors. Change-Id: I719f99ae400134074ca47ccb8bed7df74ccb9b45
|1 week ago|
|doc||2 months ago|
|releasenotes||1 week ago|
|sushy_tools||1 week ago|
|zuul.d||2 months ago|
|.coveragerc||4 years ago|
|.gitignore||3 years ago|
|.gitreview||2 years ago|
|.mailmap||4 years ago|
|.stestr.conf||3 years ago|
|CONTRIBUTING.rst||4 years ago|
|HACKING.rst||3 years ago|
|LICENSE||4 years ago|
|README.rst||2 years ago|
|bindep.txt||1 year ago|
|requirements.txt||8 months ago|
|setup.cfg||2 months ago|
|setup.py||1 year ago|
|test-requirements.txt||6 months ago|
|tox.ini||1 month ago|
Redfish development tools
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.
- Free software: Apache license
- Documentation: https://docs.openstack.org/sushy-tools
- Source: http://opendev.org/openstack/sushy-tools
- Bugs: https://storyboard.openstack.org/#!/project/openstack/sushy-tools