Piotr Czarnik 240e8d754e Normalize relative path for emulator config file
Previously we couldn't use a relative path in --config option
because it was interpreted as a path relative to the package dir.

Task: 49792
Story: 2011082
Change-Id: I59664991079a969a5af93114a0ab45fd36a4bcbe
2024-03-29 13:45:38 +02:00
2024-01-29 19:12:47 +00:00
2017-04-06 17:05:16 +01:00
2018-07-27 08:14:22 +07:00
2019-04-19 19:44:40 +00:00
2017-04-06 17:05:16 +01:00
2022-05-04 17:42:22 +02:00
2017-04-06 17:05:16 +01:00
2018-09-23 16:38:42 +08:00
2017-04-06 17:05:16 +01:00
2020-04-05 20:13:36 +02:00
2022-04-26 09:54:13 +02: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/). It is not designed for use outside of development and testing environments. Please do not run sushy-tools in a production environment of any kind.

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 responder.

Description
A set of tools to support the development and test of the Sushy library
Readme 5.2 MiB
Languages
Python 100%