A set of tools to support the development and test of the Sushy library
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Dmitry Tantsur c5b99058b2 Flatten the emulator resources 6 days ago
doc/source Replace the static Manager driver with a new fake one 6 days ago
releasenotes Support non-ide virtual media buses 1 month ago
sushy_tools Flatten the emulator resources 6 days ago
zuul.d Use victoria tests 1 month ago
.coveragerc Initial Commit 3 years ago
.gitignore Switch to use stestr for unit test 2 years ago
.gitreview OpenDev Migration Patch 1 year ago
.mailmap Initial Commit 3 years ago
.stestr.conf Switch to use stestr for unit test 2 years ago
CONTRIBUTING.rst Initial Commit 3 years ago
HACKING.rst Update the URL in HACKING.rst 1 year ago
LICENSE Initial Commit 3 years ago
README.rst Correct doc link to point to sushy-tools docs 9 months ago
bindep.txt Fix pdf build 3 months ago
lower-constraints.txt Update version of hacking 1 week ago
requirements.txt Stop using six library 3 months ago
setup.cfg Cleanup py27 support 4 months ago
setup.py Cleanup py27 support 4 months ago
test-requirements.txt Update version of hacking 1 week ago
tox.ini Set min version of tox to 3.2.1 4 weeks ago

README.rst

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.