6f7238135e
Clients like Ironic Redfish inspector expect an integer value for Cores and Threads. We do our best to return an integer value, we also provide a default of "1" in case none is found. Current logic expects the number of threads and cores to be present in the domain, but this is not necessarily the case (test case provided). We also can return a lot of information even when the domain is not active, so we do just that. Story: 2008743 Task: 42100 Change-Id: Id702ca2d7c5965217f348fc0931df0b0b1e57da8 |
||
|---|---|---|
| doc | ||
| releasenotes | ||
| sushy_tools | ||
| zuul.d | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| README.rst | ||
| bindep.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
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.
- Free software: Apache license
- Documentation: https://docs.openstack.org/sushy-tools
- Source: http://opendev.org/openstack/sushy-tools
- Bugs: https://storyboard.openstack.org/#!/project/openstack/sushy-tools