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.
Zuul 35c8b86fa3 Merge "Add Chassis to ServiceRoot" 3 weeks ago
doc remove unicode from code 2 months ago
releasenotes remove unicode from code 2 months ago
sushy_tools Merge "Add Chassis to ServiceRoot" 3 weeks ago
zuul.d Replace the netboot job with a local-boot one 3 months ago
.coveragerc Initial Commit 6 years ago
.gitignore Switch to use stestr for unit test 4 years ago
.gitreview OpenDev Migration Patch 3 years ago
.mailmap Initial Commit 6 years ago
.stestr.conf Switch to use stestr for unit test 4 years ago
CONTRIBUTING.rst Initial Commit 6 years ago
HACKING.rst Update the URL in HACKING.rst 4 years ago
LICENSE Initial Commit 6 years ago
README.rst Correct doc link to point to sushy-tools docs 3 years ago
bindep.txt Use python Zed tests 5 months ago
requirements.txt Drop lower-constraints.txt and its testing 5 months ago
setup.cfg Remove support for Python 3.6 and 3.7 3 months ago
setup.py Cleanup py27 support 3 years ago
test-requirements.txt Fix the CI 5 months ago
tox.ini Drop lower-constraints.txt and its testing 5 months 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.