Search

Home	Sort by relevance Sort by last modified time

Full Search
Definition
Symbol
File Path
History
Project
	\| \| Help

Searched refs:resource (Results 1 - 25 of 128) sorted by null

1 2 3 4 5 6

/test/ohacts/src/doc/dataservice/non_reboot/
test_14.txt	`33 Removing application resource should be successful. 38 1. Run through all the resource groups, for each resource group, 41 scswitch -r -j <resource> 43 2. Verify that resource is removed. But other resources 44 and resource groups should continue to be registered.`
test_13.txt	33 Unmanage the resource group and manage it again should be successful. 38 For all the resource groups on cluster: 40 1) Before putting a resource group into an unmanaged state, it is first 41 taken offline from all cluster nodes. Bring the resource group offline 46 2) A resource group cannot be unmanaged until all of the resources 49 scswitch -n -j <resource 1> 50 scswitch -n -j <resource 2> 52 scswitch -n -j <resource n> 54 3) Put the resource group into an unmanaged state. 58 4) Verify that the resource group into an unmanaged state [all...]
test_4.txt	`38 1. Run through all the resource groups, for each resource group, 41 If the resource type is not SUNW.LogicalHostname or 42 SUNW.SharedAddress or SUNW.HAStorage then disable resource using 44 scswitch -n -j <resource> 46 2. Verify that resource is disabled. But other resources 47 and resource groups should continue to be online. 49 3. Get the nodelist where this resource group can be mastered and 53 4. Use client program to verify that the resource is not available.`
test_5.txt	`38 1. Run through all the resource groups, for each resource group, 41 If the resource type is not SUNW.LogicalHostname or 42 SUNW.SharedAddress or SUNW.HAStorage then enable resource using 44 scswitch -e -j <resource> 46 2. Verify that resource is enabled. Also other resources 47 and resource groups should continue to be online. 49 3. Get the nodelist where this resource group can be mastered and 53 4. Use client program to verify that the resource is available.`
test_15.txt	`33 Removing the resource group should be successful. 38 1. Remove all the resource groups using : 44 Verify that the resource groups are removed.`
test_16.txt	`33 Removing the resource type should be successful. 38 Run through all the resource_group structures and for each resource 39 group structure, run through all the resource structures and for 40 each resource structure, do the following. 44 Remove the resource type (check if it already removed): 48 where i is the number of resource_group, and j is the number of resource. 53 Verify resource type: 61 where i is the number of resource_group, and j is the number of resource.`
test_7.txt	`39 1. Run through all the resource groups, for each resource group, 42 If the resource type is not SUNW.LogicalHostname or 43 SUNW.SharedAddress or SUNW.HAStorage then disable resource using 45 scswitch -n -M -j <resource> 47 2. Verify that resource is online and not monitored. Also other resources 48 and resource groups should continue to be online. 50 3. Get the nodelist where this resource group can be mastered and`
test_8.txt	`39 1. Run through all the resource groups, for each resource group, 42 If the resource type is not SUNW.LogicalHostname or 43 SUNW.SharedAddress or SUNW.HAStorage then enable resource using 45 scswitch -e -M -j <resource> 47 2. Verify that resource is enabled. Also other resources 48 and resource groups should continue to be online. 50 3. Get the nodelist where this resource group can be mastered and`
test_1.txt	`33 Registration of Resource types for the data service should be successful. 38 Run through all the resource_group structures and for each resource 39 group structure, run through all the resource structures and for 40 each resource structure, do the following. 44 Add the resource type (check if it already added): 48 where i is the number of resource_group, and j is the number of resource. 53 Verify resource type: 61 where i is the number of resource_group, and j is the number of resource.`
test_2.txt	`33 Creation of resource group(s) and resources should be successful. 38 1. Create the resource group from one of the nodes in the cluster. 40 2. Verify that the resource group is created from all the nodes 43 3. Create all the resources in the resource group 46 4. Verification of resource creation from all the nodes in the cluster.`
test_6.txt	`33 Bringing the resource group(s) offline should be successful. 38 1. Bring all the resource groups offline using : 44 Verify that the resource groups are offline and that all the resources 48 resource are not running.`
test_3.txt	`33 Bringing the resource group(s) online should be successful. 38 1. Bring all the resource groups online on one of the cluster nodes using : 43 Verify that the resource groups are online and that all the resources 44 in the groups are online, but only on the node where resource group 48 resource are up and running.`
test_11.txt	`33 If the fault monitor daemon processes associated with a resource are 39 1. For all resource groups: 41 If the resource group is failover, run the following code from the node 44 If the resource group is scalable, run the following code from any one 47 2. For all the resources in the resource group: 48 For all the Fault Monitor Daemons associated with the resource:`
test_18.txt	`33 If a daemon process associated with a resource is killed, it should 39 1. For all resource groups: 41 If the resource group is failover, run the following code from the node 44 If the resource group is scalable, run the following code from any one 47 2. For all the resources in the resource group: 48 For all the Daemon processes associated with the resource:`
test_19.txt	38 Run through all the resource groups in the loop, 39 do one node rebooting for all the resources of each resource group. 41 1. Startup the next resource group and all the resources 42 into the resource group on the cluster 46 In the case of failover resource group, get the cluster node 47 on which resource group is online along with the zone name. 50 In the case of scalable resource group, since there are multiple 58 4. Verify that Resource group is online on only one other 59 node/zone of the cluster, in the case of failover resource group or 60 Resource group is online on the some rest nodes/zones [all...]
test_10.txt	`41 1. Run through all the resource groups, for each resource group, 42 run through all the resources, for each resource, run through 43 all the resource daemons.`
/test/ohacts/src/tset/dataservice/scripts/
disable_rg_resources.ksh	`84 for resource in $resource_list 86 RESOURCE_LIST="$resource $RESOURCE_LIST" 111 resource=$1 115 if [[ $resource = $res ]]; then 121 str="$resource - Unknown resource" 132 for resource in $RESOURCE_LIST 149 resource=$1 150 get_resource_number $resource 187 # The enable $res resource depend [all...]`
remove_rg_resources.ksh	`34 # 1 if any resource is not removed or removed uncorrectly. 89 for resource in $resource_list 91 RESOURCE_LIST="$resource $RESOURCE_LIST" 119 resource=$1 123 if [[ $resource = $res ]] 130 str="$resource - Unknown resource" 141 for resource in $RESOURCE_LIST 159 resource=$1 160 get_resource_number $resource [all...]`
/test/ohacts/src/tset/dataservice/doc/assertions/
dataservice	32 1. Registration of Resource types for the data service should be successful. 34 2. Creation of resource group(s) and resources should be successful. 36 3. Bringing the resource group(s) online should be successful. 42 6. Bringing the resource group(s) offline should be successful. 50 9. Switchover of resource groups containing the application resources 58 11. If the fault monitor daemon processes associated with a resource are 63 13. Unmanage the resource group and manage it again should be successful. 65 14. Removing application resource should be successful. 67 15. Removing the resource group should be successful. 69 16. Removing the resource type should be successful [all...]
dataservice_reboot	`38 3. Failback property of the resource group should work as expected. 42 5. After the node is rebooted all the resource groups should come online.`
/test/ohacts/src/doc/dataservice/reboot/
test_3.txt	33 Failback property of the resource group should work as expected. 38 Run through all the resource groups in the loop, 39 do one node rebooting for all the resources of each resource group. 41 1. Startup the next resource group and all the resources 42 into the resource group on the cluster 44 2. Set the value of the failback property of the current Resource 49 In the case of failover resource group, get the cluster node 50 on which resource group is online. That node is the primary and 53 In the case of scalable resource group, since there are multiple 61 5. Verify that Resource group is online on only one othe [all...]
test_5.txt	32 After the node is rebooted all the resource groups should come online. 37 Run through all the resource groups in the loop, 38 do one node rebooting for all the resources of each resource group. 40 1. Startup the next resource group and all the resources 41 into the resource group on the cluster 45 In the case of failover resource group, get the cluster node 46 on which resource group is online. That node is the primary and 49 In the case of scalable resource group, since there are multiple 57 4. Verify that Resource group is online on only one other 58 node of the cluster, in the case of failover resource group o [all...]
test_1.txt	39 Run through all the resource groups in the loop, 40 do one node rebooting for all the resources of each resource group. 42 1. Startup the next resource group and all the resources 43 into the resource group on the cluster 47 In the case of failover resource group, get the cluster node 48 on which resource group is online. That node is the primary and 51 In the case of scalable resource group, since there are multiple 59 4. Verify that Resource group is online on only one other 60 node of the cluster, in the case of failover resource group or 61 Resource group is online on the some rest nodes [all...]
test_2.txt	39 Run through all the resource groups in the loop, 40 do one node rebooting for all the resources of each resource group. 42 1. Startup the next resource group and all the resources 43 into the resource group on the cluster 47 In the case of failover resource group, get the cluster node 48 on which resource group is online. That node is the primary. 50 In the case of scalable resource group, since there are multiple 58 4. Verify that Resource group is online on only one other 59 node of the cluster, in the case of failover resource group or 60 Resource group is online on the some rest nodes [all...]
/test/ohacts/src/doc/dataservice/
testcases	33 1. Registration of Resource types for the data service should be successful. 35 2. Creation of resource group(s) and resources should be successful. 37 3. Bringing the resource group(s) online should be successful. 43 6. Taking the resource groups containing the application resources 52 9. Switchover of resource groups containing the application resources 60 11. If the fault monitor daemon processes associated with a resource are 65 13. Unmanage the resource group and manage it again should be successful. 67 14. Removing application resource should be successful. 69 15. Removing the resource group should be successful. 71 16. Removing the resource type should be successful [all...]

Completed in 240 milliseconds

1 2 3 4 5 6