From: Ondrej Lichtner <olichtne(a)redhat.com>
Implementing the ping and perf endpoint generator methods as are now
expected from the BaseEnrtRecipe test loop implementation. At the same
time it's now not required to track these in the EnrtConfiguration
object so we can remove them.
Signed-off-by: Ondrej Lichtner <olichtne(a)redhat.com>
---
lnst/Recipes/ENRT/SimplePerfRecipe.py | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/lnst/Recipes/ENRT/SimplePerfRecipe.py
b/lnst/Recipes/ENRT/SimplePerfRecipe.py
index 05e2828..42491e3 100644
--- a/lnst/Recipes/ENRT/SimplePerfRecipe.py
+++ b/lnst/Recipes/ENRT/SimplePerfRecipe.py
@@ -24,8 +24,6 @@ def test_wide_configuration(self):
host1, host2 = self.matched.host1, self.matched.host2
configuration = EnrtConfiguration()
- configuration.endpoint1 = host1.eth0
- configuration.endpoint2 = host2.eth0
configuration.params = self.params
if "mtu" in self.params:
@@ -55,3 +53,9 @@ def test_wide_configuration(self):
def test_wide_deconfiguration(self, config):
host1, host2 = self.matched.host1, self.matched.host2
+
+ def generate_ping_endpoints(self, config):
+ return [(self.matched.host1.eth0, self.matched.host2.eth0)]
+
+ def generate_perf_endpoints(self, config):
+ return [(self.matched.host1.eth0, self.matched.host2.eth0)]
--
2.22.0