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.
Ilya Etingof adc16921b4 Use HTTP code 307 for redirects 1 month ago
doc/source update git.openstack.org to opendev 3 weeks ago
releasenotes Use HTTP code 307 for redirects 3 weeks ago
sushy_tools Use HTTP code 307 for redirects 3 weeks ago
zuul.d Move to zuulv3 3 months ago
.coveragerc Initial Commit 2 years ago
.gitignore Switch to use stestr for unit test 9 months ago
.gitreview OpenDev Migration Patch 1 month ago
.mailmap Initial Commit 2 years ago
.stestr.conf Switch to use stestr for unit test 9 months ago
CONTRIBUTING.rst Initial Commit 2 years ago
HACKING.rst Update the URL in HACKING.rst 8 months ago
LICENSE Initial Commit 2 years ago
README.rst update git.openstack.org to opendev 3 weeks ago
lower-constraints.txt Fix lower-constraint deps handling 1 month ago
requirements.txt Make external dependencies optional 6 months ago
setup.cfg Update home-page 4 months ago
setup.py Updated from global requirements 1 year ago
test-requirements.txt Fix lower-constraint deps handling 1 month ago
tox.ini update git.openstack.org to opendev 3 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.