Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Name

Description

Valid Values

trivialPatch contains only whitespace, comment, man page, or test script (with additional testlist=) updates and requires minimal testing. Currently, only review-ldiskfs is run for trivial patches (see Autotest Plan for details).  The Verified flag will be set upon successful test completion(s). 

testgroup

Test group to test with. testgroup can be combined with testlist:

Code Block
Test-Parameters: testgroup=review-ldiskfs testlist=sanity-selinux

will run the review-ldiskfs test group and the sanity-selinux test suite

review, regression, full, review-ldiskfs, review-dne-part-1, review-dne-part-2, review-zfs-part-1, review-zfs-part-2, etc.

testlist

Comma separated list of test names to run in place of a standard test group. testlist can be combined with testgroup. See testgroup for an example.

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

fortestonly

Patch will be built by Jenkins. A single review test session will be run by default, unless another specific test list is specified using the testlist= parameter. The Verified flag will not be set by Maloo for landing.

 

forbuildonlyPatch will be built by Jenkins, but no testing will be done. The Verified flag will not be set by Maloo for landing. 

clientcount

Number of clients to use

2-4

mdscount

Number of MDSs to test against

1-4

mdtcount

Number of MDTs to test against

1-4

osscount

Number of OSTs to test against

1-4

ostcount

Number of OSTs per OSS to test against

1-4

clientprofile

Cobbler profile to use for clients

test

mdsprofile,

ossprofile

Cobbler profile to use for servers

test

clientdistro

Distribution to use for clients

el6, el7, sles11, sles11sp2

mdsdistro, ossdistro

Distribution to use for servers

el6, el7, sles11, sles11sp2

clientarch

Architecture to use for clients

i686, x86_64, ppc64

mdsarch, ossarch

Architecture to use for servers

i686, x86_64

clientjob

Jenkins 'job' to fetch from for the clients under test

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

clientbuildno

Jenkins build number to fetch for the clients under test

Any valid Jenkins buildno for clientjob

mdsjob, ossjob

Jenkins 'job' to fetch from for the servers under test

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

serverbuildno

Jenkins build number to fetch for the servers under test

Any valid Jenkins build number for mdsjob or ossjob

nettypes

Network types to use as a comma separated array

tcp, o2ib

ostsizegb

Size of OSTs in GB. Note this is a max size and will be limited by the disk available

>0

mdssizegb

Size of MDS in GB. Note this is a max size and will be limited by the disk available

>0

mdtfilesystemtype

File system to use for MDTs and MGS

zfs, ldiskfs

ostfilesystemtype

File system to use for OSTs

zfs, ldiskfs

clientibstack

IB stack to use on the client.

inkernel, ofa

serveribstack

IB stack to use on the server.

inkernel, ofa

envdefinitions

Comma separated environment definitions passed to the environment.

Panel

Be very careful setting environment variables directly (for example OSTFSTYPE=zfs) because autotest creates a config file based on the environment it builds, and 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 envdefinitions variable when a direct variable is not listed here.

ONLY=26,EXCEPT=22

alwaysuploadlogsBy default autotest will upload logs on passing tests. This will force it do upload logs. This option is no longer necessary. 
failoverSetup cluster in failover configuration 
iscsiUse iSCSI for failover testing0, 1
combinedmdsmgsUse a combined server storage target for the MDS and MGS or use separate targets for the MDS and MGS. If false, the MGS and MDS will be on the same node, but the MDT and MGT will be separate storage targets. Default value is true; a combined storage target.true, false

...