...
Figure 1: System Level Diagram
Building the LUTF
The LUTF shall be integrated with the Lustre tests under lustre/tests/lutf
. The LUTF will be built and packaged with the standard
Code Block |
---|
sh ./autogen.sh
./configure --with-linux=<kernel path>
make
# optionally
make rpms
# optionally
make install |
The make system will build the following items:
lutf
binaryliblutf_agent.so
- shared library to communicate with the LUTF backend.clutf_agen.py
and _clutf_agent.so
: glue code that allows python to call functions in liblutf_agent.so
- glue code to allow python test scripts to utilize the DLC interface.lnetconfig.py
and _lnetconfig.so
The build process will check if python 2.7.5
and SWIG 2.0
or higher is installed before building. If these requirements are not met the LUTF will not be built
If the LUTF is built it will be packaged in the lustre-tests
rpm and installed in /usr/lib64/lustre/tests/lutf
.
Test Environment Set-Up
Each node which will run the LUTF will need to have the following installed
- ncurses library
yum install ncurses-devel
- readline library
yum install readline-devel
- python 2.7.5
https://www.python.org/download/releases/2.7.5/
./configure --prefix=<> --enable-shared # it is recommended to install in standard system path
make; make install
- setuptools
- https://pypi.python.org/pypi/setuptools
- The way it worked for me:
- Download package and untar
python2.7 setup.py install
- https://pypi.python.org/pypi/setuptools
- psutils
- https://pypi.python.org/pypi?:action=display&name=psutil
- untar
- cd to untared directory
python2.7 setup.py install
- https://pypi.python.org/pypi?:action=display&name=psutil
- netifaces
- Install PyYAML
The LUTF will also require that passwordless ssh is setup for all the nodes which run the LUTF. This task will fall on the admin.
LUTF/AT Integration
LUTF Deployment
The LUTF will provide a dependency script, lutf_dep.py,
which will download and install all the necessary elements defined above.
The LUTF will integrate with auster. LUTF should just run like any other Lustre test. A bash wrapper script will be created to execute the LUTF.
SIDE NOTE: Since LUTF simply just runs python scripts, it can run any test, including Lustre tests.
Auster
auster
configuration scripts set up the environment variables required for the tests to run. These environment variables identify:
- The nodes involved in the tests
- The devices to use for storage
- The clients
- The PDSH command to use
It also sets a host of specific Lustre environment variables.
It then executes the tests scripts, ex: sanity.sh
sanity.sh
can then run scripts utilizing the information provided in the environment variables.
LUTF and Auster
The LUTF will build on the existing test infrastructure.
An lutf.sh
script will be created, which will be executed from auster
.
auster
will continue to setup the environment variables it does as of the time of this writing. The lutf.sh
will run the LUTF. Since the LUTF is run within the auster
context, the test python scripts will have access to these environment variables and can use them the same way as the bash test scripts do. If LUTF python scripts are executed on the remote node the necessary information from the environment variables are delivered to these scripts.
Test Pre-requisit
Before each test the lutf.sh
will perform the following checks:
- If the master hasn't started, start it.
- If the agents on the nodes specified haven't started, then start them.
- Verify the system is ready to start. IE: master and agents are all started.
Test Post-requisits
It's the responsibility of the test scripts to ensure that the system is in an expected state.
A similar script to auster will be provided by the LUTF, lutf_perform_test.py
. The purpose of the script is to manage which nodes the LUTF will be deployed on. Only the AT has knowledge of the nodes available; therefore the script will perform the following steps;
...
- IP address of node to be used for master
- IP addresses of nodes to be used as agents
- Two YAML configuration files for the Master and Agent nodes.
- YAML configuration file describing the tests to run.
...
- Query the LUTF master to ensure the expected number of agents are connected.
- If everything is correct, then continue with the tests, otherwise build a YAML block describing the error.
...
LUTF Data Flow
Gliffy Diagram | ||||||
---|---|---|---|---|---|---|
|
LUTF Deployment
The LUTF will provide a dependency script, lutf_dep.py,
which will download and install all the necessary elements defined above.
The LUTF will integrate with auster. LUTF should just run like any other Lustre test. A bash wrapper script will be created to execute the LUTF, lutf.sh
.
SIDE NOTE: Since LUTF simply just runs python scripts, it can run any test, including Lustre tests.
Auster
auster
configuration scripts set up the environment variables required for the tests to run. These environment variables include:
- The nodes involved in the tests
- The devices to use for storage
- The clients
- The PDSH command to use
It also sets a host of specific Lustre environment variables.
It then executes the tests scripts, ex: sanity.sh
sanity.sh
can then run scripts utilizing the information provided in the environment variables.
LUTF and Auster
The LUTF will build on the existing test infrastructure.
An lutf.sh
script will be created, which will be executed from auster
.
auster
will continue to setup the environment variables it does as of the time of this writing. The lutf.sh
will run the LUTF. Since the LUTF is run within the auster
context, the test python scripts will have access to these environment variables and can use them the same way as the bash test scripts do. If LUTF python scripts are executed on the remote node the necessary information from the environment variables are delivered to these scripts.
Test Prerequisites
Before each test the lutf.sh
will provide functions to perform the following checks:
- If the master hasn't started, start it.
- If the agents on the nodes specified haven't started, then start them.
- Verify the system is ready to start. IE: master and agents are all started.
Test Post-requisites
- Provide test results in YAML format.
It's the responsibility of the test scripts to ensure that the system is in an expected state; ie: file system unmounted, modules unloaded, etc.
Test Environment Set-Up
Each node which will run the LUTF will need to have the following installed
- ncurses library
yum install ncurses-devel
- readline library
yum install readline-devel
- python 2.7.5
https://www.python.org/download/releases/2.7.5/
./configure --prefix=<> --enable-shared # it is recommended to install in standard system path
make; make install
- setuptools
- https://pypi.python.org/pypi/setuptools
- The way it worked for me:
- Download package and untar
python2.7 setup.py install
- https://pypi.python.org/pypi/setuptools
- psutils
- https://pypi.python.org/pypi?:action=display&name=psutil
- untar
- cd to untared directory
python2.7 setup.py install
- https://pypi.python.org/pypi?:action=display&name=psutil
- netifaces
- Install PyYAML
The LUTF will also require that passwordless ssh is setup for all the nodes which run the LUTF. This task will fall on the admin.
Building the LUTF
The LUTF shall be integrated with the Lustre tests under lustre/tests/lutf
. The LUTF will be built and packaged with the standard
Code Block |
---|
sh ./autogen.sh
./configure --with-linux=<kernel path>
make
# optionally
make rpms
# optionally
make install |
The make system will build the following items:
lutf
binaryliblutf_agent.so
- shared library to communicate with the LUTF backend.clutf_agen.py
and _clutf_agent.so
: glue code that allows python to call functions in liblutf_agent.solnetconfig.py and _lnetconfig.so
- glue code to allow python test scripts to utilize the DLC interface.
The build process will check if python 2.7.5
and SWIG 2.0
or higher is installed before building. If these requirements are not met the LUTF will not be built
If the LUTF is built it will be packaged in the lustre-tests
rpm and installed in /usr/lib64/lustre/tests/lutf
...
.
LUTF Configuration Files
Setup YAML Configuration File
...