#
# CDDL HEADER START
#
# The contents of this file are subject to the terms of the
# Common Development and Distribution License (the License).
# You may not use this file except in compliance with the License.
#
# You can obtain a copy of the license at src/CDDL.txt
# or http://www.opensolaris.org/os/licensing.
# See the License for the specific language governing permissions
# and limitations under the License.
#
# When distributing Covered Code, include this CDDL HEADER in each
# file and include the License file at src/CDDL.txt.
# If applicable, add the following below this CDDL HEADER, with the
# fields enclosed by brackets [] replaced with your own identifying
# information: Portions Copyright [yyyy] [name of copyright owner]
#
# CDDL HEADER END
#

#
# Copyright 2007 Sun Microsystems, Inc.  All rights reserved.
# Use is subject to license terms.
#
# ident	"@(#)README	1.10	07/06/26 SMI"
#

This file contains a list of configuration variables which are set in
the beginning of run_dats and prior to any test case run.  The
configuration variable values are based on the contents of the
dataservice information file provided by the user.  The actual values
used by the test can be found in the testlog file under test result
directory when test is complete.

   1) NUM_RGS 

      This is the total number of resource groups for a given data service

   2) RG_x_NAME

      This is the name of the RG x.

      Ex : If NUM_RGS is 2, there will be 2 variables, RG_1_NAME and RG_2_NAME

   3) RG_x_NODELIST

      This is the comma separated list of node names for RG x.

      Ex : RG_1_NODELIST=phys-node-1, phys-node-2

           If NUM_RGS is 2, there will be 2 variables. RG_1_NODELIST and
           RG_2_NODELIST

   4) RG_x_NUM_PROPERTIES

      This is the total number of properties for the resource group x.

      Ex : If NUM_RGS is 2, there will be 2 variables. RG_1_NUM_PROPERTIES
	   and RG_2_NUM_PROPERTIES.

   5) RG_x_PROPERTY_y

      This is the property 'y' for RG 'x'. The value of this variable will
      be of the form "a=b".

      Ex : If NUM_RGS is 1 and RG_1_NUM_PROPERTIES=2, there will be 2 values,
	   RG_1_PROPERTY_1 and RG_1_PROPERTY_2.

	   RG_1_PROPERTY_1="a1=b1"
	   RG_1_PROPERTY_2="a2=b2"

   6) RG_x_NUM_RESOURCES

      This is the number of resources in RG x.

      Ex: If NUM_RGS is 1 and RG_1_NUM_RESOURCES is 2, this would mean that
	  there are 2 resources in the RG.

   7) RG_x_R_y_NAME

      This is the name of the resource 'y' in RG 'x'.

      Ex : If NUM_RGS is 1 and RG_1_NUM_RESOURCES is 2, there would be 2
	   variables.

	       RG_1_R_1_NAME=test-1-r
	       RG_1_R_2_NAME=test-2-r

	   i.e. Name of the first resource is test-1-r and the name of
		the second resource is test-2-r.

   8) RG_x_R_y_RT_TYPE

      This is resource type of Resource 'y' in RG 'x'.

      Ex : If NUM_RGS is 1 and RG_1_NUM_RESOURCES is 2, there would be 2
	   variables.

	       RG_1_R_1_TYPE=SUNW.nfs
	       RG_1_R_2_TYPE=SUNW.oracle

	   i.e. the resource type of the first resource in the RG is SUNW.nfs
		and the resource type of the second resource in the RG is
		SUNW.oracle

   9) RG_x_R_y_NUM_SYS_PROPERTIES

      This is the number of system properties for Resource 'y' in RG 'x'.

  10) RG_x_R_y_NUM_EXT_PROPERTIES

      This is the number of extension properties for Resource 'y' in RG 'x'.

  11) RG_x_R_y_SYS_PROPERTY_z

      This is the system property 'z' for Resource 'y' in RG 'x'.
      The value of this variable will be of the form "a=b"

      Ex : Assume :
      
	   NUM_RGS is 1 
	   RG_1_NUM_RESOURCES is 1
	   RG_1_R_1_NUM_SYS_PROPERTIES is 2

	   there would be 2 variables.

	     RG_1_R_1_SYS_PROPERTY_1
	     RG_1_R_1_SYS_PROPERTY_2

           and there values would be of the form : 

	     RG_1_R_1_SYS_PROPERTY_1="a1=b1"
	     RG_1_R_1_SYS_PROPERTY_2="a2=b2"

   12) RG_x_R_y_EXT_PROPERTY_z

      This is the extension property 'z' for Resource 'y' in RG 'x'.
      The value of this variable will be of the form "a=b"

      Ex : Assume :
      
	   NUM_RGS is 1 
	   RG_1_NUM_RESOURCES is 1
	   RG_1_R_1_NUM_EXT_PROPERTIES is 2

	   there would be 2 variables.

	     RG_1_R_1_EXT_PROPERTY_1
	     RG_1_R_1_EXT_PROPERTY_2

           and there values would be of the form : 

	     RG_1_R_1_EXT_PROPERTY_1="a1=b1"
	     RG_1_R_1_EXT_PROPERTY_2="a2=b2"

   13) RG_x_R_y_ADAPTER_GROUP

       This is the list of public network adapter group for Resource 'y'
       in RG 'x'.

       Value of this variable is a string.

       Please note that this property is optional. So some resources may
       not have a value for this.

   14) RG_x_R_y_AUX_NODELIST

       This is the comma separated list of nodenames used as auxiliary 
       nodelist.

       Value of this variable is a string.

       Please note that this property is optional. So some resources may
       not have a value for this.

   15) RG_x_R_y_NUM_DAEMONS

       This is the number of daemon processes for Resource 'y' in RG 'x'.

   16) RG_x_R_y_DAEMON_z

       This is the name of the daemon process z for Resource 'y' in RG 'x'.

       Ex : If RG_1_R_1_NUM_DAEMONS is 2, there will be 2 variables.

	    RG_1_R_1_DAEMON_1 and RG_1_R_1_DAEMON_2

   17) RG_x_R_y_NUM_FM_DAEMONS

       This is the the number of fault monitor daemons for Resource 'y' in
       RG 'x.

   18) RG_x_R_y_FM_DAEMON_z

       This is the name of the fault monitor daemon process z for 
       Resource 'y' in RG 'x'.

       Ex : If RG_1_R_1_NUM_FM_DAEMONS is 2, there will be 2 variables.

	    RG_1_R_1_FM_DAEMON_1 and RG_1_R_1_FM_DAEMON_2

   19) RG_x_R_y_SETUP_PROG

       This is the name of the setup program for Resource 'y' in RG 'x'.
       This program is invoked on any one of the cluster nodes as user 
       root.

       This is an optional argument. i.e. Some of the resources may not
       have any setup program.

       Example : 
       -------
       
       Please look at tp4() in ha_nfs test suite. In that test, we needed
       to do 'mkdir' and create a dfstab file which has 'share' commands.

       Things like that will get done in the Setup Program.

   20) RG_x_R_y_SETUP_PROG_ARGS

       These are the arguments to be passed to the setup program

       Argument list may be NULL.

   21) RG_x_SETUP_PROG

       This is the name of the client program that sets up the required
       stuff for RG x. This program is invoked on one of the cluster
       nodes.

       This is an optional argument. i.e. Some of the resource groups
       may not have a setup client program.

       Example :
       -------

	  This program can create a simple Oracle or Sybase database for 
	  testing.

   22) RG_x_SETUP_PROG_ARGS

       These are the arguments to be passed to the setup client program

       Argument list may be NULL.

   23) RG_x_SETUP_PROG_NODES

       This has the comma separated list of nodenames on which the
       setup program will be executed.

   24) RG_x_SETUP_PROG_USER

       This is the 'user name' for invoking the setup client program.

       Ex : RG_1_SETUP_PROG_USER=oracle. 

	    This means that the setup program needs to be invoked as
	    oracle.

   25) RG_x_CLIENT_PROG

       This is the name of the client program for RG x.
       This program is invoked on the client machine.

       This is an optional argument. i.e. Some of the resource groups
       may not have a client program.

       Example :
       -------

       A Few examples on what the client programs can do.

        a) Program that queries the database created by RG_x_SETUP_CLIENT_PROG
	b) Program that reads a file in HA-NFS
	c) Program that talks to Apache Web Server

   26) RG_x_CLIENT_PROG_ARGS

       These are the arguments to be passed to the client program

       Argument list may be NULL.

   27) RG_x_CLIENT_PROG_USER

       This is the 'user name' for invoking the client program.

       Ex : RG_1_CLIENT_PROG_USER=oracle. 

	    This means that the client program needs to be invoked as
	    oracle.

   28) RG_x_CLEANUP_PROG

       This is the name of the client program that cleans up the required
       stuff for RG x. This program is invoked on one of the cluster nodes.

       This is an optional argument. i.e. Some of the resource groups
       may not have a cleanup client program.

       Example :
       -------

	  This program removes Oracle or Sybase database created in the setup.

   29) RG_x_CLEANUP_PROG_ARGS

       These are the arguments to be passed to the cleanup client program

       Argument list may be NULL.

   30) RG_x_CLEANUP_PROG_NODES

       This has the comma separated list of nodenames on which the
       cleanup program will be executed.

   31) RG_x_CLEANUP_PROG_USER

       This is the 'user name' for invoking the cleanup client program.

       Ex : RG_1_CLEANUP_PROG_USER=oracle. 

	    This means that the cleanup program needs to be invoked as
	    oracle.

	==================================================================
	The following environment variables are used in dataservice_reboot
	test suite
	==================================================================

   32) NUM_OF_SLAVES

	Number of systems under TET. In this case 'NUM_OF_SLAVES' is number
	of clients + CLUSTER_SIZE.

   34) NUM_OF_SLAVES_REBOOT

	Number of systems under TET. In this case 'NUM_OF_SLAVES' is number
	of clients.

   35) CLUSTER_SIZE

	Number of nodes in the cluster.
	Test runs on a cluster and some client machines outside the cluster.
	The cluster nodes will be rebooted in these test suites. So cluster
	nodes should not be part of dTET

   36) CLUSTER_NODE_n

	One for each cluster node, the machine name of the n-th node in the
	cluster under test.

   37) CLUSTER_NODEID_n

	One for each cluster node, the machine ID of the n-th node in the
	cluster under test.

   38) TET_NODE_n

	One for each node under TET, the machine name of the n-th node.

   39) TET_NODEID_n

	One for each node under TET, the machine ID of the n-th node.

   40) TET_CLCONFID_n

	One for each node, cluster's node id (clconf id).

   41) HOMEDIR_MASTER

	Test suite home directory for master machine.

   42) HOMEDIR_CLUSTER_NODE_n

	Test suite home directory for the n-th cluster machine.

   43) HOMEDIR_CLIENT_n

	Test suite home directory for the n-th client machine.

   44) START_APPLICATION_TIME

	Time in seconds, which is needed for Resource Group(s) to come
	online(failover, switchover, etc.).

   45) NODE_REBOOT_TIME

	Time in seconds, which is needed for node to reboot.

   46) RG_EXIST

	If TRUE, Resource Group(s) already created and online. Tests, which
	creates, brings online and removes RG's does not run.
	Default is FALSE.

   47) RSH

	Secure/non-secure environment (rsh or ssh).
   
	Default is rsh.

   47) RCP

	Secure/non-secure environment (rcp or scp).
   
	Default is rcp.

   48) RUN_NEWCLI

	If TRUE, the New Commmand Set will be used for running the tests.
	If not Old Command Set will be used.
	Default is FALSE.

Indexes created Sat Nov 28 12:39:51 UTC 2009

Terms of Use | Privacy | Trademarks | Copyright Policy | Site Guidelines | Help
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Use.
Copyright © 1995-2008 Sun Microsystems, Inc.