Retain boot device selection upon boot image change
When changing boot image in libvirt domain, note current boot device and restore it if the image being changed resides on the active boot device. Prior to this patch, as a side-effect of changing boot image, boot device selection could get reset. Change-Id: Ic848882acbd446effbdf9b761d4ac1025d24c324
|1 week ago|
|doc/source||2 weeks ago|
|releasenotes||1 week ago|
|sushy_tools||1 week ago|
|zuul.d||2 weeks ago|
|.coveragerc||2 years ago|
|.gitignore||1 year ago|
|.gitreview||7 months ago|
|.mailmap||2 years ago|
|.stestr.conf||1 year ago|
|CONTRIBUTING.rst||2 years ago|
|HACKING.rst||1 year ago|
|LICENSE||2 years ago|
|README.rst||1 month ago|
|bindep.txt||5 months ago|
|lower-constraints.txt||3 months ago|
|requirements.txt||3 months ago|
|setup.cfg||2 weeks ago|
|setup.py||1 year ago|
|test-requirements.txt||2 weeks ago|
|tox.ini||2 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.