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, 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 normally in addition to the normal test sessions that would be run against a patch. 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 parameter.

...

Code Block

theme	Midnight

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

theme	Midnight

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

theme	Midnight

Test-Parameters: trivial testlist=hot-pools env=HOT_POOLS_EXCEPT=75c

Quotations can be used when spaces are necessary in a value:

...

The test parameter sessions can be influenced in many ways, see the the General Parameters and Node Parameters sections below for all of the options.

...

Anchor

	build_parameters
	build_parameters

Build Parameters

Below are build parameters read by Jenkins, and the Lustre Janitor.

...

Panel

title	ignore \| flag

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.

Code Block

theme	Midnight

Test-Parameters: ignore

...

Panel

...

title	Build-Parameters:

The Build-Parameters: directive can limit the architecture/distribution combinations that will be built for a specific patch to only the specified list. This can be useful in some cases where a large number of patches will be pushed in a series, or when doing bisection testing to isolate a failure to a specific patch. Note, however, that this only filters the arch/disto combinations from what would normally be built, it cannot add arch/distro combinations that would not otherwise be built for a branch. Also note that there is not (currently) any coordination between the arch/distro combination that is built and what is tested, so this may also require corresponding "Test-Parameters: ... distro=XXXX arch=YYYY" directives to align the test sessions with the subset of packages being built, including the trivial test sessions that are always run, or use fortestonly to restrict test sessions to only those that are specified. Use with caution.

Supported keywords are arch and distro that affect both the client and server, or clientarch/clientdistro and serverarch/serverdistro to specify only the client and server builds (one set per line).

Code Block

theme	Midnight

Build-Parameters: clientdistro=el9.4 clientarch=aarch64
Build-Parameters: distro=el9.5 arch=x86_64
Build-Parameters: clientdistro=el8.10 arch=x86_64
Test-Parameters: fortestonly
Test-Parameters: kerberos=true testlist=sanity-krb5 clientdistro=el8.10 serverdistro=el9.5
Test-Parameters: kerberos=true testlist=sanity-krb5 clientdistro=el9.4 clientarch=aarch64 serverdistro=el9.5
Test-Parameters: kerberos=true testlist=sanity-krb5 clientdistro=el9.5 serverdistro=el9.5

Anchor

	general_parameters
	general_parameters

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

title	austeroptions \| String

Pass through options for auster.

Valid values: See "Auster usage help" section on the Setting up a Lustre Test Environment wiki

...

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

title	austeroptions \| String

Pass through options for auster.

Valid values: See "Auster usage help" section on the Setting up a Lustre Test Environment wiki.

Code Block

theme	Midnight

austeroptions=-R

...

Panel

title	combinedmdsmgs \| Boolean

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)

Code Block

theme	Midnight

# 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

Panel

title	env, envdefinitions \| String

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.

Code Block

theme	Midnight

env=SLOW=yes
envdefinitions=SLOW=yes

# multiple definitions
env=ONLY=123,HONOR_EXCEPT=y

# one with spaces that must be enclosed in quotations
env=SLOW=yes,SANITY_EXCEPT="101g 102i"

austeroptions=-R

Anchor

	combinedmdsmgs
	combinedmdsmgs

Panel

title	combinedmdsmgs \| Boolean

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

title	facet \| String

Used to specify which node should run the test framework. Default is client1.

Valid values: mds1, oss1, client2, etc.

Code Block

theme	Midnight

# specify mds1 as the facet
facet=mds1 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

# invalid facet value, will cause creates an erroradditional messagepartition to be postedused toby the Gerrit reviewMGT
mdscount=1 facet=mds2combinedmdsmgs=false

Panel

title	failover env, envdefinitions \| Boolean

Setup cluster in failover configuration

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

Code Block

theme	Midnight

# enable failover
failover
# or
failover=true

# disable failover setup
failover=false

...

String

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.

Code Block

theme	Midnight

env=SLOW=yes
envdefinitions=SLOW=yes

# multiple definitions
env=ONLY=123,HONOR_EXCEPT=y

# one with spaces that must be enclosed in quotations
env=SLOW=yes,SANITY_EXCEPT="101g 102i"

Panel

title	facet \| String

Used to specify which node should run the test framework. Default is client1.

Valid values: mds1, oss1, client2, etc.

Code Block

