Project

General

Profile

Actions

action #153217

open

[qe-core] Schedule network tests with bonding setup on MicroOs

Added by amanzini 11 months ago. Updated about 1 month ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Target version:
Start date:
2024-01-08
Due date:
% Done:

0%

Estimated time:
Difficulty:
Sprint:
QE-Core: September Sprint 24 (Sep 05 - Oct 03)

Description

follow up from https://github.com/os-autoinst/opensuse-jobgroups/pull/401#issuecomment-1880696012

We can leverage the special network bond setup (with double network card) to run some other network related tests in the same environment.

Let's collect some ideas and proposals.

Actions #1

Updated by amanzini 11 months ago

  • Subject changed from Schedule network tests with bonding setup on MicroOs to [qe-core] Schedule network tests with bonding setup on MicroOs
Actions #2

Updated by vkatkalov 3 months ago

What about this test? https://openqa.opensuse.org/tests/4416901#step/network_bonding/

I have tested on local machine and it seems to be working nmcli con add type bond ifname bond0 con-name bond0 bond.options "mode=balance-xor,miimon=10", therefore, need clarification on the ticket, whether to cover more cases or verify contents of cat /proc/net/bonding/bond0 or something else?

Actions #3

Updated by vkatkalov 3 months ago

  • Status changed from New to Feedback
Actions #4

Updated by amanzini 3 months ago

@vkatkalov : yes, the previous https://openqa.opensuse.org/tests/4416901#step/network_bonding/ test is just a smoke test to check whenever nic bonding and failover works on Micro.

This ticket is more a place to collect ideas and proposal about further network tests that can be scheduled on that specific hardware bonding setup. Maybe looking at the existing network testsuites could give some suggestions ?

Actions #6

Updated by amanzini 3 months ago

I would say that's on a good track; I'd personally work more on integration related test, for example providing end-to-end services like a typical customer scenario. Performance is interesting as well but I'm not sure is in scope (and we basically running only with virtual NICs, so I'd expect no big surprises here, as it would reduce to testing the hypervisor networking). But feel free to coordinate with the team :)

Actions #7

Updated by vkatkalov 3 months ago

  • Assignee set to vkatkalov
Actions #9

Updated by szarate 3 months ago

  • Sprint set to QE-Core: September Sprint 24 (Sep 05 - Oct 03)
  • Tags set to qe-core-september-sprint
Actions #12

Updated by vkatkalov about 1 month ago · Edited

https://openqa.opensuse.org/tests/4551325
https://openqa.opensuse.org/tests/4551381
Also available on OSD.

What's also possible is to overload DHCPD_SERVER_IMAGE_NAME=registry.opensuse.org/suse/alp/workloads/tumbleweed_containerfiles/suse/alp/workloads/kea:latest and DHCPD_SERVER_IMAGE_REGISTRY with own image, which let's say would have additionally iperf or anything else, and during -ping test execution pause it, VNC into it and run own commands to conduct additional experiments.

Actions

Also available in: Atom PDF