HomeSort by relevance Sort by last modified time
    Searched refs:For (Results 1 - 25 of 84) sorted by null

1 2 3 4

  /test/ohacts/src/
README 10 # See the License for the specific language governing permissions
30 Automated Test Suite. For more information or full documentation, refer to the
32 and for most up-to-date build instructions, which is available at:
37 For quick build and installation instructions, see below.
49 You will also need to download and build the CTI for TET from the OpenSolaris
61 3. Open the new ohacts/src/defines.mk file for editing.
66 - For CTI_PROTO, replace <cti_proto_path> with the full path to the CTI for
69 - For PATH, replace <compiler-path> with the path to your compiler.
  /test/ohacts/src/doc/dataservice/non_reboot/
test_15.txt 10 # See the License for the specific language governing permissions
43 2. For all the nodes:
test_11.txt 10 # See the License for the specific language governing permissions
39 1. For all resource groups:
47 2. For all the resources in the resource group:
48 For all the Fault Monitor Daemons associated with the resource:
test_18.txt 10 # See the License for the specific language governing permissions
39 1. For all resource groups:
47 2. For all the resources in the resource group:
48 For all the Daemon processes associated with the resource:
test_12.txt 10 # See the License for the specific language governing permissions
38 1. For all resource groups:
53 5. For all the nodes:
test_6.txt 10 # See the License for the specific language governing permissions
43 2. For all the nodes:
47 Verify that all the daemons and fault monitor daemons for every
test_13.txt 10 # See the License for the specific language governing permissions
38 For all the resource groups on cluster:
test_9.txt 10 # See the License for the specific language governing permissions
41 1. Get the list of nodes that can be a master for FAILOVER_RG_1
44 Get the current master (primary) for $RG_i_NAME. Remember in
54 2. For all the nodes:
59 Verify that all the daemons and fault monitor daemons for every
  /test/ontest-stc2/src/suites/os/smf/tests/libscf-low/security/smf_security_errors/
README 10 # See the License for the specific language governing permissions
36 For details of the test assertion(s) proved by each test, read the
  /test/stcnv/usr/src/suites/nfs/nfsgen/tests/recovery/
README 10 # See the License for the specific language governing permissions
37 For best testing, it's better to make each process access a different
38 mountpoint. User can set below two optional env virables for this purpose,
  /test/stcnv/usr/src/suites/os/smf/tests/libscf-low/security/smf_security_errors/
README 10 # See the License for the specific language governing permissions
36 For details of the test assertion(s) proved by each test, read the
  /test/stcnv/usr/src/tools/genutils/demo/
README.demo 10 # See the License for the specific language governing permissions
29 This directory contains some demos for those libraries in the parent include
33 environment variable before running these demos, for example:
39 For more details about STC genutils tool, see the main README in the parent
  /test/ohacts/src/tset/geo/doc/
README 10 # See the License for the specific language governing permissions
32 For ex: CLUSTER_1_NODE=pcio1.sfbay.sun.com
36 1st failover address that testsuite will use for 1st sndr set
41 2nd failover address that testsuite will use for 2nd sndr set
46 3rd failover address that testsuite will use for 1st HA-NFS
51 4th failover address that testsuite will use for 2nd HA-NFS
57 will use for 1st sndr set on primary cluster.
58 For ex: d7
63 will use for 2nd sndr set on primary cluster.
64 For ex: d
    [all...]
  /test/ohacts/src/tset/sanity/doc/assertions/
transport 10 # See the License for the specific language governing permissions
31 Test Assertions for test case tc_transport
49 For all primary interfaces on cluster do the following:
70 For all secondary interfaces on cluster do the following:
  /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/tests/other_tests/uidmapping/
README 10 # See the License for the specific language governing permissions
42 For example, to run uidmapping_pos03{a}, uidmapping_pos03{b}, and
47 The above feature(running specific assertions) is provided mainly for debugging
48 purpose, so we implement it in a simple way, and don't check user input for
  /test/stcnv/usr/src/suites/nfs/nfsv4/tests/other_tests/uidmapping/
README 10 # See the License for the specific language governing permissions
42 For example, to run uidmapping_pos03{a}, uidmapping_pos03{b}, and
47 The above feature(running specific assertions) is provided mainly for debugging
48 purpose, so we implement it in a simple way, and don't check user input for
  /test/ontest-stc2/src/suites/os/xvm/virt-install/
