Test-Parameters: testlist=conf-sanity env=ONLY=32 testlist=conf-sanity61,ONLY_REPEAT=20

Test-Parameters: testgroup=review-ldiskfs clientdistro=sles12sp3 serverdistro=sles12sp3el9.3
Test-Parameters: testgroup=review-ldiskfs clientdistro=ubuntu1804 serverdistro=el7.9

Test-Parameters: ostcount=2 clients=1 ostsizegb=2 mdssizegb=2 env=SLOW=yes \
                 testlist=sanity,liblustresanityn

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.

austeroptions=-R

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)

# creates a shared partition to be used by the MGT and a MDT - typically not necessary since this is the default
combinedmdsmgs
# or
combinedmdsmgs=true

# creates an additional partition to be used by the MGT
combinedmdsmgs=false

Patch will be built by Jenkins, but Autotest will not run any testingThe total number of MDTs across all of the MDSs.

Valid values: 1 - 4 per MDStrue, false (no value is the same as true)

# createmark build 4as MDTsfor perbuild MDS
mdscount=2 mdtcount=8only
forbuildonly
# or
forbuildonly=true

# create 1 MDT per MDS
mdscount=4 mdtcount=4disable forbuildonly - typically not necessary since the default is false
forbuildonly=false

The fortestonly parameter marks that the patch is  not intended for landing . Any testlist= specified with Test-Parameters: fortestonly will replace the default tests that will be run, so it is possible to run only a subset of tests.  Patches marked with fortestonly will not receive the Verified +1 label from Maloo and cannot be landed. In order to land such a patch, it should be rebased and submitted without the fortestonly keyword once the patch is known to be good, or the commit comment in Gerrit should be edited to remove the fortestonly label which will rebuild and retest the patch and will preserve any reviews that the patch has received).

Valid values: true, false (no value is the same as true)

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

# configuremark build theas MDTsfor to use zfs
mdtfilesystemtype=zfstest only
fortestonly
# or
fortestonly=true

# configure the MDTs to use ldiskfs
mdtfilesystemype=ldiskfs

# this may result in an unexpected configuration
fstype=zfs mdtfilesystemtype=ldiskfsmark patch as experimental and run only a custom list of test
fortestonly testlist=conf-sanity

# disable fortestonly - typically not necessary since the default is false
fortestonly=false

Use iSCSI for failover testing

Valid values: 0 (no iSCSI), 1 (iSCSI)

# do not setup iscsi
iscsi=0

# setup iscsi
iscsi=1

The total number of OSTs per OSSMDS nodes in the cluster.

Valid values: 1 - 8 MDS nodes

# create 8 OSTs per OSS
osscount2 MDS nodes with 4 MDTs each
mdscount=2 ostcountmdtcount=8

# create 4 MDS OSTsnodes per OSS
osscountwith 1 MDT each
mdscount=4 ostcountmdtcount=4

Sets the size of the partitions on the MDS in GB

Configure the file system type to use on the OSTs.

NOTE: <mdt/mgt/ost>filesystemtype should not be used in combination with fstype.

Valid values: ldiskfs, zfs> 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.

# configure the2GB OSTspartitions toon usethe zfsMDS
ostfilesystemtypemdssizegb=zfs

# configure the OSTs to use ldiskfs
ostfilesystemype=ldiskfs2

Configure the file system type to use on the MDTs.

NOTE: <mdt/mgt/ost>filesystemtype should not be used in combination with fstypeSets the size of the partitions on the OSS in GB.

Valid values: > 0 and must be an integer. When setting this value, take into consideration your ostcount value and that most test nodes have ~90GB of disk space.ldiskfs, zfs

# configure 2GBthe partitionsMDTs onto theuse OSSzfs
ostsizegbmdtfilesystemtype=2

Specifies the subproject of the patch. Subprojects must be added by Autotest Admin, currently the only configured subproject is lnetMarks the test session as optional: does not impact the verified value from Maloo and is only run if resources are immediately available.

Valid values: lnettrue, false (no value is the same as true)

# configurerun theoptional session towith runsome theexperimental lnet subproject test sessions
@lnet
# or
subproject=lnetsettings
optional testlist=sanity env=FSNAME=lus12345

The number of OSTs per OSS.

Valid values: 1 - 8

Configure the test session to run a specific test group. Specifying a test group makes it easy to run a typical test grouping with small modifications since the session will inherit all of the values from the base test with any overrides applied (see the code block below for examples).