theme	Midnight

# specify mds1 as the facet
facet=mds1

# invalid facet value, will cause an error message to be posted to the Gerrit review
mdscount=1 facet=mds2

Panel

title	failover \| Boolean

Setup cluster in failover configuration

...

Panel

title	forbuildonly \| Boolean

Patch will be built by Jenkins, but Autotest will not run any testing.

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

Code Block

theme	Midnight

# mark build as for build only
forbuildonly
# or
forbuildonly=true

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

...

Panel

title	fortestonly \| Boolean

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)

Code Block

theme	Midnight

# mark build as for test only
fortestonlyenable failover
failover
# or
fortestonlyfailover=true

# markdisable failover setup
failover=false

Anchor

	forbuildonly
	forbuildonly

Panel

title	forbuildonly \| Boolean

Patch will be built by Jenkins, but Autotest will not run any testing.

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

Code Block

theme	Midnight

# mark build as for build only
forbuildonly
# or
forbuildonly=truepatch as experimental and run only a custom list of test
fortestonly testlist=conf-sanity

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

Anchor

	fstypefortestonlyfstype
	fortestonly

Panel

title	fstype fortestonly \| String

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

Code Block

theme	Midnight

# set all server nodes to use zfs
fstype=zfs

# set all server nodes to use ldiskfs
fstype=ldiskfs

# this may result in an unexpected configuration
fstype=zfs mdtfilesystemtype=ldiskfs

Boolean

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

Panel

title	iscsi \| boolean

Use iSCSI for failover testing

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

Code Block

theme	Midnight

# do not setup iscsi
iscsi=0 mark build as for test only
fortestonly
# or
fortestonly=true

# setup iscsi
iscsi=1

Panel

title	kerberos \| boolean

Set the cluster up to use Kerberos

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

Code Block

theme	Midnight

# setup kerberos
kerberos
# or
kerberos=true

# do not setup kerberos
kerberos=false

Panel

title	livedebug

For DDN employees only: How to: livedebug

...

mark 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

Anchor

	fstype
	fstype

Panel

title	fstype \| String

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

title	mdscount \| Integer

The total number of MDS nodes in the cluster.

Valid values: 1 - 8 MDS nodes

Code Block

theme	Midnight

# createset 2all MDSserver nodes withto 4use MDTs eachzfs
mdscount=2 mdtcount=8fstype=zfs

# createset 4all MDSserver nodes with 1 MDT each
mdscount=4 mdtcount=4 to use ldiskfs
fstype=ldiskfs

# this may result in an unexpected configuration
fstype=zfs mdtfilesystemtype=ldiskfs

Panel

title	mdssizegb iscsi \| Integerboolean

Use iSCSI for failover testingSets 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.

Code Block

theme	Midnight

# configure 2GB partitions on the MDS
mdssizegb=2

...

0 (no iSCSI), 1 (iSCSI)

Code Block

theme	Midnight

# do not setup iscsi
iscsi=0

# setup iscsi
iscsi=1

Panel

title	kerberos \| boolean

Set the cluster up to use Kerberos

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

...

Panel

title	mdtcount \| Integer

The total number of MDTs spread across all of the MDSs.

Valid values: 1 - 4 per MDS

Code Block

theme	Midnight

# create 4 MDTs per MDS
mdscount=2 mdtcount=8setup kerberos
kerberos
# or
kerberos=true

# createdo 1not MDTsetup per MDSkerberos
mdscount=4 mdtcount=4kerberos=false

Panel

title	mdtfilesystemtype \| String	livedebug

For DDN employees only: How to: livedebug

Anchor

	mdscount
	mdscount

Panel

title	mdscount \| Integer

The total number of MDS nodes in the cluster

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, zfs1 - 8 MDS nodes

Code Block

theme	Midnight

# configurecreate the2 MDTsMDS tonodes use zfs
mdtfilesystemtype=zfs

# configure thewith 4 MDTs to use ldiskfs
mdtfilesystemype=ldiskfseach
mdscount=2 mdtcount=8

# create this4 mayMDS resultnodes inwith an1 unexpectedMDT configurationeach
fstypemdscount=zfs4 mdtfilesystemtypemdtcount=ldiskfs4

Panel

title	mgssizegb mdssizegb \| Integer

