Testing HOWTO

From Lustre Wiki
Jump to: navigation, search

This HOWTO is intended to demonstrate the basics of configuring and running tests on a multi-node configuration. There are many tests available in the Lustre Test Suites, and the principles demonstrated in configuring your system and running the sanity test suite will apply to them all. We will also demonstrate adding additional configuration for feature specific test suites.

While these examples do use virtual machines, they are merely examples and the specifics should be easy to apply to real hardware with the prerequisites setup.

System Configuration

This HOWTO uses a cluster of six virtual machines running CentOS 7.1 with a recent lustre-master build to run the Lustre tests. Two clients, two MDS, two OSS. This enables testing of a wide variety of Lustre features.

  • node01 - MGS and MDS - 192.168.56.201
    • 1GB MGT/MDT - /dev/sdb
  • node02 - MDS - 192.168.56.202
    • 1GB MDT - /dev/sdb
  • node03 - OSS - 192.168.56.203
    • Four 16GB OST - /dev/sdb, /dev/sdc, /dev/sdd, /dev/sde
  • node04 - OSS - 192.168.56.204
    • Four 16GB OST - /dev/sdb, /dev/sdc, /dev/sdd, /dev/sde
  • node05 - client - 192.168.56.205
    • 16GB shared directory for tests and results
  • node06 - client - 192.168.56.206

System Setup

  • Install the Lustre client packages on two machines, and the Lustre server packages on the other four, using the same version of Lustre
  • Disable SELINUX
    • Set SELINUX=disabled in /etc/sysconfig/selinux
  • Disable the firewall
    • service firewalld stop && systemctl disable firewalld.service
  • Generate passwordless ssh keys for hosts and exchange identities across all nodes, and also accept the host fingerprints
    • The goal is to be able to pdsh using ssh from all machines without requiring any user input
  • Install PDSH and ensure you can execute commands across the cluster
  • Install the epel-release package to enable the EPEL repo
  • Install the net-tools package for netstat
  • Add user 'runas' with UID 500 and GID 500 to all the nodes
  • Create an NFS share that is mounted on all the nodes
    • A small number of tests will make use of a shared storage location
  • Configure hostnames and populate /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.56.201	node01
192.168.56.202	node02
192.168.56.203	node03
192.168.56.204	node04
192.168.56.205	node05
192.168.56.206	node06

Installing Additional Applications for Testing

Test Configuration

There is a configuration distributed with the Lustre test suite, local.sh, that easily enables you to test Lustre on a single node using loopback devices with no additional configuration needed. This works well, and tests the Lustre software, but the purpose of this HOWTO is to demonstrate using multiple servers and clients to test more Lustre features in an environment representative of a real install.

Fortunately many of the default environment variables required are defined in local.sh, so we can define the specifics for our system and then source local.sh. If you're using multiple clients, we should source the ncli.sh configuration which ultimately sources local.sh but also has some functions to setup a multiple client environment.

Install this configuration file in /usr/lib64/lustre/tests/cfg/multinode.sh on all of the nodes.

# MDS and MDT configuration
MDSCOUNT=2

mds_HOST="node01"
MDSDEV1="/dev/sdb"

mds2_HOST="node02"
MDSDEV2="/dev/sdb"

# OSS and OST configuration
OSTCOUNT=8

ost_HOST="node03"
OSTDEV1="/dev/sdb"

ost2_HOST="node03"
OSTDEV2="/dev/sdc"

ost3_HOST="node03"
OSTDEV3="/dev/sdd"

ost4_HOST="node03"
OSTDEV4="/dev/sde"

ost5_HOST="node04"
OSTDEV5="/dev/sdb"

ost6_HOST="node04"
OSTDEV6="/dev/sdc"

ost7_HOST="node04"
OSTDEV7="/dev/sdd"

ost8_HOST="node04"
OSTDEV8="/dev/sde"

# Client configuration
CLIENTCOUNT=2
RCLIENTS="node05 node06"

PDSH="/usr/bin/pdsh -S -Rssh -w"

SHARED_DIRECTORY=${SHARED_DIRECTORY:-/opt/testing/shared}

. /usr/lib64/lustre/tests/cfg/ncli.sh

Running the Tests

Now you are ready to run the tests. I recommend by starting with one single subtest to check that you have everything configured correctly.

Run this command from the client1 node (node05 in this example) to launch the sanity test, running only test 0.

auster is the tool used to drive the tests. In this example we are passing the flags

  • -f multinode - use the multinode.sh configuration in /usr/lib64/lustre/tests/cfg/ when running the tests
  • -r - allow the tests to reformat the devices
  • -s - run the SLOW tests, which are skipped if we don't pass this flag
  • -v - provide verbose output
  • sanity --only 0 - run the sanity tests, but only test 0a
[root@node05 tests]# pwd
/usr/lib64/lustre/tests
[root@node05 tests]# ./auster -f multinode -rsv -d /opt/results/ sanity --only 0a

You will see a lot of output while the tests format the targets, start the filesystem, and mount it on the clients.

You will see this output if the test successfully runs:

== sanity test 0a: touch; rm ========================================================================= 11:17:34 (1441210654)
/mnt/testfs/f0a.sanity has type file OK
/mnt/testfs/f0a.sanity: absent OK
Resetting fail_loc on all nodes...done.
PASS 0a (1s)
== sanity test complete, duration 6 sec ============================================================== 11:17:35 (1441210655)

Now you're ready to run the full sanity test. Just remove the --only flag to auster:

[root@node05 tests]# pwd
/usr/lib64/lustre/tests
[root@node05 tests]# ./auster -f multinode -rsv -d /opt/results/ sanity

Running sanity with the -s flag takes about 1h32m in the virtual machine cluster on my computer.

Test Output

By default, auster will write output to
 /tmp/test_logs/<date>/<time>/ 
The -d flag directed auster to store the results in the base directory /opt/results/. auster will create
 /opt/results/<date>/<time>/ 
directories. Inside the directory corresponding to your test run, you'll find the test output.

Adding Additional Configuration for sanity-hsm

Now that we are able to run the sanity test suite, we can expand our testing by running additional test suites. For example, you may want to test the HSM feature of lustre. This is covered by the sanity-hsm test suite.

The sanity-hsm needs some additional configuration to the basic file we created earlier.

In particular, we now need a client that will act as a agent for the HSM copying, and a filesystem to archive files to.

We will add node07 to our setup.

  • node07 - client/HSM agent - 192.168.56.207
    • 8GB filesystem formatted ext4 and mounted at /archive - /dev/sdb

Add this machine to our hosts file:

192.168.56.207	node07

Expand the RCLIENTS definition to include node07:

RCLIENTS="node05 node06 node07"

Add additional environment variables to our multinode.sh configuration file for sanity-hsm:

AGTDEV1=/archive 
agt1_HOST=node07
HSMTOOL_VERBOSE="-v -v -v -v -v -v"

Our system is now setup to run the sanity-hsm test suite. This is the auster command you would run to start the test:

[root@node05 tests]# pwd
/usr/lib64/lustre/tests
[root@node05 tests]# ./auster -f multinode -rsv -d /opt/results/ sanity-hsm