NOTE: testgroup can be combined with testlist to run a test group plus additional suites

Valid values: See the Test Groups section for a complete list

# runcreate a8 typicalOSTs review-ldiskfs session with a stand alone MGS
testgroup=review-ldiskfs standalonemgsper OSS
osscount=2 ostcount=8

# runcreate failover4 withOSTs a specific server version
testgroup=failover serverversion=2.11.50

# run review-dne-part-1 with additional suites
testgroup=review-dne-part-1 testlist=sanity-lfsck,sanity-sec

Configures the session to re-provision all of the nodes instead of simply reboot themWhen true, Autotest will continue the session after a suite crashes. The session will continue with the suite following the one that crashed. When false, Autotest will stop the session and upload the results to Maloo immediately.

Valid values: true, false (no value is the same as true)

# re-provision nodes configure the session to continue after a timeout
timeoutreprovisionsuite crashes - typically not necessary since the default is true
resumeaftercrash
# or
timeoutreprovisionresumeaftercrash=true

# rebootconfigure the session nodesto stop after a timeout - typically not necessary since reboot is the default
timeoutreprovision=falsesuite crashes
resumeaftercrash=false

The trivial keyword can be Marks the session as enforcing: is used to reduce the testing time (both wall-clock time as well as total test system hours) for patches that do not affect code functionality, such as changes to whitespace, comments, man pages, and test scripts (in conjunction with the testlist keyword to ensure the modified test script is run if it isn't already).  Patches marked with trivial in the Test-Parameters: list will run the review-ldiskfs test session instead of the regular tests, so it currently runs only sanity and lnet-selftest to ensure basic functionality.  If changes are only being made to a test script outside of those already run by default, an additional testlist=<test-script(s)>keyword should be added with a comma-separated list of modified tests to ensure they are run to validate the changes.  The trivial keyword will reduce the test completion time from approximately 10h elapsed and 30h of total test system time to approximately 3h elapsed/system time.  This saves test system resources that may be better spent on other patches.determine the verified value from Maloo.

Valid values: true, false (no value is the same as true)

# mark the session as enforcing - typically not needed since the default is true
signofftest
# or
signofftest=true

# mark the session as not enforcing
signofftest=false

Configure the test session to run a specific list of suites. testlist can be combined with testgroup to run a test group plus additional suites.

Valid values: sanity, sanityn, conf-sanity, mmp, replay-single, replay-dual, lnet-selftest, etc.

The number of nodes to use for the specified node type.

NOTE: For MDS and OSS nodes, it's best to also set mdtcount / ostcount to ensure you have the expected number of targets.

Valid values:

Distribution to use for the specified node typeConfigures the session to re-provision all of the nodes instead of simply reboot them.

Valid values: el7, el7.5, el7.6, ubuntu1604, ubuntu1804, sles12sp3, etc. (The distribution specified must have been built for the patch being tested. The distros built can be seen on the patch's build page in Jenkins.true, false (no value is the same as true)

# specifyre-provision thenodes clientafter to use el7 and all servers sles12sp3
clientdistro=el7 serverdistro=sles12sp3a timeout
timeoutreprovision
# or
timeoutreprovision=true

# specifyreboot the clientnodes toafter usea ubuntu1804,timeout MDS- totypically usenot el7necessary andsince OSSreboot tois usethe sles12sp3default
clientdistro=ubuntu1804 mdsdistro=el7 ossdistro=sles12sp3timeoutreprovision=false

The IB stack to use for the specified node type.

Valid values: inkernel, ofa (The IB stack type must have been built for the build being tested. The stack types can be seen on the patch's build page in Jenkins.)

clientibstack=inkernel

The trivial keyword can be used to reduce the testing time (both wall-clock time as well as total test system hours) for patches that do not affect code functionality, such as changes to whitespace, comments, man pages, and test scripts (in conjunction with the testlist keyword to ensure the modified test script is run if it isn't already).  Patches marked with trivial in the Test-Parameters: list will run the review-ldiskfs test session instead of the regular tests, so it currently runs only  sanity  and  lnet-selftest  to ensure basic functionality.  If changes are only being made to a test script outside of those already run by default, an additional testlist=<test-script(s)>keyword should be added with a comma-separated list of modified tests to ensure they are run to validate the changes.  The trivial keyword will reduce the test completion time from approximately 10h elapsed and 30h of total test system time to approximately 3h elapsed/system time.  This saves test system resources that may be better spent on other patches

mdsdistro=el7 mgsdistro=el7 ossdistro=el7