Sets the size of the partition partitions on the MGS MDS in GB. This value is only applicable when the session is using a stand alone MGS.

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.

Code Block

theme	Midnight

# configure a 2GB partitionpartitions on the MGSMDS
mgssizegbmdssizegb=2

Anchor

	mdtcount
	mdtcount

Panel

title	mgtfilesystemtype \| String	mdtcount \| Integer

The total number of MDTs spread across all of the MDSs.

Valid values: 1 - 4 per MDS

Configure the file system type to use on the MGTs.

NOTE: The default value for combinedmdsmgs is true, therefore it must be set to false in order to configure a different file system type for the MGT. Also, <mdt/mgt/ost>filesystemtype should not be used in combination with fstype.

Valid values: ldiskfs, zfs

Code Block

theme	Midnight

# configurecreate the4 MGTsMDTs toper use zfsMDS
mgtfilesystemtypemdscount=zfs2 combinedmdsmgsmdtcount=8

# create 1 MDT per MDS
mdscount=4 mdtcount=4

Panel

title	mdtfilesystemtype \| String

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

Code Block

theme	Midnight

false

# configure the MGTsMDTs to use ldiskfszfs
mgtfilesystemype=ldiskfs combinedmdsmgs=falsemdtfilesystemtype=zfs

# sinceconfigure combinedmdsmgsthe defaultsMDTs to true, mgtfilesystemtype will be ignored and
# the MGT will use ldiskfs
mdtfilesystemtypemdtfilesystemype=ldiskfs mgtfilesystemype=zfs
 
# do not do this - may result in an unexpected configuration
fstype=zfs mgtfilesystemtypemdtfilesystemtype=ldiskfs

Panel

title	optional mgssizegb \| BooleanInteger

Sets the size of the partition on the MGS in GB. This value is only applicable when the session is using a stand alone MGSMarks 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)> 0 and must be an integer. When setting this value, take into consideration that most test nodes have ~90GB of disk space.

Code Block

theme	Midnight

# markconfigure a session2GB as optional
optional
# or
optional=true

# mark a session as required - typically not necessary since false is the default
optional=false

...

partition on the MGS
mgssizegb=2

...

Panel

title	ostcount mgtfilesystemtype \| IntegerString

Configure the file system type to use on the MGTs.

NOTE: The default value for combinedmdsmgs is true, therefore it must be set to false in order to configure a different file system type for the MGT. Also, <mdt/mgt/ost>filesystemtype should not be used in combination with fstype The number of OSTs per OSS.

Valid values: 1 - 8ldiskfs, zfs

Code Block

theme	Midnight

# configure createthe 8MGTs OSTsto peruse OSSzfs
osscountmgtfilesystemtype=2zfs ostcountcombinedmdsmgs=8false

# createconfigure the 4MGTs OSTsto peruse OSSldiskfs
osscountmgtfilesystemype=4ldiskfs ostcount=4

Panel

title	ostfilesystemtype \| String

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

Code Block

theme	Midnight

# configure the OSTs to use zfs
ostfilesystemtype=zfs

# configure the OSTs tocombinedmdsmgs=false

# since combinedmdsmgs defaults to true, mgtfilesystemtype will be ignored and
# the MGT will use ldiskfs
ostfilesystemypemdtfilesystemtype=ldiskfs mgtfilesystemype=zfs
 
# do not do this - may result in an unexpected configuration
fstype=zfs ostfilesystemtypemgtfilesystemtype=ldiskfs

Panel

title	ostsizegb optional \| IntegerBoolean

Sets the size of the partitions on the OSS in GBMarks the test session as optional: does not impact the verified value from Maloo and is only run if resources are immediately available.

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.true, false (no value is the same as true)

Code Block

theme	Midnight

# run configureoptional 2GBsession partitionswith onsome theexperimental OSS
ostsizegb=2
settings
optional testlist=sanity env=FSNAME=lus12345

Anchor

	ostcount
	ostcount

Panel

title	resumeaftercrash ostcount \| BooleanInteger

The number of OSTs per OSSWhen 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)1 - 8

Code Block

theme	Midnight

# configurecreate the8 sessionOSTs to continue after a suite crashes - typically not necessary since the default is true
resumeaftercrash
# or
resumeaftercrash=trueper OSS
osscount=2 ostcount=8

