Hello,
First, I think this is a great project and think it has a lot of
potential. Second, I'm wondering if someone might be able to help me
model my current test cases in lnst. I'll include the job xml that I'm
currently using in beaker and try and break it down here.
The physical setup is between two real systems, and on each real system
is 3 virtual systems:
SystemA
rhel6u4_1
rhel6u4_2
rhel6u4_3
SystemB
rhel6u4_4
rhel6u4_5
rhel6u4_6
SystemA and SystemB have multiple network interfaces.
We want to test OpenVSwitch with the bnx2x driver and vlans.
My test plan does the following:
- Provision SystemA with RHEL6U4
- Install three virt guests
- Install openVswitch
- Configure ovsbridge1 using p2p1 (we know this is the bnx2x card), use
a local private ip address, also configure which trunks will support.
- Add the ovsbridge1 interface to rhel6u4_1,rhel6u4_2 with tag 100
- Add the ovsbridge1 interface to rhel6u4_3 with tag 200
- Start the virt guests with their new config. All guests will start
with eth0, and when running they will configure eth1
- From each guest ping the other guests, record pass/fail based on
whether you should have been able to or not.
- same test as previous but using netperf.
In parallel I do the same thing on SystemB.
SystemA interface p2p1 is connected through a private switch to SystemB
interface p2p1
This works but I am hard coded to using two hosts that I know are
configured the way I need. From looking at lnst it looks like this
could be done more dynamically. I did see some references to beaker
integration but I didn't see anything more.
Is this use case too complicated? Do you see subsets that could be
tackled now?
Any help would be appreciated. Thanks!
Show replies by thread