Page History
...
Name | Description | Valid Values | ||
|---|---|---|---|---|
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 |
| ||
| forbuildonly | Patch will be built by Jenkins, but no testing will be done. The Verified flag will not be set by Maloo for landing. | |||
| trivial | Patch 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). | |||
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 | ||
serverprofile (use mdsprofile & ossprofile instead) | Cobbler profile to use for servers | test | ||
clientdistro | Distribution to use for clients | el6, el7, sles11, sles11sp2 | ||
serverdistro (A bug exists today which means you need to specify mdsdistro & ossdistro not serverdistro) | Distribution to use for servers | el6, el7, sles11, sles11sp2 | ||
clientarch | Architecture to use for clients | i686, x86_64, ppc64 | ||
serverarch serverdistro (A bug exists today which means you need to specify mdsarch & ossarch not serverarch) | Architecture to use for servers | i686, x86_64 | ||
clientjob | Jenkins 'job' to fetch from for the clients under test | Any valid Jenkins job | ||
clientbuildno | Jenkins build number to fetch for the clients under test | Any valid Jenkins buildno for clientjob | ||
serverjob serverdistro (A bug exists today which means you need to specify mdsjob & ossjob not serverjob) | Jenkins 'job' to fetch from for the servers under test | Any valid jenkins job | ||
serverbuildno | Jenkins build number to fetch for the servers under test | Any valid build for serverjob | ||
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 | ||
mdsfilesystemtype | File system to use for MDSs | zfs, ldiskfs | ||
mdtfilesystemtype | File system to use for MDTs | 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.
| AA=BB,CC=DD etc. | ||
testgroup | Test group to test with | review, regression, full, review-ldiskfs, review-dne-part-1, review-dne-part2, review-zfs-part1, review-zfs-part-2, etc. | ||
testlist | Comma separated list of test names to run in place of a standard test group | sanity, conf-sanity, mmp, replay-single, replay-dual, lnet-selftest, etc. | ||
| alwaysuploadlogs | By default autotest will upload logs on passing tests. This will force it do upload logs. This option is no longer necessary. | |||
| failover | Setup cluster in failover configuration | |||
| iscsi | Use iSCSI for failover testing | 0, 1 | ||
| combinedmdsmgs | Use 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. | true, false |
You do not need to specify all the values only those values important for your requirements, the test system will use your request to alter a regular test. Also to ensure that you all reviews are fully tested to a known standard. The test system will run a regular, unmodified test set as well as the special request.
...
Overview
Content Tools