# configurecreate the4 sessionOSTs to stop after a suite crashes
resumeaftercrash=falseper OSS
osscount=4 ostcount=4

Panel

title	signofftest ostfilesystemtype \| BooleanString

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

Marks the session as enforcing: is used to determine the verified value from Maloo.

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

Code Block

theme	Midnight

# markconfigure the sessionOSTs asto enforcing - typically not needed sinceuse zfs
ostfilesystemtype=zfs

# configure the defaultOSTs is true
signofftest
# or
signofftest=trueto use ldiskfs
ostfilesystemype=ldiskfs

# mark the session as not enforcing
signofftest=falsedo not do this - may result in an unexpected configuration
fstype=zfs ostfilesystemtype=ldiskfs

Panel

title	standalonemgs ostsizegb \| BooleanInteger

Sets the size of the partitions on the OSS in GBProvisions a separate test node as the MGS. The MGS will be setup with the same parameters as the MDS unless they're overwritten.

Valid values: true, false (no value is the same as true)> 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.

Code Block

theme	Midnight

# configure the2GB sessionpartitions toon the OSS
ostsizegb=2

Panel

title	resumeaftercrash \| Boolean

When 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)

Code Block

theme	Midnight

run with a stand alone MGS
standalonemgs
# or
standalonemgs=true

# configure the session to runcontinue withafter thea MGSsuite oncrashes the- MDStypically butnot separate partitions
standalonemgs=false combinedmdsmgs=false

# configure the session to run with the MGS on the MDS and have the MGT share
# a partition with a MDT
standalonemgs=false combinedmdsmgs=necessary since the default is true
resumeaftercrash
# or
resumeaftercrash=true

# configure the session to runstop withafter a stand alone MGS with a different file
# system type than the OSS and MDS
standalonemgs mgtfilesystemtype=zfs mdtfilesystemtype=ldiskfs ostfilesystemtypesuite crashes
resumeaftercrash=false

Panel

title	subproject, @ signofftest \| Boolean

Specifies the subproject of the patch. Subprojects must be added by Autotest Admin, currently the only configured subproject is lnetMarks the session as enforcing: is used to determine the verified value from Maloo.

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

Code Block

theme	Midnight

# configuremark the session as toenforcing run- thetypically lnetnot subprojectneeded test sessions
@lnetsince the default is true
signofftest
# or
subproject=lnet

...


signofftest=true

# mark the session as not enforcing
signofftest=false

...

Panel

title	testgroup standalonemgs \| StringBoolean

Provisions a separate test node as the MGS. The MGS will be setup with the same parameters as the MDS unless they're overwritten.

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

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

Code Block

theme	Midnight

# runconfigure athe typicalsession review-ldiskfsto sessionrun with a stand alone MGS
testgroup=review-ldiskfs standalonemgs
standalonemgs
# or
standalonemgs=true

# configure the session to run failover with athe specificMGS server version
testgroup=failover serverversion=2.11.50on the MDS but separate partitions
standalonemgs=false combinedmdsmgs=false

# configure the session to run review-dne-part-1 with the MGS on the MDS and have the MGT share
# a partition with additionala suitesMDT
testgroup=review-dne-part-1 testlist=sanity-lfsck,sanity-sec

...

Panel

title	testlist \| String

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.

Code Block

theme	Midnight

# run a custom list of suites
testlist=sanity,sanity-sec,sanity-hsm

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

standalonemgs=false combinedmdsmgs=true

# configure the session to run with a stand alone MGS with a different file
# system type than the OSS and MDS
standalonemgs mgtfilesystemtype=zfs mdtfilesystemtype=ldiskfs ostfilesystemtype

Panel

title	subproject, @ \| Boolean

Specifies the subproject of the patch. Subprojects must be added by Autotest Admin, currently the only configured subproject is lnet.

Valid values: lnet

Panel

title	timeoutreprovision \| Boolean

Configures the session to re-provision all of the nodes instead of simply reboot them.

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

Code Block

theme	Midnight

# re-provisionconfigure nodesthe aftersession a timeout
timeoutreprovision
# or
timeoutreprovision=true

# reboot the nodes after a timeout - typically not necessary since reboot is the default
timeoutreprovision=falseto run the lnet subproject test sessions
@lnet
# or
subproject=lnet

Anchor

	testgroup
	testgroup

