Ilya Etingof b13ea4e9c7 Add memoization to expensive emulator calls
Drivers of Redfish emulator now cache the
outcome of a select calls choosing either the
two policies:

* Cache the information for the lifetime of the
  emulator process if it's unlikely for such
  data to get out of sync
* Cache the more dynamic information just for
  the duration of a single Redfish REST API
  call

This change improves emulator responsiveness.

Change-Id: Ief46a0a7b82900ccf6d4c9ebb417f711a9b00513
2019-03-05 14:39:58 +01:00
2019-02-13 18:50:28 +01:00
2018-12-05 23:18:39 +01:00
2019-02-14 11:03:31 +01:00
2017-04-06 17:05:16 +01:00
2018-07-27 08:14:22 +07:00
2017-04-03 08:33:46 +00:00
2017-04-06 17:05:16 +01: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
2018-08-31 06:17:00 -04:00
2019-01-14 11:29:12 +00:00
2018-01-08 13:02:05 +00:00
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.

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