#54: Documentation: clean up LnstIntro
----------------------+------------------------------------------
Reporter: olichtne | Owner:
Type: task | Status: new
Priority: major | Milestone: Complete Wiki Documentation
Component: wiki | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------------------------
The document is a little bit outdated. It contains a lot of information
because when it was created the wiki didn't exist.
First we want to move the first part to be a separate page. This contains
information about the project and the community. The new page should
either be the front-page or an About page where the user goes first.
Then we need to clean up the entire document so that it doesn't contain
redundant information that will be located in other documents created in
this milestone.
--
Ticket URL: <https://fedorahosted.org/lnst/ticket/54>
lnst <https://fedorahosted.org/lnst/>
Linux Network Stack Test
#53: Documentation: using 3rd party test tools
----------------------+------------------------------------------
Reporter: olichtne | Owner:
Type: task | Status: new
Priority: major | Milestone: Complete Wiki Documentation
Component: wiki | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------------------------
This is a new feature that was implemented recently. You can now use any
number of test tools, and all you need to do is place them in the correct
directory.
This is an advanced topic so the article should be located accordingly.
Documentation should contain information about where and in what format
you need to put the tools. How they are transferred to the slave machines.
And how to use them from the recipe.
--
Ticket URL: <https://fedorahosted.org/lnst/ticket/53>
lnst <https://fedorahosted.org/lnst/>
Linux Network Stack Test
#64: Add Support for Configuration via NetworkManager
-------------------------------------+------------------
Reporter: rpazdera | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: lnst-ctl and lnst-slave | Version: git
Keywords: | Blocked By:
Blocking: |
-------------------------------------+------------------
LNST at the moment doesn't work well with NetworkManager, which must be
disabled in order for LNST to operate properly.
Based on discussions with Pavlix, the problems we've been having with NM
should be all solved now, so it would be nice to add support for network
manager as well.
The options are to use libnm-glib or the dbus interface directly from
python.
However, we need to support older RHEL6 versions as well, so we need to
keep the current configuration routines as a fallback.
--
Ticket URL: <https://fedorahosted.org/lnst/ticket/64>
lnst <https://fedorahosted.org/lnst/>
Linux Network Stack Test
#55: XML Schema Definition for LNST Recipe Syntax
----------------------+------------------
Reporter: rpazdera | Owner:
Type: task | Status: new
Priority: major | Milestone:
Component: lnst-ctl | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------
It would be great if we had a scheme definition for recipes and machine
configs. It could be used for preliminary validation. Also VIM >= 7 should
support syntax checking and even completion based on this definitions!
--
Ticket URL: <https://fedorahosted.org/lnst/ticket/55>
lnst <https://fedorahosted.org/lnst/>
Linux Network Stack Test
#50: Wiki article: How to Structure LNST Recipes
----------------------+------------------------------------------
Reporter: rpazdera | Owner:
Type: task | Status: new
Priority: major | Milestone: Complete Wiki Documentation
Component: wiki | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------------------------
This article should cover everything about lnst recipe creation from a
point of view of an inexperienced LNST user.
It should be easy to understand and not too technical. It doesn't have to
cover the topic completely, but it should give enough information for a
newcomer.
This article should incorporate the topic in the 4th section of the LNST
Intro document.
--
Ticket URL: <https://fedorahosted.org/lnst/ticket/50>
lnst <https://fedorahosted.org/lnst/>
Linux Network Stack Test
#52: Wiki article: Machine Config XML Reference
----------------------+------------------------------------------
Reporter: rpazdera | Owner:
Type: task | Status: new
Priority: major | Milestone: Complete Wiki Documentation
Component: wiki | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------------------------
There should be a separate reference for the XML format of machine configs
that belong to a pool directory. It should be a brief enumeration of
values for advanced users (the guide for beginners will be placed
separately).
--
Ticket URL: <https://fedorahosted.org/lnst/ticket/52>
lnst <https://fedorahosted.org/lnst/>
Linux Network Stack Test
#59: TestPacketAssert: pipe buffering bug
----------------------+------------------
Reporter: olichtne | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: lnst-ctl | Version: git
Keywords: | Blocked By:
Blocking: |
----------------------+------------------
There seems to be a bug caused by using pipes for reading output of the
tcpdump command. Parts of the output are not read often resulting in fail
state of the command.
I think it is connected to buffering of these pipes as sometimes it does
appear and other times it works correctly. The problem could also be
connected to the fact that the program is being run in the background and
is therefore interrupted by a signal, the handler of the signal doesn't
read the rest of the output which it probably should.
--
Ticket URL: <https://fedorahosted.org/lnst/ticket/59>
lnst <https://fedorahosted.org/lnst/>
Linux Network Stack Test
#58: TestIperf
----------------------+------------------
Reporter: olichtne | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: lnst-ctl | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------
Option '''bind''' for this test is mandatory but, if it is not specified
value "None" is used making the corresponding iperf command incorrect and
failing.
Either the default value should be changed or, in my opinion better, this
option should be mandatory seeing as you will probably want to use this on
a testing interface which will most probably not be the default bind
interface.
--
Ticket URL: <https://fedorahosted.org/lnst/ticket/58>
lnst <https://fedorahosted.org/lnst/>
Linux Network Stack Test