Panel

title	trivial testgroup \| BooleanString

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

Code Block

theme	Midnight

# run a typical review-ldiskfs session with a stand alone MGS
testgroup=review-ldiskfs standalonemgs

# run failover with 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

Anchor

	testlist
	testlist

Panel

title	testlist \| String

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 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.

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

Code Block

theme	Midnight

# markrun thea patchcustom as trivial
trivial
# or
trivial=truelist of suites
testlist=sanity,sanity-sec,sanity-hsm

# mark the patch as non-trivial - typically not necessary since this is the default
trivial=false

...

Node Parameters

...

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

Panel

title	timeoutreprovision \| Boolean

Configures the session to re-provision all of the nodes instead of simply reboot them.

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

Code Block

theme	Midnight

mdsdistro=el7 mgsdistro=el7 ossdistro=el7

Users can simply write

Code Block

theme	Midnight

serverdistro=el7

Panel

title	arch \| String or Array

Sets the architecture for the specified node type

Valid values: x86_64, ppc64, aarch64 (architecture must have been built for patch)

Code Block

theme	Midnight

# clients will use x86_64
clientarch=x86_64

...

# re-provision nodes after a timeout
timeoutreprovision
# or
timeoutreprovision=true

# reboot the nodes after a timeout - typically not necessary since reboot is the default
timeoutreprovision=false

Panel

title	trivial \| Boolean

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.

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

...

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:

Panel

title	buildno \| Integer

Used in conjunction with job to install a specific build on the specified node. job must be specified with buildno and version cannot be specified with buildno.

Valid values: Any valid Jenkins build number for the specified job

Code Block

theme	Midnight

# installmark the serverpatch with a specific job/build combination
serverbuildno=343 serverjob=lustre-master as trivial
trivial
# or
trivial=true

# thismark wouldthe failpatch since serverjobas non-trivial - typically not necessary since this is notthe specifieddefault
serverbuildno=343

Panel

title	count \| Integer

trivial=false

Anchor

	node_parameters
	node_parameters

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

Code Block

theme	Midnight

mdsdistro=el7 mgsdistro=el7 ossdistro=el7

Users can simply write

Code Block

theme	Midnight

serverdistro=el7

Panel

title	arch \| String or Array

Sets the architecture for the specified node type

Valid values: x86_64, ppc64, aarch64 (architecture must have been built for patch

clientcount

2 - 4

mdscount

1 - 6

osscount

1 - 4

Code Block

theme	Midnight

# configure session to run with 4 clients, 2 MDSs and 1 OSS
clientcount=4 mdscount=2 osscount=1

Panel

title	distro \| String

Distribution to use for the specified node type.

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.)

Code Block

theme	Midnight

# specifyclients thewill client to use el7 and all servers sles12sp3
clientdistro=el7 serverdistro=sles12sp3

# specify the client to use ubuntu1804, MDS to use el7 and OSS to use sles12sp3
clientdistro=ubuntu1804 mdsdistro=el7 ossdistro=sles12sp3use x86_64
clientarch=x86_64

Anchor

	buildno_attr
	buildno_attr

Panel

title	ibstack buildno \| String

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.)

Code Block

theme	Midnight

clientibstack=inkernel

...

Integer

Used in conjunction with job to install

...

Panel

title	job \| String

Used with buildno to install a specific build on the specified node. buildno job must be specified with job. buildno and version cannot be specified with jobbuildno.

Valid values: Any valid Jenkins job, such as lustre-reviews, lustre-master, etc.build number for the specified job

Code Block

theme	Midnight

# install the server with a specific job/build combination
serverbuildno=343 serverjob=lustre-b2_10 serverbuildno=123master 

# this would fail since buildnoserverjob is not specified for client
serverjob=lustre-b2_10 serverbuildno=123 clientjob=lustre-master

Panel

borderStyle	solid
title	selinux \| Boolean

Enables selinux on the specified node type.

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

Code Block

theme	Midnight

# enables selinux on clients
clientselinux
# or
clientselinux=true

# disables selinux on clients - not typically necessary since false is the default
clientselinux=false

...

serverbuildno=343

Panel

title	count \| Integer

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:

clientcount	2 - 4
mdscount	1 - 6
osscount	1 - 4

Code Block

theme	Midnight

