summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZuul <zuul@review.opendev.org>2023-03-14 18:02:40 +0000
committerGerrit Code Review <review@openstack.org>2023-03-14 18:02:40 +0000
commit041e242e70afaf83cefebde1aa45fcbb581e74fc (patch)
treebbeeffc7644d3b74f5be6ad4f20124400b4c0fbb
parent718d52c792290e3e10892667eb4fa2b48b273f81 (diff)
parentb41d5d514585a1cc5c6d80553afdf2eb767d6917 (diff)
downloadironic-041e242e70afaf83cefebde1aa45fcbb581e74fc.tar.gz
Merge "Document [fake] delay config values"
-rw-r--r--doc/source/admin/drivers/fake.rst24
1 files changed, 24 insertions, 0 deletions
diff --git a/doc/source/admin/drivers/fake.rst b/doc/source/admin/drivers/fake.rst
index ea7d7ef4c..2e2cc355e 100644
--- a/doc/source/admin/drivers/fake.rst
+++ b/doc/source/admin/drivers/fake.rst
@@ -23,6 +23,30 @@ Development
Developers can use ``fake-hardware`` hardware-type to mock out nodes for
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
--------
Some OpenStack deployers have used ``fake`` interfaces in Ironic to allow an