Hi again,
thanks for your continued interest in our project!
I went through all the tests on the link, using the same version
(lnst-0.1 devel), and I didn't have any compatibility issues. I only
changed a few machine specific values. Could you be more specific as to
which recipes you had to modify, and how?
However thanks for the feedback, we will start to include some kind of
lnst version indication to our documentation. As it is now there are a
few pages that are already documenting the version in git which isn't in
any way obvious.
For the problem with your vlan recipe. I fixed your recipe and will
attach it to this email, it should run for your setup once you replace
the IP and MAC addresses.
The problem which you were having is that yoy specified a physical eth
interface in the netdevices section:
<netdevice type="eth" network="tnet"
hwaddr="00:0c:29:04:e0:1f" phys_id="1"/>
This means that lnst expects to find this physical interface on the slave
machine and later configure it and use it somehow in the test. The
configuration part means that this interface MUST appear again in the
netconfig section, however as it will be used by the vlan interface the
configuration is empty:
<interface id="1" phys_id="1" type="eth"/>
And now you need to configure the vlan interface itself. This is a software
interface- it's not permanently present on the slave machine (that's why
it's not in the netdevices section) and it will be created by lnst (it
needs to be in the netconfig section):
<interface id="testfc1" type="vlan">
<options>
<option name="vlan_tci" value="10"/>
</options>
<slaves>
<slave id="1"/>
</slaves>
<addresses>
<address value="192.168.1.7/24"/>
</addresses>
</interface>
Since it's a soft interface and doesn't reference any physical interface
this tag doesn't have any phys_id attribute. Also the vlan_tci option is
MANDATORY, it specifies what tag should the interface be using, the
value needs to be the same for both machines if you want to connect
them.
And again I must stress that we know this is quite confusing which is why
this will be done differently in the next snapshot we release.
If you have any more question/problems, we will be happy to help.
-Ondrej
On Sat, Jun 29, 2013 at 09:47:18AM +0800, FangXinglorrie wrote:
Hi Ondrej,
Thanks again for your reply!
I've made all the existing recipes running smoothly except the vlan one. I attached
my version within this mail and hopefully you can help me to figure out what's wrong
in my case.
BTW, I noticed that I have to do some modification to make the following link's test
cases
"https://fedorahosted.org/lnst/wiki/Tests"
to work in my environment successfully.
It may because of the version I am using (lnst-0.1 devel) . But I suggest that the lnst
developers to put some words on the webpage to mention that which version of lnst that
those recipes should work on.
Thanks and looking forward to hearing from you!
Xing