# configure session to run with 4 clients, 2 MDSs and 1 OSS
clientcount=4 mdscount=2 osscount=1

Panel

title	distro \| String

Distribution to use for the specified node type.

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 .)

Code Block

theme	Midnight

# specify the client to use el7 and all servers sles12sp3
clientdistro=el7 serverdistro=sles12sp3

# specify the client to use ubuntu1804, MDS to use el7 and OSS to use sles12sp3
clientdistro=ubuntu1804 mdsdistro=el7 ossdistro=sles12sp3

Panel

title	ibstack \| String

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 .)

Code Block

theme	Midnight

clientibstack=inkernel

Anchor

	job_attr
	job_attr

Panel

title	job \| String

Used with buildno to install a specific build on the specified node. buildno must be specified with job. version cannot be specified with job.

Valid values: Any valid Jenkins job, such as lustre-reviews, lustre-master, etc.

Code Block

theme	Midnight

# install the server with a specific job/build combination
serverjob=lustre-b2_10 serverbuildno=123

# this would fail since buildno is not specified for client
serverjob=lustre-b2_10 serverbuildno=123 clientjob=lustre-master

Panel

borderStyle	solid
title	selinux \| Boolean

Enables selinux on the specified node type.

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

Code Block

theme	Midnight

# enables selinux on clients
clientselinux
# or
clientselinux=true

# disables selinux on clients - not typically necessary since false is the default
clientselinux=false

Anchor

	node_parameter_version
	node_parameter_version

Panel

borderStyle	solid
title	version \| String

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.

Code Block

theme	Midnight

# specify patch level versions
clientversion=2.10.3 serverversion=2.11.0

# specify minor versions which uses the highest patch level version
clientversion=2.10 serverversion=2.11

# specify Exascaler tags in the -ddn[0-9] format
clientversion=2.12.2-ddn2 serverversion=2.14.0-ddn23

# specify Exascaler tags in the EXAx.x.x format
clientversion=EXA5.0.1 serverversion=EXA6.0.0

# specify Exascaler tags in the EXAx format which uses the highest minor version
clientversion=EXA5 serverversion=EXA6

Note that in addition to the more commonly used serverversion= option, it is possible (to a limited extent) to request separate ossversion= and mdsversion= if necessary.

Anchor

	tags
	tags

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 version 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

Version	Build
2.7.0 (2.7)	https://build.whamcloud.com/job/lustre-b2_7/29/
2.8.0 (2.8)	https://build.whamcloud.com/job/lustre-b2_8/12/
2.9.0 (2.9)	https://build.whamcloud.com/job/lustre-b2_9/22/
2.10.0	https://build.whamcloud.com/job/lustre-b2_10/5/
2.10.1	https://build.whamcloud.com/job/lustre-b2_10/30/
2.10.2	https://build.whamcloud.com/job/lustre-b2_10/52/
2.10.3	https://build.whamcloud.com/job/lustre-b2_10/69/
2.10.4	https://build.whamcloud.com/job/lustre-b2_10/116/
2.10.5	https://build.whamcloud.com/job/lustre-b2_10/136/
2.10.6	https://build.whamcloud.com/job/lustre-b2_10/152/
2.10.7	https://build.whamcloud.com/job/lustre-b2_10/168/
2.10.8 (2.10)	https://build.whamcloud.com/job/lustre-b2_10/170/
2.11.0 (2.11)	https://build.whamcloud.com/job/lustre-b2_11/2/
2.12.0	https://build.whamcloud.com/job/lustre-b2_12/2/
2.12.1	https://build.whamcloud.com/job/lustre-b2_12/13/
2.12.2	https://build.whamcloud.com/job/lustre-b2_12/18/
2.12.3	https://build.whamcloud.com/job/lustre-b2_12/53/
2.12.4	https://build.whamcloud.com/job/lustre-b2_12/66/
2.12.5

...

Panel

borderStyle	solid
title	version \| String

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.

Code Block

theme	Midnight

# specify patch level versions
clientversion=2.10.3 serverversion=2.11.0

# specify minor versions which uses the highest patch level version
clientversion=2.10 serverversion=2.11

# specify Exascaler tags in the -ddn[0-9] format
clientversion=2.12.2-ddn2 serverversion=2.14.0-ddn23

