From f13eb91e51bd9bbae2f15c498b5ebb213ad62705 Mon Sep 17 00:00:00 2001 From: Loic Dachary Date: Fri, 27 Mar 2015 07:19:23 +0100 Subject: [PATCH] rados: explain that the task is asynchronous by default Signed-off-by: Loic Dachary --- tasks/rados.py | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/tasks/rados.py b/tasks/rados.py index 720da159630d0..e5f83cbf3a4c7 100644 --- a/tasks/rados.py +++ b/tasks/rados.py @@ -89,6 +89,38 @@ def task(ctx, config): pool_prefix: foo ... + The tests are run asynchronously, they are not complete when the task + returns. For instance: + + - rados: + clients: [client.0] + pools: [ecbase] + ops: 4000 + objects: 500 + op_weights: + read: 100 + write: 100 + delete: 50 + copy_from: 50 + - print: "**** done rados ec-cache-agent (part 2)" + + will run the print task immediately after the rados tasks begins but + not after it completes. To make the rados task a blocking / sequential + task, use: + + - sequential: + - rados: + clients: [client.0] + pools: [ecbase] + ops: 4000 + objects: 500 + op_weights: + read: 100 + write: 100 + delete: 50 + copy_from: 50 + - print: "**** done rados ec-cache-agent (part 2)" + """ log.info('Beginning rados...') assert isinstance(config, dict), \ -- 2.39.5