README.CONFIG 10 # See the License for the specific language governing permissions
30 up a valid test_config file for the virt-install test suite. There
32 which are configured specifically for the BRM05 internal network.
36 - At least one UFS slice of at least 15gb. For the maxflags test
38 - At least one plumbed network interface. For the maxflags test case,
40 - A valid network name for the domU to use with a valid IP address.
41 For the simultaneous test case, 2 (or more) are required.
47 test_config.template - template file to use for new sites
57 suite. Configured for linux, pxe and simultaneous test cases.
99 # SYSIDCFG is the full path to a valid sysidcfg for the network th
    [all...]
  /test/ontest-stc2/src/suites/storage/megacli/
README 10 # See the License for the specific language governing permissions
31 The LSI MegaCli tool is a command line interface application for MegaRAID SAS
34 megacli is a test suite for mega_sas driver regression testing. It will use
46 3. For SNV users, use SNV_88 or above. For S10 Updates users, use
115 disks. Make sure the disks available for the testing adapter do not have
142 For user using megacli pakcage:
147 For user using megacli source code:
173 For how to edit the test scenario file, refer to the TET user guide at:
  /test/stcnv/usr/src/suites/storage/jist/
README.CONFIG 10 # See the License for the specific language governing permissions
50 - For Parallel SCSI Targets, one of the following:
53 - For Fibre Channel SCSI Targets, one of the following:
60 - For iSCSI Targets, one of the following:
63 - For Serial (SAS/SATA) Targets, one of the following:
72 o For Fibre Channel or iSCSI Targets, one of the following:
76 o For SAS/SATA Targets, the following:
79 o For CAS Targets, the following:
116 [2]See the Java supported system configurations for a specific list of
  /test/stcnv/usr/src/suites/storage/megacli/
README 10 # See the License for the specific language governing permissions
31 The LSI MegaCli tool is a command line interface application for MegaRAID
35 megacli is a test suite for mega_sas driver regression testing. It uses
50 3. For SNV users, use SNV_88 or above. For S10 Updates users, use
53 for instructions on how to get and install the CTI-TET package.
124 disks used for testing. Make sure the disks available for the testing
152 For user using megacli pakcage:
157 For user using megacli source code
    [all...]
  /test/ohacts/src/tset/geo/
README 10 # See the License for the specific language governing permissions
30 test harness. For more information or full documentation, refer to the
32 and for most up-to-date build instructions, which is available at:
44 test request file. For example,
48 3. Open the new test request file for editing.
56 5. Example of test request file for running geo-avs testsuite on cluster
104 disk you are using for the test, the scconf command returns some output.
  /test/ohacts/src/doc/dataservice/reboot/
test_3.txt 10 # See the License for the specific language governing permissions
39 do one node rebooting for all the resources of each resource group.
57 and waiting for the node to go down.
68 7. Waiting for the old primary node is booted back up
70 Wait for 'rgmd' process to be started up on that node.
76 For failover resource group :
82 For Scalable resource group :
  /test/ohacts/src/tset/geo/doc/assertions/
geo_avs_mult_pgs 10 # See the License for the specific language governing permissions
31 Test Assertions for test case tc_geo_avs_mult_pgs
49 For both PGs, do the following steps:
86 Created 2 PGs, and do the following for both PGs.
87 For both PGs, verify that geopg takeover succeeds when AVS is in
94 Create 2 PGs with AVS, and do the following for both PGs.
108 Created 2 PGs, and do the following for both PGs.
115 Create 2 PGs with AVS, and do the following for both PGs.
117 Issue 'sndradm -n -l' to bring AVS set for both PGs to be in LOG mode.
  /test/ontest-stc2/src/tools/checkenv/
README 10 # See the License for the specific language governing permissions
33 checkenv is a harness-independent tool which provides a framework for a test
36 For some test suites, the requirements can be simple, such as the installation
37 of core Solaris components with a common build environment. However, for many
38 test suites, the requirements can be complex. For example, tests suites may
48 checkenv provides a standard way to check for such dependencies.
  /test/stcnv/usr/src/tools/checkenv/
README 10 # See the License for the specific language governing permissions
33 checkenv is a harness-independent tool which provides a framework for a test
36 For some test suites, the requirements can be simple, such as the installation
37 of core Solaris components with a common build environment. However, for many
38 test suites, the requirements can be complex. For example, tests suites may
48 checkenv provides a standard way to check for such dependencies.

Completed in 840 milliseconds

1 2 3 4