# specify Exascaler tags in the EXAx.x.x format
clientversion=EXA5.0.1 serverversion=EXA6.0.0

# specify Exascaler tags in the EXAx format which uses the highest minor version
clientversion=EXA5 serverversion=EXA6

Note that in addition to the more commonly used serverversion= option, it is possible (to a limited extent) to request separate ossversion= and mdsversion= if necessary.

...

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 version 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.

...

Version	Build
2.7.0 (2.7)	https://build.whamcloud.com/job/lustre-b2_712/2987/
2.8.0 (2.8)12.6	https://build.whamcloud.com/job/lustre-b2_812/12112/
2.9.0 (2.9).12.7	https://build.whamcloud.com/job/lustre-b2_12/135/
2.12.8	https://build.whamcloud.com/job/lustre-b2_912/22152/
2.12.10.09 (2.12)	https://build.whamcloud.com/job/lustre-b2_1012/5164/
2.10.113.0 (2.13)	https://build.whamcloud.com/job/lustre-b2_1013/306/
2.1014.0 (2.14)	https://build.whamcloud.com/job/lustre-b2_1014/522/
2.1015.30	https://build.whamcloud.com/job/lustre-b2_1015/6913/
2.1015.41	https://build.whamcloud.com/job/lustre-b2_1015/11628/
2.1015.52	https://build.whamcloud.com/job/lustre-b2_1015/13648/
2.1015.63	https://build.whamcloud.com/job/lustre-b2_1015/15265/
2.1015.74	https://build.whamcloud.com/job/lustre-b2_1015/16881/
2.10.8 (2.10)15.5	https://build.whamcloud.com/job/lustre-b2_1015/17094/
2.11.0 (2.11)15.6	https://build.whamcloud.com/job/lustre-b2_1115/2100/
2.15.12.07 (2.15)	https://build.whamcloud.com/job/lustre-b2_1215/2107/
2.1216.10	https://build.whamcloud.com/job/lustre-b2_1216/132/
2.1216.1 (2.16)	https://build.whamcloud.com/job/lustre-b2_1216/18/
2.12.3	https://build.whamcloud.com/job/lustre-b2_12/53/
2.12.4	https://build.whamcloud.com/job/lustre-b2_12/66/
2.12.5	https://build.whamcloud.com/job/lustre-b2_12/87/
2.12.6	https://build.whamcloud.com/job/lustre-b2_12/112/
2.12.7	https://build.whamcloud.com/job/lustre-b2_12/135/
2.12.8	https://build.whamcloud.com/job/lustre-b2_12/152/
2.12.9 (2.12)	https://build.whamcloud.com/job/lustre-b2_12/164/
2.13.0 (2.13)	https://build.whamcloud.com/job/lustre-b2_13/6/
2.14.0 (2.14)	https://build.whamcloud.com/job/lustre-b2_14/2/
2.15.0	https://build.whamcloud.com/job/lustre-b2_15/13/
2.15.1	https://build.whamcloud.com/job/lustre-b2_15/28/
2.15.2	https://build.whamcloud.com/job/lustre-b2_15/48/
2.15.3	https://build.whamcloud.com/job/lustre-b2_15/65/
2.15.4 (2.15)	https://build.whamcloud.com/job/lustre-b2_15/81
EXAScaler Versions

...

EXAScaler Versions
6/

Anchor
test_groups_section
test_groups_section

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

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

, sanity-lipe-find3

, racer

full

-dne

-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-

dne-zfs-part-1sanity-scrub, replay-single, obdfilter-survey, replay-ost-single, large-scale, insanity, parallel-scale, runtests, replay-dual, sanity-flr

patchless

lnet-selftest, runtests, sanity, sanity-scrub, sanity-benchmark, sanity-lfsck, sanityn, sanity-hsm, sanity-flr, sanity-dom, sanity-lsnapshot,

mmp

insanity, sanity-

dom

quota,

mds

sanity-

survey

sec, sanity-

lfsck

pfl,

sanity

lustre-rsync-

lnet

test,

pjdfstest,

ost-pools,

recovery-small

full-dne-zfs-part-2

lnet-selftest, sanity, sanity-hsm, lustre-rsync-test, sanity-sec, replay-vbr

mds-survey, mmp, performance-sanity, parallel-scale, large-scale, obdfilter-survey, parallel-scale-nfsv3,

