From: Ondrej Lichtner <olichtne(a)redhat.com>
EnrtConfiguration object should contain information about the test wide
configuration, that is relevant during the entire execution of the
recipe. Most of this is directly represented by the values of recipe
parameters.
I'm adding the params attribute to the EnrtConfiguration class as a way
to have access to a copy of these values during parts of the test that
don't have access to the original Recipe object.
The most logical place where this will be used is PerfResult evaluation.
However I still consider this just an experimental approach as I think
it might not work very well for all the enrt recipes that we have and a
larger code refactoring of this code might be required.
Signed-off-by: Ondrej Lichtner <olichtne(a)redhat.com>
---
lnst/Recipes/ENRT/BaseEnrtRecipe.py | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/lnst/Recipes/ENRT/BaseEnrtRecipe.py b/lnst/Recipes/ENRT/BaseEnrtRecipe.py
index 1c2b062..6beee3c 100644
--- a/lnst/Recipes/ENRT/BaseEnrtRecipe.py
+++ b/lnst/Recipes/ENRT/BaseEnrtRecipe.py
@@ -18,6 +18,7 @@ class EnrtConfiguration(object):
def __init__(self):
self._endpoint1 = None
self._endpoint2 = None
+ self._params = None
@property
def endpoint1(self):
@@ -35,6 +36,15 @@ class EnrtConfiguration(object):
def endpoint2(self, value):
self._endpoint2 = value
+ @property
+ def params(self):
+ return self._params
+
+ @params.setter
+ def params(self, value):
+ self._params = value
+
+
class EnrtSubConfiguration(object):
def __init__(self):
self._ip_version = None
--
2.21.0