I have another idea for a feature to LNST. I'm using it together with
libvirt and I
thought that it could be nice to have direct control over the network
from LNST. When using libvirt for testing, this could be easily
the virsh command.
Now, when you're running some tests, you have to set up the required network
topology by yourself and put MAC and IP addresses into the recipe. When you
want to run the test on a different VM (with different version of
you need to set up the topology again by hand and also alter the recipe.
I thought we could make LNST to be able to control this setup. Virtually
configuration of libvirt's networks and domains are accessible through XML,
so they can be easily parsed and modified.
There could be a pool of installed VM's available on the controller.
LNST could detect
available machines (virsh list --all), modify the number of interfaces
(virsh dumpxml/define), define some networks (bridges/tap devices -
and connect them into some topology. Everything would be controlled from
the recipe XML file. At the end LNST would boot up the machines and run
Some of those machines could act as switches (with openvswitch) or even
we could build a whole virtual network.
What do you think?
Could this approach be useful?