sanity

parallel-scale-

quota

nfsv4,

sanity-pcc

pjdfstest, sanity

-lipe

-

find3

lnet, racer

full

-dne

-zfs-

part-3

dkms

sanity-scrub, replay-

pfl

single,

performance

obdfilter-

sanity

survey,

sanity

replay-ost-

benchmark

single,

conf

large-

sanity

scale,

sanityn

insanity, parallel-scale

-nfsv4, hot-pools

, runtests, replay-dual, sanity-flr, sanity-lsnapshot, mmp, sanity-dom, mds-survey, sanity-

lipe

lfsck, sanity

-lipe-scan3

-lnet, pjdfstest, ost-pools, recovery-small

full-zfs

full

-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

, sanity-lipe-find3

, 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

full-patchless

lnet-selftest

, runtests

, sanity, sanity-

scrub

lnet, sanity-

benchmark

sec
lustrefs_exporter	lustrefs_exporter
review	lnet-selftest, runtests, sanity

-lfsck

, sanityn,

sanity

replay-

hsm

single, conf-sanity, recovery-

flr

small,

sanity

replay-

dom, sanity

ost-

lsnapshot

single, insanity, sanity-quota

, sanity-sec, sanity-pfl

, lustre-rsync-test, ost-pools,

mds

sanity-

survey, mmp

lfsck,

performance-

sanity

, parallel-scale, large-scale, obdfilter-survey, parallel-scale-nfsv3, parallel-scale-nfsv4, pjdfstest

-hsm, sanity-lnet

, racer

review-dne-exa6-part-1

full-zfs-dkms

sanity-

scrub

pcc,

replay

sanity-

single

sec,

obdfilter

sanity-lipe-

survey

scan3,

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

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

sanity-scrub, replay-single, obdfilter-survey

, replay-ost-single,

large

sanity-

scale, insanity, parallel-scale, runtests, replay-dual,

dom, sanity-flr, sanity-

lsnapshot, mmp

hsm, sanity

-dom, mds-survey, sanity-lfsck, sanity-lnet, pjdfstest, ost-pools

-quota
review-dne-part-5	lustre-rsync-test, recovery-small

, sanity-scrub, sanityn

review-dne

full-zfs

-part-

2lnet-selftest, sanity, sanity-hsm, lustre-rsync-test, sanity-sec, replay-vbr, parallel-scale-nfsv3, sanity-quota

6	replay-single, ost-pools
review-dne-part-7	large-scale, hot-pools, sanity-pcc, sanity-lipe

-find3, racer


review-dne-part-8	replay-vbr, replay-dual
review-dne

full-zfs

-part-

3

9

sanity

obdfilter-

pfl

survey, performance-sanity, sanity-benchmark,

conf

parallel-

sanity, sanityn

scale, parallel-scale-nfsv4,

hot

parallel-scale-

pools, sanity-lipe, sanity-lipe-scan3

lnet-review-ldiskfs-dne

lnet-selftest, sanity, sanity-lnet, sanity-sec

review

lnet-selftest,

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

, sanity-lnet


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-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

review-dne-selinux-ssk

, sanity-lipe
review-e2fsprogs-part-1	conf-sanity
review-e2fsprogs-

dne-selinux-ssk

part-2	sanity, mmp
review-exa6-part-

2

1

recovery

sanity-

small

pcc, sanity-sec, sanity

-selinux

-lipe-scan3, sanity-lipe-find3

review-

dne

exa6-part-

zfs

2

runtests,

sanity

, sanityn, replay-single, conf-sanity, recovery-small, replay-ost-single, insanity, sanity-quota, lustre-rsync-test, ost-pools, sanity-lfsck, sanity-hsm

-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

sanity, mmp

Page tree

Versions Compared

Old Version 124

New Version Current

Key

Introduction

Build Parameters

General Parameters

General Parameters

Node Parameters

Node Parameters

Versions

Versions

Anchor
test_groups_section
test_groups_section

Test Groups

Page tree

Page History

Versions Compared

Old Version 124

New Version Current

Key

Introduction

Build Parameters

General Parameters

General Parameters

Node Parameters

Node Parameters

Versions

Versions

Anchortest_groups_sectiontest_groups_sectionTest Groups

Anchor
test_groups_section
test_groups_section

Test Groups