| /test/stcnv/usr/src/suites/nfs/nfsgen/tests/recovery/ |
| README | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
29 All tests in this directory verify NFSv4 RECOVERY
34 Some tests in recovery will test conflicting lock, original scenario is
35 start processes on different machine (such as CLIENT and CLIENT2). In
|
| /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/server/ |
| README | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
36 script to create test files/directories in the current
37 directory based on variables in v4test.cfg file, which
38 must be found in the same directory as the script. In
49 installed in server systems which maybe outside the testing
|
| /test/stcnv/usr/src/suites/nfs/nfsv4/server/ |
| README | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
36 script to create test files/directories in the current
37 directory based on variables in v4test.cfg file, which
38 must be found in the same directory as the script. In
49 installed in server systems which maybe outside the testing
|
| /test/ohacts/src/doc/dataservice/non_reboot/ |
| test_19.txt | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
38 Run through all the resource groups in the loop,
46 In the case of failover resource group, get the cluster node
50 In the case of scalable resource group, since there are multiple
59 node/zone of the cluster, in the case of failover resource group or
61 in the case of scalable resource group
72 of the cluster, in the case of failover resource group
74 in the case of scalable resource group
|
| /test/ohacts/src/doc/dataservice/reboot/ |
| test_1.txt | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
39 Run through all the resource groups in the loop,
47 In the case of failover resource group, get the cluster node
51 In the case of scalable resource group, since there are multiple
60 node of the cluster, in the case of failover resource group or
62 in the case of scalable resource group
73 of the cluster, in the case of failover resource group
75 in the case of scalable resource group
|
| test_2.txt | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
39 Run through all the resource groups in the loop,
47 In the case of failover resource group, get the cluster node
50 In the case of scalable resource group, since there are multiple
59 node of the cluster, in the case of failover resource group or
61 in the case of scalable resource group
72 of the cluster, in the case of failover resource group
74 in the case of scalable resource group
|
| test_3.txt | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
38 Run through all the resource groups in the loop,
49 In the case of failover resource group, get the cluster node
53 In the case of scalable resource group, since there are multiple
62 node of the cluster, in the case of failover resource group or
64 in the case of scalable resource group
|
| test_5.txt | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
37 Run through all the resource groups in the loop,
45 In the case of failover resource group, get the cluster node
49 In the case of scalable resource group, since there are multiple
58 node of the cluster, in the case of failover resource group or
60 in the case of scalable resource group
71 of the cluster, in the case of failover resource group
73 in the case of scalable resource group
|
| /test/ohacts/src/tset/dataservice/sample/get_dsinfo_output/ |
| README | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
38 in it. First resource is of type SUNW.LogicalHostname and second
42 properties of both the resources in this resource group and also names
50 This file is similar to 1) above. In addition to all the information
65 has a Resource of type SUNW.SharedAddress in it. The second resource
77 This file is similar to 3) above. In addition to all the information
|
| /test/stcnv/usr/src/suites/os/xvm/virt-install/ |
| README | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
73 In the majority of cases, the test suite can be installed from packages. The
103 In addition, test suite packages can be built using the proto directory,
149 was in before the suite was run.
153 All of the jumpstart files (found in $TET_SUITE_ROOT/virt-install/etc)
156 file in the configuration file.
|
| README.CONFIG | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
31 are example test_config files in $TET_SUITE_ROOT/virt-install/config
40 This network name/IP also needs a valid mac address. In order to
50 test_config.fullrun - config file which will run all test cases in the
65 # DO NOT CHANGE ANYTHING IN THIS SECTION. PYTHONPATH MUST BE SET OR
90 # need to know about this mac address in order to run the PXE and
133 # NFSVDISKTYPE is the type of vdisk to create in the NFSROOT.
139 # vdisk file of type NFSVDISKTYPE in NFSROOT. NFSVDISKSPARSE can be
155 # (in MB). NOTE: This value has a lower bound of 20000.0 (20 gb
[all...] |
| /test/ontest-stc2/src/suites/zfs/ |
| README | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
47 3.2 Configuring and running in global zone
49 3.3 Configuring and running in local zone
65 o In the majority of cases, the test suite can be installed from packages. The
85 the suite is recommended if you have previous run the suite in local zone mode. For
133 SUNWstc-stf in global zone
139 ~root/.rhosts file in the server, for example:
145 3.2 Configuring and running in global zone
180 RDISKS -- The corresponding scratch disks list for each host in RHOSTS list
[all...] |
| /test/stcnv/usr/src/suites/fs/zfs/ |
| README | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
42 3.2 Configuring and running in global zone
43 3.3 Configuring and running in local zone
58 o In the majority of cases, the test suite can be installed from
80 recommended if you have previous run the suite in local zone mode.
135 SUNWstc-stf in the global zone
141 to ~root/.rhosts file in the server, for example:
150 3.2 Configuring and running in global zone
194 RDISKS -- The corresponding scratch disks list for each host in
[all...] |
| /test/ontest-stc2/src/suites/share/ |
| README | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
47 In the majority of cases, the test suite can be installed from packages. The
71 In the majority of cases, the test suite can be installed from packages. The
90 The test suite source can also be installed locally, built in the source
105 environment variable. In addition, test suite packages can be built using
106 the proto directory and stored in the packages directory below the defined
|
| /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/tests/other_tests/domain/ |
| README | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
75 User can customize this value with DOMAIN_TMOUT env variable, in the
80 Please note the above method only works in global zone and whole root zone.
82 In sparse root zone, however, the file is on a file system shared with
86 So it takes much longer(more than 1 hour) to run all tests in sparse root zone.
|
| /test/ontest-stc2/src/suites/os/smf/tests/libscf-low/trans/scf_transaction_start/ |
| ASSERTIONS | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
80 and allows multiple transactions to be in progress on the same
83 In other words, scf_transaction_start() successfully starts a
84 transaction even if the supplied propertygroup is already in
85 use in another transaction which is currently in progress.
|
| /test/stcnv/usr/src/suites/nfs/nfsv4/tests/other_tests/domain/ |
| README | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
75 User can customize this value with DOMAIN_TMOUT env variable, in the
80 Please note the above method only works in global zone and whole root zone.
82 In sparse root zone, however, the file is on a file system shared with
86 So it takes much longer(more than 1 hour) to run all tests in sparse root zone.
|
| /test/stcnv/usr/src/suites/os/smf/tests/libscf-low/trans/scf_transaction_start/ |
| ASSERTIONS | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
80 and allows multiple transactions to be in progress on the same
83 In other words, scf_transaction_start() successfully starts a
84 transaction even if the supplied propertygroup is already in
85 use in another transaction which is currently in progress.
|
| /test/stcnv/usr/src/tools/genutils/ |
| README | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
32 come up in the future.
39 and tx areas, more will be added in the future as needed. They are structured
55 In the majority of cases, the STC GenUtils tool can be installed
82 the source code in an STC workspace and invoke 'stf_build'. An example
92 which can be installed as described in the "Installation" section above.
106 or any other locations that you install SUNWstc-genutils package or build it in
109 In <STC_GENUTILS>/bin, we have a program named stc_genutils that returns the
110 value of STC GenUtils tool in use. Each test suite can invoke this program t
[all...] |
| /test/ontest-stc2/src/suites/iSCSI/ |
| README | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
54 In the majority of cases, the test suite can be installed from packages. The
79 In the majority of cases, the test suite can be installed from packages. The
99 The test suite source can also be installed locally, built in the source
129 Other configurable variables that can be set in the configuration line :
|
| /test/ontest-stc2/src/suites/os/xvm/virt-install/ |
| README | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
94 In the majority of cases, the test suite can be installed from packages. The
105 The test suite source can also be installed locally, built in the source
120 environment variable. In addition, test suite packages can be built using
121 the proto directory and stored in the packages directory below the defined
171 was in before the suite was run.
175 All of the jumpstart files (found in $TET_SUITE_ROOT/virt-install/etc)
178 file in the configuration file.
192 - uncomment the PXE and DOMUMACADDR arguments in you
[all...] |
| /test/stcnv/usr/src/suites/storage/fwflash/ |
| README | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
52 In the majority of cases, the test suite can be installed from packages.
55 source and build the binaries in the source tree. Both methods are
93 usr/src directory resides (in the example above, the workspace root
98 In addition, test suite binary packages can be constructed using the
103 This can be done instead of, or in addition to, 'make install'. The
104 package thus constructed will be placed in the 'packages' directory
135 Another variable that can be set in the configuration line:
|
| /test/stcnv/usr/src/tools/tet/contrib/ctitools/ |
| README | 10 # under the terms of the "Artistic License" which is located in
39 include - CTI header files that are to be included in code.
53 src/scripts - tools to assist in the building and packaging of CTI for TET.
97 the built code in $WS_ROOT/proto and stores the packages (SUNWstc-tetlite or
98 SUNWstc-dtet) in the $WS_ROOT/packages directory.
149 The ksh files to be sourced in are :
164 The Perl files to be soureced in are:
187 (respectively) to support options in scenario test case names. Both scripts
200 directly in the kernel, for example:
211 NOTE: these scripts are available in the $CTI_ROOT/bin directory
[all...] |
| /test/ontest-stc2/src/suites/os/smf/tests/libscf-low/iterators/scf_iter_instance_snapshots/ |
| ASSERTIONS | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
123 5. In order to verify that an iteration has been correctly
125 the snapshot created in 2 is returned.
|
| /test/ontest-stc2/src/suites/os/smf/tests/libscf-low/snaplevel/scf_snaplevel_get_scope_name/ |
| ASSERTIONS | 6 # You may not use this file except in compliance with the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
101 returned is same as the length of the string returned in
103 6. In order to verify the scope name is correct, first get a
135 returned is same as the length of the string returned in
140 same as that in step 5. Also, verify that the truncated
141 name of the scope is returned in the buffer.
173 returned is same as the length of the string returned in
178 returned is same as that in step 5. Also, verify that the
179 truncated name of the scope is returned in the buffer an
[all...] |
