A set of tools to support the development and test of the Sushy library
Go to file
2019-02-28 16:55:27 +00:00
doc/source Limit instances exposure 2019-02-13 18:50:28 +01:00
releasenotes Fix copyright statement 2018-12-05 23:18:39 +01:00
sushy_tools Limit instances exposure 2019-02-13 18:50:28 +01:00
zuul.d Move to zuulv3 2019-02-14 11:03:31 +01:00
.coveragerc Initial Commit 2017-04-06 17:05:16 +01:00
.gitignore Switch to use stestr for unit test 2018-07-27 08:14:22 +07:00
.gitreview Added .gitreview 2017-04-03 08:33:46 +00:00
.mailmap Initial Commit 2017-04-06 17:05:16 +01:00
.stestr.conf Switch to use stestr for unit test 2018-07-27 08:14:22 +07:00
CONTRIBUTING.rst Initial Commit 2017-04-06 17:05:16 +01:00
HACKING.rst Update the URL in HACKING.rst 2018-09-23 16:38:42 +08:00
LICENSE Initial Commit 2017-04-06 17:05:16 +01:00
lower-constraints.txt Add release notes generation 2018-12-04 08:55:16 +01:00
README.rst fix bug link in readme 2018-08-31 06:17:00 -04:00
requirements.txt Make external dependencies optional 2018-11-14 14:54:00 +01:00
setup.cfg Update home-page 2019-01-14 11:29:12 +00:00
setup.py Updated from global requirements 2018-01-08 13:02:05 +00:00
test-requirements.txt Merge "Add release notes generation" 2018-12-05 20:51:28 +00:00
tox.ini Add release notes generation 2018-12-04 08:55:16 +01:00

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.