Page History
| Table of Contents |
|---|
Introduction
There may be times that you wish to influence the building and testing carried out on your change. You might for example be fixing an issue that affects a particular distribution or combination of distributions, for this reason , CPU architecture, interoperability with a particular Lustre version, or fails only intermittently and needs multiple test runs to confirm it is fixed. To address these needs, you can change or add the tests carried out by indicating in the commit message the changes you require. Test Parameter sessions are -Parameter sessions are normally in addition to to the normal tests test sessions that would be run against a patch. This This allows a patch with specific or unusual testing requirements to ensure that sufficient additional testing is run to gain confidence in the change being made. For patches that are of an experimental nature (i.e. developer is not sure of functionality, or only wants a limited set of tests to be run just to try something), it is also possible to submit a patch with the fortestonly parameterparameter.
To run additional sessions for your patch, add 'Test-Parameters: ' with space-separated name value pairs to your commit message (order within the line does not matter).
For example:
| Code Block | ||
|---|---|---|
| ||
Test-Parameters: testlist=conf-sanity env=ONLY=32 testlist=conf-sanity61,ONLY_REPEAT=20 |
This will cause Autotest to run the normal test sessions plus 1 one additional session where only conf-sanity.sh test #32 will run._61 will run, and it will be repeated 20 times. The parameters specified in Test-Parameters do not affect the existing sessions that are run by default.
Multiple 'Test-Parameters:' lines can be defined, with each Test-Parameters line triggering a separate test session to run in parallel with the default test sessions (parameters are not carried over across multiple lines):
| Code Block | ||
|---|---|---|
| ||
Test-Parameters: testgroup=review-ldiskfs clientdistro=sles12sp3 serverdistro=sles12sp3el9.3 Test-Parameters: testgroup=review-ldiskfs clientdistro=ubuntu1804 serverdistro=el7.9 |
Long lists can be catered for by escaping the carriage return, but are otherwise not subject to the 70-character limit for commit messages:
| Code Block | ||
|---|---|---|
| ||
Test-Parameters: ostcount=2 clients=1 ostsizegb=2 mdssizegb=2 env=SLOW=yes \
testlist=sanity,liblustresanityn |
A single test can be skipped like this one:
| Code Block | ||
|---|---|---|
| ||
Test-Parameters: testlist=hot-pools env=EXCEPT=75c |
which will skip that subtest in the current script, or if multiple test scripts are running then:
| Code Block | ||
|---|---|---|
| ||
Test-Parameters: trivial testlist=hot-pools env=HOT_POOLS_EXCEPT=75c |
Quotations can be used when spaces are Quotations can be used when spaces are necessary in a value:
| Code Block | ||
|---|---|---|
| ||
Test-Parameters: testlist=sanity env=SANITY_EXCEPT="101g 102i" |
The test parameter sessions can be influenced in many ways, see the General Parameters and and Node Parameters sections sections below for all of the options.
| Anchor | ||||
|---|---|---|---|---|
|
...
Build Parameters
Below is the list of general test parameters that can be used to run custom test sessions. These parameters differ from the node_parameters in that these do not need to be specified with a node type prefix.For all of the examples below the 'Test-Parameters:' marker has been omitted to simplify the examplesare build parameters read by Jenkins, and the Lustre Janitor.
...
| Panel | |||||
|---|---|---|---|---|---|
| |||||
Signals to all components the patch is intended for Lustre Janitor testing only. Jenkins will not build the patch (the status will be FAILURE) and therefore, Autotest will not test it. Your patch will not receive a +/- 1 from Maloo Pass through options for auster. Valid values: See "Auster usage help" section on the Setting up a Lustre Test Environment wiki.
|
...
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
Signals to all components the patch should be completely ignored. Jenkins will not build the patch (the status will be FAILURE) and as a result it will not be tested by Autotest or the Lustre Janitor. Your patch will not receive a +/- 1 from Maloo. When true, the MGT will share a partition with an MDT. When false, AT will create an additional partition to be used by just the MGT. NOTE: mdtfilesystemtype will override mgtfilesystemtype when combinedmdsmgs is true. If standalonemgs is set to true, this option will be ignored. Valid values: true, false (no value is the same as true)
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
Comma separated environment definitions passed to the test environment. For definitions requiring spaces, enclose them in quotations. NOTE: Be very careful setting environment variables directly (for example OSTFSTYPE=zfs) because Autotest creates a config file based on the environment it builds. If you ask for something at odds with Autotest's expectations you will see failure instead of success. In this case, for example, you should use the filesystemtype keyword described on this page. Autotest will then create the appropriate environment variables, the same is true for other things like ostcount instead of OSTCOUNT, ostsizegb instead of OSTSIZE, etc. Only use the env parameter when a direct variable is not listed here.
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
Used to specify which node should run the test framework. Default is client1. Valid values: mds1, oss1, client2, etc.
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
Setup cluster in failover configuration Valid values: true, false (no value is the same as true)
|
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
The Supported keywords are
|
| Anchor | ||||
|---|---|---|---|---|
|
General Parameters
Below is the list of general test parameters that can be used to run custom test sessions. These parameters differ from the node_parameters in that these do not need to be specified with a node type prefix.
For all of the examples below the 'Test-Parameters:' marker has been omitted to simplify the examples.
| Panel | |||||
|---|---|---|---|---|---|
| |||||
Pass through options for auster. Valid values: See "Auster usage help" section on the Setting up a Lustre Test Environment wiki.
|
| Anchor | ||||
|---|---|---|---|---|
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
When true, the MGT will share a partition with an MDT. When false, AT will create an additional partition to be used by just the MGT. NOTE: mdtfilesystemtype will override mgtfilesystemtype when combinedmdsmgs is true. If standalonemgs is set to true, this option will be ignored. | |||||
| Panel | |||||
| |||||
Patch will be built by Jenkins but Autotest will not run any testing. Valid values: true, false (no value is the same as true)
|
...
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
Comma separated environment definitions passed to the test environment. For definitions requiring spaces, enclose them in quotations. NOTE: Be very careful setting environment variables directly (for example OSTFSTYPE=zfs) because Autotest creates a config file based on the environment it builds. If you ask for something at odds with Autotest's expectations you will see failure instead of success. In this case, for example, you should use the filesystemtype keyword described on this page. Autotest will then create the appropriate environment variables, the same is true for other things like ostcount instead of OSTCOUNT, ostsizegb instead of OSTSIZE, etc. Only use the The Valid values: true, false (no value is the same as true)
|
...
|
...
| Panel | |||||
|---|---|---|---|---|---|
| |||||
Sets the file system type for all server nodes (MDS, MGS and OSS). NOTE: fstype should not be used in combination with <mdt/mgt/ost>filesystemtypeUsed to specify which node should run the test framework. Default is client1. Valid values: ldiskfs, zfsmds1, oss1, client2, etc.
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
Setup cluster in failover configurationUse iSCSI for failover testing Valid values: 0 (no iSCSI), 1 (iSCSItrue, false (no value is the same as true)
|
| Anchor | ||||
|---|---|---|---|---|
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
For DDN employees only: How to: livedebug | |||||
| |||||
Patch will be built by Jenkins, but Autotest will not run any testing | |||||
| Panel | |||||
| |||||
Sets the size of the partitions on the MDS in GB. Valid values: > 0 and must be an integer. When setting this value, take into consideration your mdtcount value and that most test nodes have ~90GB of disk space.true, false (no value is the same as true)
|
...
|
| Anchor | ||||
|---|---|---|---|---|
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
The Valid values: true, false (no value is the same as true)
|
| Anchor | ||||
|---|---|---|---|---|
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
Sets the file system type for all server nodes (MDS, MGS and OSS). NOTE: fstype should not be used in combination with <mdt/mgt/ost>filesystemtype. Valid values: ldiskfs, zfs
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
Use iSCSI for failover testing Valid values: 0 (no iSCSI), 1 (iSCSI)
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
Set the cluster up to use Kerberos Valid values: true, false (no value is the same as true)
|
| Panel | ||
|---|---|---|
| ||
For DDN employees only: How to: livedebug |
| Anchor | ||||
|---|---|---|---|---|
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
The total number of MDS nodes in the cluster. Valid values: 1 - 8 MDS nodes
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
Sets the size of the partitions on the MDS in GB. Valid values: > 0 and must be an integer. When setting this value, take into consideration your mdtcount value and that most test nodes have ~90GB of disk space.
|
| Anchor | ||||
|---|---|---|---|---|
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
The total number of MDTs spread across all of the MDSs. Valid values: 1 - 4 per MDS
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
Configure the file system type to use on the MDTs. NOTE: <mdt/mgt/ost>filesystemtype should not be used in combination with fstype. Valid values: ldiskfs, zfs
|
...
| Panel | |||||
|---|---|---|---|---|---|
| |||||
The total number of MDTs across all of the MDSs. Valid values: 1 - 4 per MDS
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
Configure the file system type to use on the MDTs. NOTE: <mdt/mgt/ost>filesystemtype should not be used in combination with fstype. Valid values: ldiskfs, zfs
|
...
| Panel | |||||
|---|---|---|---|---|---|
| |||||
Marks the test session as optional: does not impact the verified value from Maloo and is only run if resources are immediately available. Valid values: true, false (no value is the same as true)
|
| Anchor | ||||
|---|---|---|---|---|
|
| Panel | |||||
|---|---|---|---|---|---|
| |||||
The number of OSTs per OSS. Valid values: 1 - 8
|
...
| Anchor | ||||
|---|---|---|---|---|
|
Node Parameters
Node parameters are used to change how specific node types are configured. They must be prefixed with the node type being changed. Valid node types are client, mds, mgs, oss and server. Server is an alias that allows users to modify a value for all server node types (mds, mgs and oss). For example instead of writing
...
| Panel | |||||
|---|---|---|---|---|---|
| |||||
The version of Lustre to use for the specified node type. Version cannot be specified with job and build. If a distro is not specified in the test parameters, Autotest will use the highest el version available for the specified version. Valid values: For a list of valid versions see the Versions section.
Note that in addition to the more commonly used |
| Anchor | ||||
|---|---|---|---|---|
|
Versions
Versions are pointers to job/build combinations and simplify using a specific Lustre version on a test node. Versions can be specified in the test parameters using the the version node node parameter.
The versions in parenthesis auto-update as new versions are added. For example 1.9 will always point to the highest 1.9.x version. EXA1 will always point to the highest EXA1.x.x version.
If there is a version missing, send an email to charlie@whamcloud.com
email to charlie@whamcloud.com
...
| Anchor | ||||
|---|---|---|---|---|
|
Test Groups
Test groups are set lists of Lustre test suites managed by Autotest.
Name | Suites |
|---|---|
clean-downgrade | file_creation_validation |
clean-downgrade-zfs | file_creation_validation |
clean-upgrade | file_creation_validation, file_creation |
clean-upgrade-init | file_creation |
clean-upgrade-init-zfs | file_creation |
clean-upgrade-zfs | file_creation_validation, file_creation |
failover-part-1 | replay-vbr, replay-dual, replay-single, mmp, replay-ost-single, recovery-small, recovery-double-scale |
failover-part-2 | recovery-random-scale |
failover-part-3 | recovery-mds-scale |
failover-zfs-part-1 | replay-vbr, replay-dual, replay-single, mmp, replay-ost-single, recovery-small, recovery-double-scale |
failover-zfs-part-2 | recovery-random-scale |
failover-zfs-part-3 | recovery-mds-scale |
full-dkms | sanity-scrub, replay-single, obdfilter-survey, replay-ost-single, large-scale, insanity, parallel-scale, runtests, replay-dual, sanity-flr, sanity-lsnapshot, mmp, sanity-dom, mds-survey, sanity-lfsck, sanity-lnet, pjdfstest, ost-pools, recovery-small |
full-dne-part-1 | sanity-scrub, replay-single, obdfilter-survey, replay-ost-single, large-scale, insanity, parallel-scale, runtests, replay-dual, sanity-flr, sanity-lsnapshot, mmp, sanity-dom, mds-survey, sanity-lfsck, sanity-lnet, pjdfstest, ost-pools, recovery-small |
full-dne-part-2 | lnet-selftest, sanity, sanity-hsm, lustre-rsync-test, sanity-sec, replay-vbr, parallel-scale-nfsv3, sanity-quota, sanity-pcc, racer |
full-dne-part-3 | sanity-pfl, performance-sanity, sanity-benchmark, conf-sanity, sanityn, parallel-scale-nfsv4, hot-pools, sanity-lipe |
full-dne-part-exa6 | sanity-lipe-find3, sanity-lipe-scan3, sanity-compr |
full-dne-zfs-part-1 | sanity-scrub, replay-single, obdfilter-survey, replay-ost-single, large-scale, insanity, parallel-scale, runtests, replay-dual, sanity-flr, sanity-lsnapshot, mmp, sanity-dom, mds-survey, sanity-lfsck, sanity-lnet, pjdfstest, ost-pools, recovery-small |
full-dne-zfs-part-2 | lnet-selftest, sanity, sanity-hsm, lustre-rsync-test, sanity-sec, replay-vbr, parallel-scale-nfsv3, sanity-quota, sanity-pcc, racer |
full-dne-zfs-part-3 | sanity-pfl, performance-sanity, sanity-benchmark, conf-sanity, sanityn, parallel-scale-nfsv4, hot-pools, sanity-lipe |
full-dne-zfs-part-exa6 | sanity-lipe-find3, sanity-lipe-scan3, sanity-compr |
full |
Test groups are set lists of Lustre test suites managed by Autotest.
Name
Suites
basic
conf-sanity
failover-part-1
replay-vbr, replay-dual, replay-single, mmp, replay-ost-single, recovery-small, recovery-double-scale
failover-part-2
recovery-random-scale
failover-part-3
recovery-mds-scale
failover-zfs-part-1
replay-vbr, replay-dual, replay-single, mmp, replay-ost-single, recovery-small, recovery-double-scale
failover-zfs-part-2
recovery-random-scale
failover-zfs-part-3
recovery-mds-scale
-part-1 | sanity-scrub, replay-single, obdfilter-survey, replay-ost-single, large-scale, insanity, parallel-scale, runtests, replay-dual, sanity-flr, sanity-lsnapshot, mmp, sanity-dom, mds-survey, sanity-lfsck, sanity-lnet, pjdfstest, ost-pools, recovery-small |
full |
-part-2 | lnet-selftest, sanity, sanity-hsm, lustre-rsync-test, sanity-sec, replay-vbr, parallel-scale-nfsv3, sanity-quota, sanity-pcc |
, racer |
full |
-part-3 | sanity-pfl, performance-sanity, sanity-benchmark, conf-sanity, sanityn, parallel-scale-nfsv4, hot-pools, sanity-lipe |
full-part-exa6 | sanity-lipe-find3, sanity-lipe-scan3, sanity-compr |
full- |
patchless | lnet-selftest, runtests, sanity, sanity-scrub, sanity-benchmark, sanity-lfsck, sanityn, sanity-hsm, sanity-flr, sanity-dom, sanity-lsnapshot, |
insanity, sanity- |
quota, |
sanity- |
sec, sanity- |
pfl, |
lustre-rsync- |
test, |
ost-pools, |
full-dne-zfs-part-2
mds-survey, mmp, performance-sanity, parallel-scale, large-scale, obdfilter-survey, parallel-scale-nfsv3, |
parallel-scale- |
nfsv4, |
pjdfstest, sanity |
- |
lnet, racer |
full |
-zfs- |
dkms | sanity-scrub, replay- |
single, |
obdfilter- |
survey, |
replay-ost- |
single, |
large- |
scale, |
insanity, parallel-scale |
, runtests, replay-dual, sanity-flr, sanity-lsnapshot, mmp, sanity-dom, mds-survey, sanity- |
lfsck, sanity |
-lnet, pjdfstest, ost-pools, recovery-small |
full-zfs |
-part-1 | sanity-scrub, replay-single, obdfilter-survey, replay-ost-single, large-scale, insanity, parallel-scale, runtests, replay-dual, sanity-flr, sanity-lsnapshot, mmp, sanity-dom, mds-survey, sanity-lfsck, sanity-lnet, pjdfstest, ost-pools, recovery-small |
full-zfs-part-2 | lnet-selftest, sanity, sanity-hsm, lustre-rsync-test, sanity-sec, replay-vbr, parallel-scale-nfsv3, sanity-quota, sanity-pcc |
, racer | |
full-zfs-part-3 | sanity-pfl, performance-sanity, sanity-benchmark, conf-sanity, sanityn, parallel-scale-nfsv4, hot-pools, sanity-lipe |
full-zfs-part-exa6 | sanity-lipe-find3, sanity-lipe-scan3 |
, sanity-compr |
lnet-review-ldiskfs-dne |
lnet-selftest |
, sanity, sanity- |
lnet, sanity- |
sec | |
lustrefs_exporter | lustrefs_exporter |
review | lnet-selftest, runtests, sanity |
, sanityn, |
replay- |
single, conf-sanity, recovery- |
small, |
replay- |
ost- |
single, insanity, sanity-quota |
, lustre-rsync-test, ost-pools, |
sanity- |
lfsck, |
sanity |
-hsm, sanity-lnet |
review-dne-exa6-part-1 |
sanity- |
pcc, |
sanity- |
sec, |
sanity-lipe- |
scan3, |
sanity-lipe-find3 | |
review-dne-exa6-part-2 | sanity-compr |
review-dne-part-1 | sanity, sanity-pfl |
review-dne-part-2 | mds-survey, replay-dual, runtests, sanity-lfsck, sanity-sec |
review-dne-part-3 | conf-sanity |
review-dne-part-4 | insanity, mmp |
full-zfs-part-1
, replay-ost-single, |
sanity- |
dom, sanity-flr, sanity- |
hsm, sanity |
-quota | |
review-dne-part-5 | lustre-rsync-test, recovery-small |
, sanity-scrub, sanityn |
review-dne |
-part- |
6 | replay-single, ost-pools |
review-dne-part-7 | large-scale, hot-pools, sanity-pcc, sanity-lipe |
review-dne-part-8 | replay-vbr, replay-dual |
review-dne |
-part- |
9 |
obdfilter- |
survey, performance-sanity, sanity-benchmark, |
parallel- |
scale, parallel-scale-nfsv4, |
parallel-scale- |
lnet-review-ldiskfs-dne
lnet-selftest, sanity, sanity-lnet, sanity-sec
review
nfsv3, racer | |
review-dne-selinux-ssk-part-1 | sanity |
review-dne-selinux-ssk-part-2 | recovery-small, sanity-sec, sanity-selinux |
review-dne-zfs | runtests, sanity, sanityn, replay-single, conf-sanity, recovery-small, replay-ost-single, insanity, sanity-quota, lustre-rsync-test, ost-pools, sanity-lfsck, sanity-hsm |
review-dne-zfs-part-1 | sanity, sanity-pfl |
review-dne-zfs-part-2 | mds-survey, replay-dual, runtests, sanity-lfsck, sanity-sec |
review-dne-zfs-part-3 | conf-sanity |
review-dne-zfs-part-4 | insanity, mmp, replay-ost-single, sanity-dom, sanity-flr, sanity-hsm, sanity-quota |
review-dne-zfs-part-5 | lustre-rsync-test, recovery-small, sanity-scrub, sanityn |
review-dne-zfs-part-6 | replay-single, ost-pools |
review-dne-zfs-part-7 | large-scale, hot-pools, sanity-pcc |
review-dne-part-8
parallel-scale, replay-vbr, replay-dual, racer
review-dne-part-9
obdfilter-survey, performance-sanity, sanity-benchmark, parallel-scale-nfsv4, parallel-scale-nfsv3
, sanity-lipe | |
review-e2fsprogs-part-1 | conf-sanity |
review-e2fsprogs- |
part-2 | sanity, mmp |
review-exa6-part- |
1 |
sanity- |
pcc, sanity-sec, sanity |
-lipe-scan3, sanity-lipe-find3 |
review- |
exa6-part- |
2 |
sanity |
-compr | |
review-ldiskfs | lnet-selftest, sanity, sanity-lnet |
review-ldiskfs-arm | lnet-selftest, sanity, sanity-lnet |
review-ldiskfs-dne | lnet-selftest, sanity, sanity-lnet |
review-ldiskfs-dne-arm | lnet-selftest, sanity, sanity-lnet |
review-ldiskfs-ubuntu | lnet-selftest, sanity, sanity-lnet |
review-zfs | sanity-quota, sanity-flr, replay-single, replay-ost-single, insanity |
review-zfs-part-1 | runtests, sanity, sanityn, sanity-quota, ost-pools, sanity-lfsck, sanity-hsm, sanity-flr |
review-zfs-part-2 | replay-single, conf-sanity, recovery-small, replay-ost-single, insanity, lustre-rsync-test, large-scale, mds-survey |
rolling-downgrade-client1 | sanity |
rolling-downgrade-client1-zfs | sanity |
rolling-downgrade-client2 | sanity |
rolling-downgrade-client2-zfs | sanity |
rolling-downgrade-mds | sanity |
rolling-downgrade-mds-zfs | sanity |
rolling-downgrade-oss | sanity |
rolling-downgrade-oss-zfs | sanity |
rolling-upgrade-client1 | sanity |
rolling-upgrade-client1-zfs | sanity |
rolling-upgrade-client2 | sanity |
rolling-upgrade-client2-zfs | sanity |
rolling-upgrade-init | sanity |
rolling-upgrade-init-zfs | sanity |
rolling-upgrade-mds | sanity |
rolling-upgrade-mds-zfs | sanity |
rolling-upgrade-oss | sanity |
rolling-upgrade-oss-zfs | sanity |
review-dne-zfs-part-1
sanity, sanity-pfl
review-dne-zfs-part-2
mds-survey, replay-dual, runtests, sanity-lfsck, sanity-sec
review-dne-zfs-part-3
conf-sanity
review-dne-zfs-part-4
insanity, mmp, replay-ost-single, sanity-dom, sanity-flr, sanity-hsm, sanity-quota
review-dne-zfs-part-5
lustre-rsync-test, recovery-small, sanity-scrub, sanityn
review-dne-zfs-part-6
replay-single, ost-pools
review-dne-zfs-part-7
large-scale, hot-pools, sanity-pcc, sanity-lipe
review-exa6
sanity-pcc, sanity-sec
review-ldiskfs
lnet-selftest, sanity, sanity-lnet
review-ldiskfs-arm
lnet-selftest, sanity, sanity-lnet
review-ldiskfs-dne
lnet-selftest, sanity, sanity-lnet
review-ldiskfs-dne-arm
lnet-selftest, sanity, sanity-lnet
review-ldiskfs-ubuntu
lnet-selftest, sanity, sanity-lnet
review-zfs
sanity-quota, sanity-flr, replay-single, replay-ost-single, insanity
review-zfs-part-1
runtests, sanity, sanityn, sanity-quota, ost-pools, sanity-lfsck, sanity-hsm, sanity-flr
review-zfs-part-2
replay-single, conf-sanity, recovery-small, replay-ost-single, insanity, lustre-rsync-test, large-scale, mds-survey
tiny
Overview
Content Tools