openstack/ironic
Code Issues Proposed changes

Merge "Document [fake] delay config values"

Browse Source
This commit is contained in:
Zuul 2023-03-14 18:02:40 +00:00 committed by Gerrit Code Review
commit 041e242e70
1 changed files with 24 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
doc/source/admin/drivers/fake.rst
View File

@ -23,6 +23,30 @@ Development
Developers can use ``fake-hardware`` hardware-type to mock out nodes for Developers can use ``fake-hardware`` hardware-type to mock out nodes for
testing without those nodes needing to exist with physical or virtual hardware. testing without those nodes needing to exist with physical or virtual hardware.
Scale testing
-------------
The ``fake`` drivers have a configurable delay in seconds which will result in
those operations taking that long to complete. Two comma-delimited values will
result in a delay with a triangular random distribution, weighted on the first
value. These delays are applied to operations which typically block in other
drivers. This allows more realistic scenarios to be arranged for performance and
functional testing of an Ironic service without requiring real bare metal or
faking at the BMC protocol level.
.. code-block:: ini
[fake]
power_delay = 5
boot_delay = 10
deploy_delay = 60,360
vendor_delay = 1
management_delay = 5
inspect_delay = 360,480
raid_delay = 10
bios_delay = 5
storage_delay = 10
rescue_delay = 120
Adoption Adoption
-------- --------
Some OpenStack deployers have used ``fake`` interfaces in Ironic to allow an Some OpenStack deployers have used ``fake`` interfaces in Ironic to allow an