It doesn't look like we'll get more alternative implementations for all resources except for systems, nor do we allow loading 3rd party ones. For the sake of simpler development, flatten the package structure and get rid of most abstract classes. Change-Id: I7f84b535520b0be8e8c636d55e109d0402471dc0
|6 days ago|
|doc/source||6 days ago|
|releasenotes||1 month ago|
|sushy_tools||6 days ago|
|zuul.d||1 month ago|
|.coveragerc||3 years ago|
|.gitignore||2 years ago|
|.gitreview||1 year ago|
|.mailmap||3 years ago|
|.stestr.conf||2 years ago|
|CONTRIBUTING.rst||3 years ago|
|HACKING.rst||1 year ago|
|LICENSE||3 years ago|
|README.rst||9 months ago|
|bindep.txt||3 months ago|
|lower-constraints.txt||1 week ago|
|requirements.txt||3 months ago|
|setup.cfg||4 months ago|
|setup.py||4 months ago|
|test-requirements.txt||1 week ago|
|tox.ini||4 weeks ago|
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.