diff --git a/SAPHanaSR-tester.spec b/SAPHanaSR-tester.spec index c3e7f30e..9e868ed2 100644 --- a/SAPHanaSR-tester.spec +++ b/SAPHanaSR-tester.spec @@ -20,7 +20,7 @@ License: GPL-2.0 Group: Productivity/Clustering/HA AutoReqProv: on Summary: Test suite for SAPHanaSR clusters -Version: 1.2.14 +Version: 1.3.5 Release: 0 Url: https://www.suse.com/c/fail-safe-operation-of-sap-hana-suse-extends-its-high-availability-solution/ @@ -109,6 +109,7 @@ install -m 0444 man-tester-client/*.7.gz %{buildroot}%{_mandir}/man7 /usr/lib/%{name}/saphana_sr_*.py /usr/bin/SAPHanaSR-testCluster /usr/bin/SAPHanaSR-checkJson +/usr/bin/SAPHanaSR-testSelect /usr/bin/sct_* /usr/bin/callTest* /usr/bin/loopTests* diff --git a/alert/SAPHanaSR-alert-fencing b/alert/SAPHanaSR-alert-fencing index 6005e254..ab340498 100755 --- a/alert/SAPHanaSR-alert-fencing +++ b/alert/SAPHanaSR-alert-fencing @@ -1,14 +1,14 @@ #!/bin/bash # -# SAPHanaSR-alert +# SAPHanaSR-alert-fencing # Author: Lars Pinne Fabian Herschel, June 2024 # Support: linux@sap.com # License: GNU General Public License (GPL) # Copyright: (c) 2024 SUSE LLC -# Version: 2024-06-18-15:33 +# Version: 2024-08-09-14:35 # -# crm configure alert nodes-1 "/usr/bin/SAPHanaSR-alert" select nodes -# crm configure alert fencing-1 "/usr/bin/SAPHanaSR-alert" select fencing attributes alert_uptime_threshold=300 +# crm configure alert nodes-1 "/usr/bin/SAPHanaSR-alert-fencing" select nodes +# crm configure alert fencing-1 "/usr/bin/SAPHanaSR-alert-fencing" select fencing attributes alert_uptime_threshold=300 # logger_tag="SAPHanaSR-alert-fencing" @@ -20,13 +20,12 @@ crm_alert_kind="${CRM_alert_kind:-manual call}" crm_alert_node="${CRM_alert_node:-$HOSTNAME}" crm_alert_desc="${CRM_alert_desc:-no description provided}" -$logger -t "$logger_tag" "AH: begin event '$crm_alert_kind'" cache_file="/run/crm/SAPHanaSR_site_cache" alert_uptime_threshold="${alert_uptime_threshold:-300}" IFS=. read -r sys_uptime REST 0 +Usage, syntax or execution errors. +.PP +.\" +.PP +.\" +.SH EXAMPLES +.PP +\fB*\fP Check one of the predefined files. +.PP +.RS 2 +# SAPHanaSR-checkJson --file /usr/share/SAPHanaSR-tester/json/angi-ScaleUp/maintenance_cluster_hana_running.json +.RE +.PP +.\" +.SH FILES +.TP +/usr/bin/SAPHanaSR-checkJson +the program itself. +.PP +.\" +.SH REQUIREMENTS +.PP +See REQUIREMENTS section in SAPHanaSR-tester(7) and SAPHanaSR-tests-syntax(5). +.PP +.\" +.SH BUGS +.PP +In case of any problem, please use your favourite SAP support process to open +a request for the component BC-OP-LNX-SUSE. +Please report any other feedback and suggestions to feedback@suse.com. +.PP +.\" +.SH SEE ALSO +.PP +\fBSAPHanaSR-tester\fP(7) , \fBSAPHanaSR-tests-syntax\fP(5) , +\fBSAPHanaSR-tests-classic-ScaleUp\fP(7) , +\fBSAPHanaSR-tests-angi-ScaleUp\fP(7) , \fBSAPHanaSR-tests-angi-ScaleOut\fP(7) +.PP +.\" +.SH AUTHORS +.PP +F.Herschel, L.Pinne. +.PP +.\" +.SH COPYRIGHT +.PP +(c) 2023-2024 SUSE LLC +.br +The package SAPHanaSR-tester comes with ABSOLUTELY NO WARRANTY. +.br +For details see the GNU General Public License at +http://www.gnu.org/licenses/gpl.html +.\" diff --git a/man-tester/SAPHanaSR-testCluster.8 b/man-tester/SAPHanaSR-testCluster.8 index 385ac46d..8702927a 100644 --- a/man-tester/SAPHanaSR-testCluster.8 +++ b/man-tester/SAPHanaSR-testCluster.8 @@ -1,20 +1,20 @@ -.\" Version: 1.001 +.\" Version: 1.2.4 .\" -.TH SAPHanaSR-testCluster 8 "03 Apr 2024" "" "SAPHanaSR-angi" +.TH SAPHanaSR-testCluster 8 "24 Nov 2024" "" "SAPHanaSR-angi" .\" .SH NAME SAPHanaSR-testCluster \- Run functional tests for SAPHanaSR clusters. .PP .\" .SH SYNOPSIS -.\" +.PP \fBSAPHanaSR-testCluster\fR [ --help | --version ] .br \fBSAPHanaSR-testCluster\fR \fIOPTION\fR [ \fIOPTION\fR ... ] .PP .\" .SH DESCRIPTION -.\" +.PP SAPHanaSR-testCluster is a tool to run one of the predefined test cases on a given test cluster. For that purpose it is called with options specifying the test case and the properties of the cluster to be tested. @@ -23,7 +23,6 @@ and test automation frameworks. .PP .\" .SH OPTIONS -.\" .TP --help print help message and exit. @@ -40,6 +39,9 @@ print and log debug messages. --logFile \fIFILE\fP path to log file. .TP +--password \fIPASSWORD\fP +remote root user´s password (for debugging only). +.TP --printTestProperties print test properties and exit. .TP @@ -60,10 +62,10 @@ path to testcase description file. .TP --version print version and exit. - .PP .\" .SH RETURN CODES +.PP .B 0 Successful program execution. .br @@ -72,7 +74,6 @@ Usage, syntax or execution errors. .PP .\" .SH EXAMPLES -.\" .PP \fB*\fR Running a very basic functional test. .PP @@ -118,7 +119,6 @@ Test ID is 8585, logfile is test.log, debug output is omitted. .PP .\" .SH FILES -.\" .TP /usr/bin/SAPHanaSR-testCluster the program itself. @@ -127,10 +127,10 @@ the program itself. functional tests for SAPHanaSR-angi scale-up scenarios. .TP /usr/share/SAPHanaSR-tester/json/angi-ScaleOut/ -functional tests for SAPHanaSR-angi scale-out ERP scenarios, without HANA host auto-autofailover. +functional tests for SAPHanaSR-angi scale-out ERP scenarios, without HANA host auto-failover. .TP /usr/share/SAPHanaSR-tester/json/angi-ScaleOut-BW/ -functional tests for SAPHanaSR-angi scale-out BW scenarios, with HANA host auto-autofailover. Not yet implemented. +functional tests for SAPHanaSR-angi scale-out BW scenarios, with HANA host auto-failover. Not yet implemented. .TP /usr/share/SAPHanaSR-tester/json/classic-ScaleUp/ functional tests for SAPHanaSR classic scale-up scenarios. @@ -144,36 +144,43 @@ not yet implemented. $PWD/.test_properties auto-generated properties file for called shell scripts. No need to touch. .TP -/usr/bin/ -TODO +/usr/bin/SAPHanaSR-showAttr +script SAPHanaSR-showAttr from SAPHanaSR-angi. +.TP +/usr/bin/sct_test_* +shell scripts for un-easy tasks on the cluster nodes. .PP .\" .SH REQUIREMENTS -.\" +.PP See the REQUIREMENTS section in SAPHanaSR-tester(7) and SAPHanaSR-angi(7). Of course, HANA database and Linux cluster have certain requirements. Please refer to the product documentation. .PP .\" .SH BUGS +.PP In case of any problem, please use your favourite SAP support process to open a request for the component BC-OP-LNX-SUSE. Please report any other feedback and suggestions to feedback@suse.com. .PP .\" .SH SEE ALSO +.PP \fBSAPHanaSR-tester\fP(7) , \fBSAPHanaSR-tests-syntax\fP(5) , -\fBSAPHanaSR-tests-description\fP(7) , +\fBSAPHanaSR-tests-description\fP(7) , \fBSAPHanaSR-tests-classic-ScaleUp\fP(7) , \fBSAPHanaSR-tests-angi-ScaleUp\fP(7) , \fBSAPHanaSR-tests-angi-ScaleOut\fP(7) , \fBSAPHanaSR-angi\fP(7) , \fBSAPHanaSR-showAttr\fP(8) , -\fBcrm_mon\fP(8) , \fBcrm\fP(8) , \fBcs_clusterstate\fP(8) +\fBcrm_mon\fP(8) , \fBcrm\fP(8) , \fBcs_clusterstate\fP(8) , \fBcs_show_cluster_actions\fP(8) , .PP .\" .SH AUTHORS +.PP F.Herschel, L.Pinne. .PP .\" .SH COPYRIGHT +.PP (c) 2023-2024 SUSE LLC .br The package SAPHanaSR-tester comes with ABSOLUTELY NO WARRANTY. diff --git a/man-tester/SAPHanaSR-tester.7 b/man-tester/SAPHanaSR-tester.7 index c933b477..c1113079 100644 --- a/man-tester/SAPHanaSR-tester.7 +++ b/man-tester/SAPHanaSR-tester.7 @@ -1,49 +1,50 @@ -.\" Version: 1.001 +.\" Version: 1.2.4 .\" -.TH SAPHanaSR-tester 7 "04 Jul 2024" "" "SAPHanaSR-angi" +.TH SAPHanaSR-tester 7 "20 Nov 2024" "" "SAPHanaSR-angi" .\" .SH NAME SAPHanaSR-tester \- Functional testing for SAPHanaSR clusters. .PP .\" .SH DESCRIPTION -.\" +.PP SAPHanaSR-tester is a suite of tools for automating functional tests of SAP HANA system replication HA clusters. - +.PP .B SAPHanaSR-tester is shipped as technology preview. - +.PP The package is focussing on functional tests for the SAPHanaSR resource agents, -the related configuration of the Linux cluster and the SAP HANA database pair. +alert agents, HA/DR provider hook scripts, the related configuration of the Linux +cluster and the SAP HANA database pair. In addition to this functional tests, specific tests for the underlying infrastructure, Linux OS and cluster as well as the database need to be done. See manual page SAPHanaSR-tests-basic-cluster(7). - +.PP SAPHanaSR-tester provides predefined functional tests for scale-up and scale-out scenarios. This tests could be run out-of-the-box. The predefined tests also can be used for creating new test definitions. So parameters for timing and expected attributes can be customised. - +.PP The test cases are defined in dedicated files. Each test is separated into steps. For each step there is an expectation for SAPHanaSR attributes, which need to match. Additionally each step defines the 'next' step and an optional action to be triggered if the step status has been reached (all expectations match). - +.PP The tests usually are self-contained and can run in any order. Entry point always is a clean and idle Linux cluster and a clean HANA pair in sync. Same is true for the final state. Of course the HANA sites may change during the test. Consequently, each predefined test starts and ends with checking the clean status of the HANA pair. - +.PP For tests involving complex actions on the cluster nodes, predefined shell scripts are executed remotely. - +.PP Input - Processing - Output .\" TODO - +.PP \fB*\fP Input: Test cases and test system properties - +.PP a. Test cases are defined in JSON files. Each case is described in one file. It also can reference to defaults.json for common status definitions. Each step contains an expectation for SAPHanaSR attributes, which need to @@ -52,23 +53,23 @@ Each test step status is described by one or more conditions. Each condition is described by one comparision. See manual page SAPHanaSR-tests-syntax(5) for details, see also the EXAMPLES section in SAPHanaSR-tests-angi-ScaleUp(7) and SAPHanaSR-tests-angi-ScaleOut(7). - +.PP b. Test system properties are defined in JSON files. This properties are decribing the test system. The properties are separated from the test cases, because they need to be adapted for each system. The values are static during test run and common for all test on one system. The test cases on the other hand are mostly similar for all test systems. See manual page SAPHanaSR-tests-syntax(5) for details, see also example below. - +.PP \fB*\fP Processing: - +.PP .\" TODO SAPHanaSR-testCluster .\" TODO shell scripts shiped with SAPhanaSR-tester, e.g. sct_test_ .\" TODO custom scripts and test automation frameworks See manual page SAPHanaSR-testCluster(8) and SAPHanaSR-tests-description(7). - +.PP \fB*\fP Output: Test results - +.PP .\" TODO output of SAPHanaSR-testCluster See manual page SAPHanaSR-testCluster(8) and SAPHanaSR-tests-description(7). .PP @@ -88,7 +89,7 @@ node1 and node2, SID is Q42, instance number is 85, HANA´s virtual IP address i .br # zypper in python3-paramiko .br -# ssh-kegen -t rsa -b 4096 +# ssh-keygen -t rsa -b 4096 .br # ssh-copy-id root@node1 .br @@ -160,19 +161,18 @@ while read; do echo $REPLY; grep "name" $REPLY | head -1; done .PP .\" .SH FILES -.\" .TP /usr/share/SAPHanaSR-tester/json/angi-ScaleUp/ functional tests for SAPHanaSR-angi scale-up scenarios. .TP /usr/share/SAPHanaSR-tester/json/angi-ScaleOut/ -functional tests for SAPHanaSR-angi scale-out ERP scenarios, without HANA host auto-autofailover. +functional tests for SAPHanaSR-angi scale-out ERP scenarios, without HANA host auto-failover. .TP /usr/share/SAPHanaSR-tester/json/angi-ScaleOut-BW/ -functional tests for SAPHanaSR-angi scale-out BW scenarios, with HANA host auto-autofailover. Not yet implemented. +functional tests for SAPHanaSR-angi scale-out BW scenarios, with HANA host auto-failover. Not yet implemented. .TP /usr/share/SAPHanaSR-tester/json/classic-ScaleUp/ -not yet implemented. +functional tests for SAPHanaSR classic scale-up scenarios. .TP /usr/share/SAPHanaSR-tester/json/classic-ScaleOut/ not yet implemented. @@ -191,11 +191,13 @@ SAPHanaSR-showAttr, compatible to SAPHanaSR-angi and SAPHanaSR-tester .PP .\" .SH REQUIREMENTS -.\" +.PP For the current version of the SAPHanaSR-tester, the capabilities are limited to the following: .PP -\fB*\fP Resource agents and configuration of SAPHanaSR-angi is supported. +\fB*\fP SLES-for-SAP 15 SP4 or newer. +.PP +\fB*\fP Resource agents and configuration of SAPHanaSR-angi 1.2 or newer is supported. .PP \fB*\fP Resource agents and configuration of SAPHanaSR or SAPHanaSR-ScaleOut with additional package SAPHanaSR-tester-client is supported. @@ -203,6 +205,9 @@ with additional package SAPHanaSR-tester-client is supported. \fB*\fP Scale-up setups with or without multi-target replication. No scale-up multi-SID (MCOS) setups. .PP +\fB*\fP The tester checks cluster attributes via SAPHanaSR-showAttr. It only +detects an status represented by those attributes. +.PP \fB*\fP Scale-out setups with or without multi-target replication. No HANA host auto-failover. .PP @@ -216,7 +221,8 @@ login as database user SYSTEM into the HANA database. This is only needed for some test cases. .PP \fB*\fP Package python3-paramiko is needed on the tester machine for the -tester´s multi-node feature. +tester´s multi-node feature. The cluster nodes need to run an openssh-server +compatible to that python3-paramiko. .PP \fB*\fP Package ClusterTools2 is needed on the cluster nodes. .PP @@ -228,6 +234,11 @@ If disk-based SBD is used, then service sbd enabled and SBD_STARTMODE=always is needed for this tests. The stonith-action=reboot is needed in any case. This cluster basics might be different for production. .PP +\fB*\fP In some cases the various timings for stonith and service startup might +need alignement to prevent fenced nodes from re-joining the cluster before the +resource takeover has been finished. This most likely applies if stonith-timeout +is long, but the cluster nodes are booting very fast. +.PP \fB*\fP Sufficient disk space, particularly for HANA transaction logs, e.g. /hana/log/. Depending on the backup implementation, also space for log backups might be needed, e.g. /hana/shared//HDB/backup/. Strict housekeeping @@ -238,6 +249,7 @@ Most tests are disruptive. .PP .\" .SH BUGS +.PP The SAPHanaSR-tester is under development. Syntax and formats are subject to change. .br @@ -247,8 +259,10 @@ Please report any other feedback and suggestions to feedback@suse.com. .PP .\" .SH SEE ALSO +.PP \fBSAPHanaSR-testCluster\fP(8) , \fBSAPHanaSR-tests-syntax\fP(5) , -\fBSAPHanaSR-tests-description\fP(7) , +\fBSAPHanaSR-tests-description\fP(7) , +\fBSAPHanaSR-tests-description_on-fail-fence\fP(7) , \fBSAPHanaSR-tests-angi-ScaleUp\fP(7) , \fBSAPHanaSR-tests-angi-ScaleOut\fP(7) , \fBSAPHanaSR-tests-classic-ScaleUp\fP(7) , \fBSAPHanaSR-angi\fP(7) , \fBSAPHanaSR-showAttr\fP(8) , \fBcrm_mon\fP(8) , @@ -262,10 +276,12 @@ https://www.suse.com/releasenotes/ .PP .\" .SH AUTHORS +.PP F.Herschel, L.Pinne. .PP .\" .SH COPYRIGHT +.PP (c) 2023-2024 SUSE LLC .br The package SAPHanaSR-tester comes with ABSOLUTELY NO WARRANTY. diff --git a/man-tester/SAPHanaSR-tests-angi-ScaleOut.7 b/man-tester/SAPHanaSR-tests-angi-ScaleOut.7 index efce76f9..43508fc9 100644 --- a/man-tester/SAPHanaSR-tests-angi-ScaleOut.7 +++ b/man-tester/SAPHanaSR-tests-angi-ScaleOut.7 @@ -1,6 +1,6 @@ -.\" Version: 1.001 +.\" Version: 1.2.4 .\" -.TH SAPHanaSR-tests-angi-ScaleOut 7 "20 Dec 2023" "" "SAPHanaSR-angi" +.TH SAPHanaSR-tests-angi-ScaleOut 7 "30 Sep 2024" "" "SAPHanaSR-angi" .\" .SH NAME SAPHanaSR-tests-angi-ScaleOut \- Functional tests for SAPHanaSR Scale-Out. @@ -13,17 +13,20 @@ be run out-of-the-box. The test cases are defined in dedicated files. See manual page SAPHanaSR-tests-syntax(5) for syntax details. Details like performed steps or expected behaviour of cluster and HANA are explained in SAPHanaSR-tests-description(7). - +.PP Each test can be executed by running the command SAPHanaSR-testCluster with appropriate parameters. See manual page SAPHanaSR-testCluster(8). .PP -Predefined functional tests for scale-out ERP overwiev: +Overview on predefined functional tests for scale-out ERP: .TP \fBblock_manual_takeover\fP Blocked manual takeover, for susTkOver.py. .TP +\fBblock_sr\fP +Block HANA SR between master nodes and check SFAIL attribute, unblock to recover, for susHanaSR.py. +.TP \fBblock_sr_and_freeze_prim_master_nfs\fP -Block HANA SR and freeze HANA NFS on primary master node. Not yet implemented. +Block HANA SR and freeze HANA NFS on primary master node. .TP \fBblock_sr_and_freeze_prim_site_nfs\fP Block HANA SR and freeze HANA NFS on primary site. Not yet implemented. @@ -38,52 +41,79 @@ Freeze HANA NFS on primary master node. Freeze HANA NFS on primary site. .TP \fBfreeze_secn_site_nfs\fP -Freeze HANA NFS on secondary site. Not yet implemented. +Freeze HANA NFS on secondary site. .TP \fBkill_prim_indexserver\fP -Kill primary master indexserver, for susChkSrv.py. +Kill primary master indexserver, for susChkSrv.py (action_on_lost=kill). .TP \fBkill_prim_inst\fP Kill primary master instance. .TP +\fBkill_prim_ipaddr\fP +Kill primary HANA´s IP address once. +.TP +\fBkill_prim_nameserver\fP +Kill primary master nameserver. Not yet implemented. +.TP \fBkill_prim_node\fP -Kill primary master node (no fencing alert agent configured). +Kill primary master node. +.TP +\fBkill_prim_pacemakerd\fP +Kill primary master node´s pacemakerd (PCMK_fail_fast=yes). .TP -\fBkill_prim_node_fencing_alert\fP -Kill primary master node (fencing alert agent configured). +\fBkill_prim_pacemkr-ctrld\fP +Kill primary master node´s pacemaker-controld (PCMK_fail_fast=yes). .TP \fBkill_prim_worker_indexserver\fP -Kill primary worker indexserver, for susChkSrv.py. +Kill primary worker indexserver, for susChkSrv.py (action_on_lost=kill). .TP \fBkill_prim_worker_inst\fP Kill primary worker instance. .TP \fBkill_prim_worker_node\fP -Kill primary worker node (no fencing alert agent configured). +Kill primary worker node. .TP -\fBkill_prim_worker_node_fencing_alert\fP -Kill primary master node (fencing alert agent configured). +\fBkill_prim_worker_pacemakerd\fP +Kill primary worker node´s pacemakerd (PCMK_fail_fast=yes). +.TP +\fBkill_prim_worker_pacemkr-ctrld\fP +Kill primary worker node´s pacemaker-controld (PCMK_fail_fast=yes). .TP \fBkill_prim_site\fP Kill primary site nodes. Not yet implemented. .TP \fBkill_secn_indexserver\fP -Kill secondary master indexserver, for susChkSrv.py. +Kill secondary master indexserver, for susChkSrv.py (action_on_lost=kill). .TP \fBkill_secn_inst\fP Kill secondary master instance. .TP +\fBkill_secn_nameserver\fP +Kill secondary master nameserver. Not yet implemented. +.TP \fBkill_secn_node\fP Kill secondary master node. .TP +\fBkill_secn_pacemakerd\fP +Kill secondary master node´s pacemakerd (PCMK_fail_fast=yes). +.TP +\fBkill_secn_pacemkr-ctrld\fP +Kill secondary master node´s pacemaker-controld (PCMK_fail_fast=yes). +.TP +\fBkill_secn_site\fP +Kill secondary site nodes. Not yet implemented. +.TP \fBkill_secn_worker_inst\fP Kill secondary worker instance. .TP \fBkill_secn_worker_node\fP Kill secondary worker node. .TP -\fBkill_secn_site\fP -Kill secondary site nodes. Not yet implemented. +\fBkill_secn_worker_pacemakerd\fP +Kill secondary worker node´s pacemakerd (PCMK_fail_fast=yes). +.TP +\fBkill_secn_worker_pacemkr-ctrld\fP +Kill secondary worker node´s pacemaker-controld (PCMK_fail_fast=yes). .TP \fBmaintenance_cluster_bootstrap\fP Maintenance procedure, initially configuring cluster resources. Not yet implemented. @@ -147,28 +177,36 @@ shell scripts for un-easy tasks on the cluster nodes. .SH REQUIREMENTS .PP See the REQUIREMENTS section in SAPHanaSR-tester(7) and SAPHanaSR-angi(7). +Further, HANA database and Linux cluster are configured according to the SUSE +setup guide for the scale-out ERP style scenario (two nodes per site, no standby). +No immediate fencing is configured, except for the SAPHanaFilesystem RA. Of course, HANA database and Linux cluster have certain requirements. Please refer to the product documentation. .\" .SH BUGS +.PP In case of any problem, please use your favourite SAP support process to open a request for the component BC-OP-LNX-SUSE. Please report any other feedback and suggestions to feedback@suse.com. .PP .\" .SH SEE ALSO +.PP \fBSAPHanaSR-tester\fP(7) , \fBSAPHanaSR-testCluster\fP(8) , \fBSAPHanaSR-tests-description\fP(7) , \fBSAPHanaSR-tests-syntax\fP(5) , +\fBSAPHanaSR-tests-angi-ScaleOut_on-fail-fence\fP(7) , \fBSAPHanaSR-tests-angi-ScaleUp\fP(7) , \fBSAPHanaSR-angi\fP(7) , \fBSAPHanaSR-showAttr\fP(8) .PP .\" .SH AUTHORS +.PP F.Herschel, L.Pinne. .PP .\" .SH COPYRIGHT -(c) 2023 SUSE LLC +.PP +(c) 2023-2024 SUSE LLC .br The package SAPHanaSR-tester comes with ABSOLUTELY NO WARRANTY. .br diff --git a/man-tester/SAPHanaSR-tests-angi-ScaleOut_on-fail-fence.7 b/man-tester/SAPHanaSR-tests-angi-ScaleOut_on-fail-fence.7 index b38ee3e6..7db11725 100644 --- a/man-tester/SAPHanaSR-tests-angi-ScaleOut_on-fail-fence.7 +++ b/man-tester/SAPHanaSR-tests-angi-ScaleOut_on-fail-fence.7 @@ -1,6 +1,6 @@ -.\" Version: 1.001 +.\" Version: 1.2.4 .\" -.TH SAPHanaSR-tests-angi-ScaleOut 7 "06 Jul 2024" "" "SAPHanaSR-angi" +.TH SAPHanaSR-tests-angi-ScaleOut_on-fail-fence 7 "30 Sep 2024" "" "SAPHanaSR-angi" .\" .SH NAME SAPHanaSR-tests-angi-ScaleOut_on-fail-fence \- Functional tests for SAPHanaSR Scale-Out with immediate fencing. @@ -10,58 +10,67 @@ SAPHanaSR-tests-angi-ScaleOut_on-fail-fence \- Functional tests for SAPHanaSR Sc .PP Functional test are shipped for the scale-out ERP scenario when configured for immediate fencing. See manual page ocf_suse_SAPHanaController(7), susChkSrv.py(7) -nd SAPHanaSR-alert-fencing(8) for the respective configuration details. This +and SAPHanaSR-alert-fencing(8) for the respective configuration details. This tests could be run out-of-the-box. The test cases are defined in dedicated files. See manual page SAPHanaSR-tests-syntax(5) for syntax details. Details like performed steps or expected behaviour of cluster and HANA are explained in SAPHanaSR-tests-description(7). - +.PP Each test can be executed by running the command SAPHanaSR-testCluster with appropriate parameters. See manual page SAPHanaSR-testCluster(8). .PP -Predefined functional tests specific for scale-out ERP with immediate fencing overwiev: +Overview on predefined functional tests specific for scale-out ERP with immediate fencing: .TP \fBfreeze_prim_master_nfs_fencing_alert\fP -Freeze HANA NFS on primary master node. +Freeze HANA NFS on primary master node, for SAPHanaFilesystem (fencing alert agent configured). +.TP +\fBkill_prim_indexserver_fencing_alert\fP +Kill primary master indexserver, for susChkSrv.py (action_on_lost=fence and fencing alert agent configured). .TP -\fBkill_prim_indexserver_on_fail_fence\fP -Kill primary master indexserver, for susChkSrv.py. +\fBkill_prim_inst_fencing_alert\fP +Kill primary master instance, for SAPHanaController (ON_FAIL_ACTION=fence and fencing alert agent configured). .TP -\fBkill_prim_inst\fP -Kill primary master instance. +\fBkill_prim_nic_fencing_alert\fP +Kill primary HANA network interface (IPAddr2 start on-fail=fence, fencing alert agent configured). Not yet implemented. .TP \fBkill_prim_node_fencing_alert\fP Kill primary master node (fencing alert agent configured). .TP -\fBkill_prim_worker_indexserver_on_fail_fence\fP -Kill primary worker indexserver, for susChkSrv.py. +\fBkill_prim_pacemakerd_fencing_alert\fP +Kill primary master node´s pacemakerd (PCMK_fail_fast=yes and fencing alert agent configured). +.TP +\fBkill_prim_pacemkr-ctrld_fencing_alert\fP +Kill primary master node´s pacemaker-controld (PCMK_fail_fast=yes and fencing alert agent configured). .TP -\fBkill_prim_worker_inst\fP -Kill primary worker instance. +\fBkill_prim_worker_indexserver_fencing_alert\fP +Kill primary worker indexserver, for susChkSrv.py (action_on_lost=fence and fencing alert agent configured). .TP -\fBkill_prim_worker_node\fP -Kill primary worker node (no fencing alert agent configured). +\fBkill_prim_worker_inst_fencing_alert\fP +Kill primary worker instance, for SAPHanaController (ON_FAIL_ACTION=fence and fencing alert agent configured). .TP \fBkill_prim_worker_node_fencing_alert\fP -Kill primary master node (fencing alert agent configured). +Kill primary worker node (fencing alert agent configured). .TP -\fBkill_secn_indexserver\fP -Kill secondary master indexserver, for susChkSrv.py. +\fBkill_secn_indexserver_fencing_alert\fP +Kill secondary master indexserver, for susChkSrv.py (action_on_lost=fence and fencing alert agent configured). .TP -\fBkill_secn_inst\fP -Kill secondary master instance. +\fBkill_secn_node_fencing_alert\fP +Kill secondary master node (fencing alert agent configured). .TP -\fBkill_secn_node\fP -Kill secondary master node. +\fBkill_secn_pacemakerd_fencing_alert\fP +Kill secondary master node´s pacemakerd (PCMK_fail_fast=yes and fencing alert agent configured). .TP -\fBkill_secn_worker_inst\fP -Kill secondary worker instance. +\fBkill_secn_pacemkr-ctrld_fencing_alert\fP +Kill secondary master node´s pacemaker-controld (PCMK_fail_fast=yes and fencing alert agent configured). .TP -\fBkill_secn_worker_node\fP -Kill secondary worker node. +\fBkill_secn_worker_indexserver_fencing_alert\fP +Kill secondary worker indexserver, for susChkSrv.py (action_on_lost=fence and fencing alert agent configured). .TP -\fBkill_secn_site\fP -Kill secondary site nodes. Not yet implemented. +\fBkill_secn_worker_node_fencing_alert\fP +Kill secondary worker node (fencing alert agent configured). +.PP +More recommended tests, but not specific to immediate fencing, are listed in +manual page SAPHanaSR-tests-angi-ScaleOut(7). .PP .\" .SH EXAMPLES @@ -85,8 +94,11 @@ shell scripts for un-easy tasks on the cluster nodes. .SH REQUIREMENTS .PP See the REQUIREMENTS section in SAPHanaSR-tester(7) and SAPHanaSR-angi(7). -See also ocf_suse_SAPHanaController(7), susChkSrv.py(7) and -SAPHanaSR-alert-fencing(8) for configuration. +Further, HANA database and Linux cluster are configured almost according to the +SUSE setup guide for the scale-out ERP style scenario (two nodes per site, no +standby). In opposite to that guide, immediate fencing is configured. +See ocf_suse_SAPHanaController(7), susChkSrv.py(7) and +SAPHanaSR-alert-fencing(8). Of course, HANA database and Linux cluster have certain requirements. Please refer to the product documentation. .\" @@ -98,8 +110,9 @@ Please report any other feedback and suggestions to feedback@suse.com. .\" .SH SEE ALSO \fBSAPHanaSR-tester\fP(7) , \fBSAPHanaSR-testCluster\fP(8) , +\fBSAPHanaSR-tests-description_on-fail-fence\fP(7) , \fBSAPHanaSR-tests-description\fP(7) , \fBSAPHanaSR-tests-syntax\fP(5) , -\fBSAPHanaSR-tests-angi-ScaleOu\fP(7) , +\fBSAPHanaSR-tests-angi-ScaleOut\fP(7) , \fBSAPHanaSR-angi\fP(7) , \fBSAPHanaSR-showAttr\fP(8) , \fBocf_suse_SAPHanaController\fP(7) , \fBsusChkSrv.py\fP(7) , \fBSAPHanaSR-alert-fencing\fP(8) diff --git a/man-tester/SAPHanaSR-tests-angi-ScaleUp.7 b/man-tester/SAPHanaSR-tests-angi-ScaleUp.7 index 067bc91b..5e00cbed 100644 --- a/man-tester/SAPHanaSR-tests-angi-ScaleUp.7 +++ b/man-tester/SAPHanaSR-tests-angi-ScaleUp.7 @@ -1,6 +1,6 @@ -.\" Version: 1.001 +.\" Version: 1.2.4 .\" -.TH SAPHanaSR-tests-angi-ScaleUp 7 "20 Dec 2023" "" "SAPHanaSR-angi" +.TH SAPHanaSR-tests-angi-ScaleUp 7 "18 Sep 2024" "" "SAPHanaSR-angi" .\" .SH NAME SAPHanaSR-tests-angi-ScaleUp \- Functional tests for SAPHanaSR Scale-Up. @@ -14,13 +14,16 @@ See manual page SAPHanaSR-tests-syntax(5) for syntax details. Details like performed steps or expected behaviour of cluster and HANA are explained in SAPHanaSR-tests-description(7). .PP -Predefined functional tests for scale-up overview: +Each test can be executed by running the command SAPHanaSR-testCluster with +appropriate parameters. See manual page SAPHanaSR-testCluster(8). +.PP +Overview on predefined functional tests for scale-up: .TP \fBblock_manual_takeover\fP Blocked manual takeover, for susTkOver.py. .TP \fBblock_sr\fP -Block HANA SR and check SFAIL attribute; unblock to recover, for SAPHanaSR.py. +Block HANA SR and check SFAIL attribute, unblock to recover, for susHanaSR.py. .TP \fBblock_sr_and_freeze_prim_fs\fP Block HANA SR and freeze HANA FS on primary master node. @@ -34,24 +37,51 @@ Free HANA log area on primary site. \fBfreeze_prim_fs\fP Freeze HANA FS on primary master node. .TP +\fBfreeze_secn_fs\fP +Freeze HANA FS on secondary master node. +.TP \fBkill_prim_indexserver\fP -Kill primary indexserver, for susChkSrv.py. +Kill primary indexserver, for susChkSrv.py (action_on_lost=kill). .TP \fBkill_prim_inst\fP Kill primary instance. .TP +\fBkill_prim_ipaddr\fP +Kill primary HANA IP address once. +.TP +\fBkill_prim_nameserver\fP +Kill primary nameserver. +.TP +\fBkill_prim_nic\fP +Kill primary HANA network interface (IPAddr2 start on-fail=fence). Not yet implemented. +.TP \fBkill_prim_node\fP Kill primary node. .TP +\fBkill_prim_pacemakerd\fP +Kill primary pacemakerd (PCMK_fail_fast=yes). +.TP +\fBkill_prim_pacemkr-ctrld\fP +Kill primary pacemaker-controld (PCMK_fail_fast=yes). +.TP \fBkill_secn_indexserver\fP -Kill secondary indexserver, for susChkSrv.py. +Kill secondary indexserver, for susChkSrv.py (action_on_lost=kill). .TP \fBkill_secn_inst\fP Kill secondary instance. .TP +\fBkill_secn_nameserver\fP +Kill secondary nameserver. +.TP \fBkill_secn_node\fP Kill secondary node. .TP +\fBkill_secn_pacemakerd\fP +Kill secondary pacemakerd (PCMK_fail_fast=yes). +.TP +\fBkill_secn_pacemkr-ctrld\fP +Kill secondary pacemaker-controld (PCMK_fail_fast=yes). +.TP \fBmaintenance_cluster_bootstrap\fP Maintenance procedure, initially configuring cluster resources. .TP @@ -81,7 +111,7 @@ Stop and restart cluster and HANA. .TP \fBrestart_cluster_turn_hana\fP Stop cluster and HANA, manually start and takeover HANA, start cluster. -.PP +.TP \fBsplit_brain_prio\fP Network split-brain with priority fencing. .TP @@ -114,6 +144,9 @@ shell scripts for un-easy tasks on the cluster nodes. .SH REQUIREMENTS .\" See the REQUIREMENTS section in SAPHanaSR-tester(7) and SAPHanaSR-angi(7). +Further, HANA database and Linux cluster are configured according to the SUSE +setup guide for the scale-up performance-optimised scenario. +No immediate fencing is configured, except for the SAPHanaFilesystem RA. Of course, HANA database and Linux cluster have certain requirements. Please refer to the product documentation. .PP @@ -136,7 +169,7 @@ F.Herschel, L.Pinne. .PP .\" .SH COPYRIGHT -(c) 2023 SUSE LLC +(c) 2023-2024 SUSE LLC .br The package SAPHanaSR-tester comes with ABSOLUTELY NO WARRANTY. .br diff --git a/man-tester/SAPHanaSR-tests-angi-ScaleUp_on-fail-fence.7 b/man-tester/SAPHanaSR-tests-angi-ScaleUp_on-fail-fence.7 index f6e2eb43..29a2a0d0 100644 --- a/man-tester/SAPHanaSR-tests-angi-ScaleUp_on-fail-fence.7 +++ b/man-tester/SAPHanaSR-tests-angi-ScaleUp_on-fail-fence.7 @@ -1,6 +1,6 @@ .\" Version: 1.001 .\" -.TH SAPHanaSR-tests-angi-ScaleUp 7 "06 Jul 2024" "" "SAPHanaSR-angi" +.TH SAPHanaSR-tests-angi-ScaleUp_on-fail-fence 7 "30 Sep 2024" "" "SAPHanaSR-angi" .\" .SH NAME SAPHanaSR-tests-angi-ScaleUp_on-fail-fence \- Functional tests for SAPHanaSR Scale-Up with immediate fencing. @@ -16,19 +16,22 @@ See manual page SAPHanaSR-tests-syntax(5) for syntax details. Details like performed steps or expected behaviour of cluster and HANA are explained in SAPHanaSR-tests-description(7). .PP -Predefined functional tests specific for scale-up with immediate fencing overview: -.TP -\fBkill_prim_indexserver_onfail_fence\fP -Kill primary indexserver, for susChkSrv.py. +Each test can be executed by running the command SAPHanaSR-testCluster with +appropriate parameters. See manual page SAPHanaSR-testCluster(8). +.PP +Overview on predefined functional tests specific for scale-up with immediate fencing: .TP -\fBkill_prim_inst_onfail_fence\fP -Kill primary instance. +\fBkill_prim_indexserver_fencing\fP +Kill primary indexserver, for susChkSrv.py (action_on_lost=fence). .TP -\fBkill_secn_indexserver_onfail_fence\fP -Kill secondary indexserver, for susChkSrv.py. +\fBkill_prim_inst_fencing\fP +Kill primary instance, for SAPHanaController (ON_FAIL_ACTION=fence). .TP -\fBkill_secn_inst_onfail_fence\fP -Kill secondary instance. +\fBkill_secn_indexserver_fencing\fP +Kill secondary indexserver, for susChkSrv.py (action_on_lost=fence). +.PP +More recommended tests, but not specific to immediate fencing, are listed in +manual page SAPHanaSR-tests-angi-ScaleUp(7). .PP .\" .SH EXAMPLES @@ -53,7 +56,11 @@ shell scripts for un-easy tasks on the cluster nodes. .SH REQUIREMENTS .\" See the REQUIREMENTS section in SAPHanaSR-tester(7) and SAPHanaSR-angi(7). -See also ocf_suse_SAPHanaController(7) and susChkSrv.py(7) for configuration. +Further, HANA database and Linux cluster are configured almost according to the +SUSE setup guide for the scale-up performance-optimised scenario. +In opposite to that guide, immediate fencing is configured. +See ocf_suse_SAPHanaController(7), susChkSrv.py(7) and +SAPHanaSR-alert-fencing(8). Of course, HANA database and Linux cluster have certain requirements. Please refer to the product documentation. .PP @@ -66,6 +73,7 @@ Please report any other feedback and suggestions to feedback@suse.com. .\" .SH SEE ALSO \fBSAPHanaSR-tester\fP(7) , \fBSAPHanaSR-testCluster\fP(8) , +\fBSAPHanaSR-tests-description_on-fail-fence\fP(7) , \fBSAPHanaSR-tests-description\fP(7) , \fBSAPHanaSR-tests-syntax\fP(5) , \fBSAPHanaSR-tests-angi-ScaleUp\fP(7) , \fBSAPHanaSR-angi\fP(7) , \fBSAPHanaSR-showAttr\fP(8) , diff --git a/man-tester/SAPHanaSR-tests-basic-cluster.7 b/man-tester/SAPHanaSR-tests-basic-cluster.7 index 1cd9f603..ffd5ad75 100644 --- a/man-tester/SAPHanaSR-tests-basic-cluster.7 +++ b/man-tester/SAPHanaSR-tests-basic-cluster.7 @@ -1,6 +1,6 @@ -.\" Version: 1.001 +.\" Version: 1.2.4 .\" -.TH SAPHanaSR-tests-basic-cluster 7 "20 Nov 2023" "" "SAPHanaSR-angi" +.TH SAPHanaSR-tests-basic-cluster 7 "30 Sep 2024" "" "SAPHanaSR-angi" .\" .SH NAME SAPHanaSR-tests-basic-cluster \- Checking SAPHanaSR clusters basics. @@ -162,22 +162,24 @@ grep -e "NOPASSWD.*crm_attribute" -e "NOPASSWD.*SAPHanaSR-hookHelper" .PP .\" .SH FILES -.\" .TP /etc/hosts - +local hostname resolution .TP /etc/chrony.d/* - +config files for chrony daemon .TP /etc/modprobe.d/* .TP /etc/sysconfig/sbd - +config file for SBD daemon +.TP +/etc/sysconfig/pacemaker +config file for pacemaker daemon .TP /etc/corosync/corosync.conf - +config file for corosync daemon .TP /etc/sudoers, /etc/sudoers.d/* the sudo permissions configuration @@ -193,19 +195,21 @@ path to HANA tracefiles .PP .\" .SH REQUIREMENTS -.\" +.PP See the REQUIREMENTS section in SAPHanaSR-tester(7) and SAPHanaSR-angi(7). Of course, the Linux cluster has certain requirements. Please refer to the product documentation. .PP .\" .SH BUGS +.PP In case of any problem, please use your favourite SAP support process to open a request for the component BC-OP-LNX-SUSE. Please report any other feedback and suggestions to feedback@suse.com. .PP .\" .SH SEE ALSO +.PP \fBSAPHanaSR-tester\fP(7) , \fBSAPHanaSR-angi\fP(7) , \fBSAPHanaSR_basic_cluster\fP(7) , \fBSAPHanaSR-ScaleOut_basic_cluster\fP(7) , \fBsusHanaSR.py\fP(7) , \fBsusTkOver.py\fP(7) , \fBsusChkSrv.py\fP(7) , @@ -213,7 +217,6 @@ Please report any other feedback and suggestions to feedback@suse.com. \fBcs_show_error_patterns\fP(8) , \fBcs_sum_base_config\fP(8) , \fBcs_show_sbd_devices\fP(8) , \fBsbd\fP(8) , \fBstonith_sbd\fP(8) , \fBsaptune\fP(8) , \fBchronyc\fP(8) , \fBsystemctl\fP(8) , \fBhosts\fP(5) , -\fBsystemctl\fP(8) , .br https://documentation.suse.com/sbp/sap/ , .br @@ -225,11 +228,13 @@ https://www.suse.com/releasenotes/ .PP .\" .SH AUTHORS +.PP F.Herschel, L.Pinne. .PP .\" .SH COPYRIGHT -(c) 2023 SUSE LLC +.PP +(c) 2023-2024 SUSE LLC .br The package SAPHanaSR-tester comes with ABSOLUTELY NO WARRANTY. .br diff --git a/man-tester/SAPHanaSR-tests-classic-ScaleUp.7 b/man-tester/SAPHanaSR-tests-classic-ScaleUp.7 index 5787fb75..0d800c65 100644 --- a/man-tester/SAPHanaSR-tests-classic-ScaleUp.7 +++ b/man-tester/SAPHanaSR-tests-classic-ScaleUp.7 @@ -1,6 +1,6 @@ -.\" Version: 1.001 +.\" Version: 1.2.4 .\" -.TH SAPHanaSR-tests-classic-ScaleUp 7 "29 Feb 2024" "" "SAPHanaSR-angi" +.TH SAPHanaSR-tests-classic-ScaleUp 7 "26 Nov 2024" "" "SAPHanaSR-angi" .\" .SH NAME SAPHanaSR-tests-classic-ScaleUp \- Functional tests for SAPHanaSR Scale-Up. @@ -14,7 +14,7 @@ See manual page SAPHanaSR-tests-syntax(5) for syntax details. Details like performed steps or expected behaviour of cluster and HANA are explained in SAPHanaSR-tests-description(7). .PP -Predefined functional tests for SAPHanaSR scale-up overview: +Overview on predefined functional tests for classical SAPHanaSR scale-up: .TP \fBblock_manual_takeover\fP Blocked manual takeover, for susTkOver.py. @@ -29,29 +29,52 @@ Like nop but very short sleep, just checking the test engine. Free HANA log area on primary site. .TP \fBkill_prim_indexserver\fP -Kill primary indexserver, for susChkSrv.py. +Kill primary indexserver, for susChkSrv.py (action_on_lost=kill). .TP \fBkill_prim_inst\fP Kill primary instance. .TP +\fBkill_prim_ipaddr\fP +Kill primary HANA IP address once. +.TP +\fBkill_prim_nameserver\fP +Kill primary nameserver. +.TP +\fBkill_prim_nic\fP +Kill primary HANA network interface (IPAddr2 start on-fail=fence). +.TP \fBkill_prim_node\fP Kill primary node. .TP +\fBkill_prim_pacemakerd\fP +Kill primary pacemakerd (PCMK_fail_fast=yes). +.TP +\fBkill_prim_pacemkr-ctrld\fP +Kill primary pacemaker-controld (PCMK_fail_fast=yes). +.TP \fBkill_secn_indexserver\fP -Kill secondary indexserver, for susChkSrv.py. +Kill secondary indexserver, for susChkSrv.py (action_on_lost=kill). .TP \fBkill_secn_inst\fP Kill secondary instance. .TP +\fBkill_secn_nameserver\fP +Kill secondary nameserver. +.TP \fBkill_secn_node\fP Kill secondary node. .TP +\fBkill_secn_pacemakerd\fP +Kill secondary pacemakerd (PCMK_fail_fast=yes). +.TP +\fBkill_secn_pacemkr-ctrld\fP +Kill secondary pacemaker-controld (PCMK_fail_fast=yes). +.TP \fBmaintenance_cluster_bootstrap\fP Maintenance procedure, initially configuring cluster resources. Not yet implemented. .TP \fBmaintenance_cluster_hana_running\fP Maintenance procedure with stopping and restarting cluster, keep HANA running. -.\" former restart_cluster_hana_running .TP \fBmaintenance_cluster_turn_hana\fP Maintenance procedure, manually turning HANA sites. @@ -65,6 +88,9 @@ No operation - check, wait and check again (stability check). \fBone_stable_hour\fP Check regulary for one hour that there is no failure, like nop. .TP +\fBrestart_cluster\fP +Stop and restart cluster and HANA. +.TP \fBsplit_brain_prio\fP Network split-brain with priority fencing. .TP @@ -91,10 +117,9 @@ Set secondary node standby and online again. .PP .\" .SH FILES -.\" .TP /usr/share/SAPHanaSR-tester/json/classic-ScaleUp/ -functional tests for SAPHanaSR scale-up scenarios. +functional tests for SAPHanaSR classic scale-up scenarios. .TP /usr/bin/sct_test_* shell scripts for un-easy tasks on the cluster nodes. @@ -104,33 +129,41 @@ script SAPHanaSR-showAttr from SAPHanaSR-angi. .PP .\" .SH REQUIREMENTS -.\" +.PP * The package SAPHanaSR-tester-client is needed on the cluster nodes. .PP * See also the REQUIREMENTS section in SAPHanaSR-tester(7) and SAPHanaSR(7). .PP +* HANA database and Linux cluster are configureded according to the SUSE setup +guide for scale-up performance-optimised scenario (classical SAPHanaSR). +.PP * Of course, HANA database and Linux cluster have certain requirements. Please refer to the product documentation. .PP .\" .SH BUGS +.PP In case of any problem, please use your favourite SAP support process to open a request for the component BC-OP-LNX-SUSE. Please report any other feedback and suggestions to feedback@suse.com. .PP .\" .SH SEE ALSO +.PP \fBSAPHanaSR-tester\fP(7) , \fBSAPHanaSR-testCluster\fP(8) , \fBSAPHanaSR-tests-description\fP(7) , \fBSAPHanaSR-tests-syntax\fP(5) , \fBSAPHanaSR-tests-ScaleOut\fP(7) , -\fBSAPHanaSR\fP(7) , \fBSAPHanaSR-showAttr\fP(8) +\fBSAPHanaSR\fP(7) , \fBSAPHanaSR-showAttr\fP(8) , +\fBSAPHanaSR-tester-client\fP(7) .PP .\" .SH AUTHORS +.PP F.Herschel, L.Pinne. .PP .\" .SH COPYRIGHT +.PP (c) 2024 SUSE LLC .br The package SAPHanaSR-tester comes with ABSOLUTELY NO WARRANTY. diff --git a/man-tester/SAPHanaSR-tests-description.7 b/man-tester/SAPHanaSR-tests-description.7 index ab4e9d28..98dbccf3 100644 --- a/man-tester/SAPHanaSR-tests-description.7 +++ b/man-tester/SAPHanaSR-tests-description.7 @@ -1,6 +1,6 @@ -.\" Version: 1.001 +.\" Version: 1.2 .\" -.TH SAPHanaSR-tests-description 7 "04 Jul 2024" "" "SAPHanaSR-angi" +.TH SAPHanaSR-tests-description 7 "26 Nov 2024" "" "SAPHanaSR-angi" .\" .SH NAME SAPHanaSR-tests-description \- Functional tests for SAPHanaSR. @@ -13,16 +13,16 @@ out-of-the-box. The test cases are defined in dedicated files. See manual page SAPHanaSR-tests-syntax(5) for syntax details. Tests for SAPHanaSR-angi scale-up scenarios are listed in SAPHanaSR-tests-angi-ScaleUp(7), for SAPHanaSR-angi scale-out ERP scenarios in SAPHanaSR-tests-angi-ScaleOut(7). - +.PP Entry point for all predefined tests is a clean and idle Linux cluster and a clean HANA pair in sync. Same is true for the final state. See manual page SAPHanaSR_maintenance_examples(7) for detecting the correct status and watching changes near real-time. - +.PP Each test can be executed by running the command SAPHanaSR-testCluster with appropriate parameters. See manual page SAPHanaSR-testCluster(8). .PP -Predefined functional tests: +Predefined functional tests without immediate fencing: .PP \fBblock_manual_takeover\fP .RS 2 @@ -204,6 +204,25 @@ One takeover. One fence. Comment: Infrastructure failure, main cluster case. .RE .PP +\fBfreeze_secn_fs\fP +.RS 2 +Descr: Freeze HANA FS on secondary node. +.br +Topology: ScaleUp (angi only). +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: See ocf_suse_SAPHanaFilesystem(7). +Freeze is shorter than SAPHanaController monitor timeout. +.br +Expect: Primary keeps running. +HANA secondary keeps running. +SR SFAIL and finally SOK. +No takeover. No fence. +.br +Comment: Infrastructure failure, main cluster case. +.RE +.PP \fBfreeze_secn_site_nfs\fP .RS 2 Freeze HANA NFS on secondary site. @@ -251,7 +270,7 @@ Topology: ScaleUp, ScaleOut. .br Prereq: Cluster and HANA are up and running, all good. .br -Test: HDB kill +Test: HDB kill-9 .br Expect: Primary (master) node stays online. HANA primary (master) stopped and finally started as secondary. @@ -262,9 +281,66 @@ One takeover. No fencing. Comment: Application failure, main cluster case. .RE .PP +\fBkill_prim_ipaddr\fP +.RS 2 +Descr: Kill primary HANA´s IP address once. +.br +Topology: ScaleUp, ScaleOut. +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: ip a d dev +.br +Expect: IP address is recovered. +All nodes stay online. +Primary and secondary HANA stay online. +No takeover. No fencing. +.br +Comment: +.RE +.PP +\fBkill_prim_nameserver\fP +.RS 2 +Descr: Kill primary nameserver. +On scale-out, kill primary master nameserver (not yet implemented). +.br +Topology: ScaleUp, ScaleOut. +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: killall -11 hdbnameserver +.br +Expect: Primary (master) nameserver restarted. +HANA primary temporarily degraded (lss=2), no Linux cluster resource failure. +No takeover. No fencing. +.br +Comment: Application failure, HANA recovers on its own. +.RE +.PP +.TP +\fBkill_prim_nic\fP +.RS 2 +Descr: Kill primary HANA network interface. +On scale-out, kill primary master HANA network interface (not yet implemented). +.br +Topology: ScaleUp, ScaleOut. +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: TODO (IPAddr2 start on-fail=fence). +.br +Expect: Primary (master) node fenced and finally started as secondary. +HANA primary stopped and finally started as secondary. +HANA secondary becomes finally primary. +SR SFAIL and finally SOK. +One takeover. One fencing. +.br +Comment: Infrastructure failure. +.RE +.PP \fBkill_prim_node\fP .RS 2 -Descr: Kill primary node (no fencing alert agent configured). +Descr: Kill primary node. On scale-out, kill primary master node. .br Topology: ScaleUp, ScaleOut. @@ -282,24 +358,43 @@ One takeover. One fencing. Comment: Node failure, main cluster case. .RE .PP -\fBkill_prim_node_fencing_alert\fP +\fBkill_prim_pacemakerd\fP .RS 2 -Descr: Kill primary node (fencing alert agent configured). -On scale-out, kill primary master node. +Descr: Kill primary pacemakerd. +On scale-out, kill primary master node´s pacemakerd. .br -Topology: ScaleOut. +Topology: ScaleUp, ScaleOut. .br Prereq: Cluster and HANA are up and running, all good. .br -Test: systemctl reboot --force +Test: killall -9 pacemakerd .br -Expect: All primary nodes fenced and finally started as secondary. +Expect: Primary (master) pacemakerd restarted. +Both HANA stay online. +SR stays SOK. +No takeover. No fencing. +.br +Comment: Cluster failure. +.RE +.PP +\fBkill_prim_pacemkr-ctrld\fP +.RS 2 +Descr: Kill primary pacemaker-controld. +On scale-out, kill primary master node´s pacemaker-controld. +.br +Topology: ScaleUp, ScaleOut. +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: killall -9 pacemaker-controld +.br +Expect: Primary (master) node fenced (for PCMK_fast_fail=yes). HANA primary stopped and finally started as secondary. HANA secondary becomes finally primary. SR SFAIL and finally SOK. -One takeover. One fencing for each primary node. +One takeover. One fencing. .br -Comment: Node failure, main cluster case. +Comment: Cluster failure. .RE .PP \fBkill_prim_worker_indexserver\fP @@ -328,7 +423,7 @@ Topology: ScaleOut. .br Prereq: Cluster and HANA are up and running, all good. .br -Test: HDB kill +Test: HDB kill-9 .br Expect: HANA primary stopped and finally started as secondary. HANA secondary becomes finally primary. @@ -357,23 +452,40 @@ One takeover. One fencing. Comment: Node failure, main cluster case. .RE .PP -\fBkill_prim_worker_node_fencing_alert\fP +\fBkill_prim_worker_pacemakerd\fP .RS 2 -Descr: Kill primary worker node (fencing alert agent configured).. +Descr: Kill primary worker node´s pacemakerd. .br Topology: ScaleOut. .br Prereq: Cluster and HANA are up and running, all good. .br -Test: systemctl reboot --force +Test: killall -9 pacemakerd +.br +Expect: Primary worker pacemakerd restarted. +Both HANA stay online. +No takeover. No fencing. +.br +Comment: Cluster failure. +.RE +.PP +\fBkill_prim_worker_pacemkr-ctrld\fP +.RS 2 +Descr: Kill primary worker node´s pacemaker-controld. +.br +Topology: ScaleOut. .br -Expect: All primary nodes fenced. +Prereq: Cluster and HANA are up and running, all good. +.br +Test: killall -9 pacemaker-controld +.br +Expect: Primary worker node fenced (for PCMK_fast_fail=yes). HANA primary stopped and finally started as secondary. HANA secondary becomes finally primary. SR SFAIL and finally SOK. -One takeover. One fencing for each primary node. +One takeover. One fencing. .br -Comment: Node failure, main cluster case. +Comment: Cluster failure. .RE .PP \fBkill_secn_indexserver\fP @@ -404,7 +516,7 @@ Topology: ScaleUp, ScaleOut. .br Prereq: Cluster and HANA are up and running, all good. .br -Test: HDB kill +Test: HDB kill-9 .br Expect: HANA secondary stopped and finally online. HANA primary stays online. @@ -414,6 +526,26 @@ No takeover. No fencing. Comment: Application failure, main cluster case. .RE .PP +\fBkill_secn_nameserver\fP +.RS 2 +Descr: Kill secondary nameserver. +On scale-out, kill secondary master nameserver (not yet implemented). +.br +Topology: ScaleUp, ScaleOut. +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: killall -11 hdbnameserver +.br +Expect: Secondary (master) nameserver restarted. +HANA secondary temporarily degraded (lss=2), no Linux cluster resource failure. +HANA primary stays online. +SR SFAIL and finally SOK. +No takeover. No fencing. +.br +Comment: Application failure, HANA recovers on its own. +.RE +.PP \fBkill_secn_node\fP .RS 2 Descr: Kill secondary node. @@ -433,6 +565,44 @@ No takeover. One fencing. Comment: Node failure, main cluster case. .RE .PP +\fBkill_secn_pacemakerd\fP +.RS 2 +Descr: Kill secondary pacemakerd. +On scale-out, kill secondary master node´s pacemakerd. +.br +Topology: ScaleUp, ScaleOut. +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: killall -9 pacemakerd +.br +Expect: Secondary (master) pacemakerd restarted. +Both HANA stay online. +SR stays SOK. +No takeover. No fencing. +.br +Comment: Cluster failure. +.RE +.PP +\fBkill_secn_pacemkr-ctrld\fP +.RS 2 +Descr: Kill secondary pacemaker-controld. +On scale-out, kill secondary master node´s pacemaker-controld. +.br +Topology: ScaleUp, ScaleOut. +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: killall -9 pacemaker-controld +.br +Expect: Secondary (master) node fenced (for PCMK_fast_fail=yes). +HANA primary stays online. +SR SFAIL and finally SOK. +No takeover. One fencing. +.br +Comment: Cluster failure. +.RE +.PP \fBkill_secn_worker_inst\fP .RS 2 Descr: Kill secondary worker instance. @@ -443,15 +613,30 @@ Prereq: Cluster and HANA are up and running, all good. .br Test: .br -Expect: - -HANA primary stays online. +Expect: HANA primary stays online. SR SFAIL and finally SOK. No takeover. No fencing. .br Comment: Application failure, main cluster case. .RE .PP +\fBkill_secn_worker_pacemkr-ctrld\fP +.RS 2 +Descr: Kill secondary worker node´s pacemaker-controld. +.br +Topology: ScaleOut. +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: killall -9 pacemaker-controld +.br +Expect: TODO. +HANA secondary TODO. +No takeover. TODO fencing. +.br +Comment: Cluster failure. +.RE +.PP \fBkill_secn_worker_node\fP .RS 2 Descr: Kill secondary worker node. @@ -778,6 +963,10 @@ shell scripts for un-easy tasks on the cluster nodes. .SH REQUIREMENTS .\" See the REQUIREMENTS section in SAPHanaSR-tester(7) and SAPHanaSR-angi(7). +Further, HANA database and Linux cluster are configured according to the SUSE +setup guide for the scale-up performance-optimised scenario or the +scale-out ERP style scenario (two nodes per site, no standby). +No immediate fencing is configured, except for the SAPHanaFilesystem RA. Of course, HANA database and Linux cluster also have certain requirements. Please refer to the product documentation. .PP @@ -793,6 +982,7 @@ Please report any other feedback and suggestions to feedback@suse.com. \fBSAPHanaSR-tests-syntax\fP(5) , \fBSAPHanaSR-tests-angi-ScaleUp\fP(7) , \fBSAPHanaSR-tests-angi-ScaleOut\fP(7) , \fBSAPHanaSR-tests-classic-ScaleUp\fP(7) , +\fBSAPHanaSR-tests-description_on-fail-fence\fP(7) , \fBSAPHanaSR-angi\fP(7) , \fBSAPHanaSR-showAttr\fP(8) .PP .\" diff --git a/man-tester/SAPHanaSR-tests-description_on-fail-fence.7 b/man-tester/SAPHanaSR-tests-description_on-fail-fence.7 new file mode 100644 index 00000000..df7eaa38 --- /dev/null +++ b/man-tester/SAPHanaSR-tests-description_on-fail-fence.7 @@ -0,0 +1,333 @@ +.\" Version: 1.001 +.\" +.TH SAPHanaSR-tests-description_on-fail-fence 7 "30 Sep 2024" "" "SAPHanaSR-angi" +.\" +.SH NAME +SAPHanaSR-tests-description_on-fail-fence \- Functional tests for SAPHanaSR with immediate fencing. +.PP +.\" +.SH DESCRIPTION +.PP +Functional test are shipped for different scenarios. This tests could be run +out-of-the-box. The test cases are defined in dedicated files. +See manual page SAPHanaSR-tests-syntax(5) for syntax details. Tests for +SAPHanaSR-angi scale-up scenarios are listed in +SAPHanaSR-tests-angi-ScaleUp_on-fail-fence(7), for SAPHanaSR-angi scale-out ERP +scenarios in SAPHanaSR-tests-angi-ScaleOut_on-fail-fence(7). +.PP +Entry point for all predefined tests is a clean and idle Linux cluster and a +clean HANA pair in sync. Same is true for the final state. +See manual page SAPHanaSR_maintenance_examples(7) for detecting the correct +status and watching changes near real-time. +.PP +Each test can be executed by running the command SAPHanaSR-testCluster with +appropriate parameters. See manual page SAPHanaSR-testCluster(8). +.PP +Predefined functional tests with immediate fencing: +.PP +\fBfreeze_prim_master_nfs_fencing_alert\fP +.RS 2 +Descr: Freeze HANA NFS on primary master node. +.br +Topology: ScaleOut (angi only). +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: See ocf_suse_SAPHanaFilesystem(7). +.br +Expect: Primary nodes fenced. +HANA primary killed and finally started as secondary. +HANA secondary becomes finally primary. +SR SFAIL and finally SOK. +One takeover. All primary nodes fenced. +.br +Comment: Infrastructure failure, main cluster case. +.RE +.PP +\fBkill_prim_indexserver_fencing\fP +.RS 2 +Descr: Kill primary indexserver, for susChkSrv.py. +.br +Topology: ScaleUp (angi only). +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: See susChkSrv.py(7). +.br +Expect: Primary node fenced. +HANA primary killed and finally started as secondary. +HANA secondary becomes finally primary. +SR SFAIL and finally SOK. +One takeover. One fencing (for action_on_lost=fence). +.br +Comment: Application failure, main cluster case +.RE +.PP +\fBkill_prim_indexserver_fencing_alert\fP +.RS 2 +Descr: Kill primary master indexserver, for susChkSrv.py. +.br +Topology: ScaleOut (angi only). +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: See susChkSrv.py(7). +.br +Expect: All primary nodes fenced. +HANA primary killed and finally started as secondary. +HANA secondary becomes finally primary. +SR SFAIL and finally SOK. +One takeover. All primary nodes fenced (for action_on_lost=fence). +.br +Comment: Application failure, main cluster case. +.RE +.PP +\fBkill_prim_inst_fencing\fP +.RS 2 +Descr: Kill primary instance. +.br +Topology: ScaleUp (angi only). +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: HDB kill +.br +Expect: Primary node fenced. +HANA primary killed and finally started as secondary. +HANA secondary becomes finally primary. +SR SFAIL and finally SOK. +One takeover. One fencing. +.br +Comment: Application failure, main cluster case. +.RE +.PP +\fBkill_prim_inst_fencing_alert\fP +.RS 2 +Descr: Kill primary master instance. +.br +Topology: ScaleOut (angi only). +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: HDB kill +.br +Expect: All primary nodes fenced. +HANA primary killed and finally started as secondary. +HANA secondary becomes finally primary. +SR SFAIL and finally SOK. +One takeover. All primary nodes fenced. +.br +Comment: Application failure, main cluster case. +.RE +.PP +\fBkill_prim_node_fencing_alert\fP +.RS 2 +Descr: Kill primary master node. (fencing alert agent configured). +.br +Topology: ScaleOut (angi only). +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: systemctl reboot --force +.br +Expect: All primary nodes fenced. +HANA primary killed and finally started as secondary. +HANA secondary becomes finally primary. +SR SFAIL and finally SOK. +One takeover. All primary nodes fenced. +.br +Comment: Node failure, main cluster case. +.RE +.PP +\fBkill_prim_pacemkr-ctrld_fencing_alert\fP +.RS 2 +Descr: Kill primary master node´s pacemaker-controld. +.br +Topology: ScaleOut (angi only). +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: killall -9 pacemaker-controld +.br +Expect: Primary master node fenced (for PCMK_fast_fail=yes). +HANA primary killed and finally started as secondary. +HANA secondary becomes finally primary. +SR SFAIL and finally SOK. +One takeover. All primary nodes fenced. +.br +Comment: Cluster failure. +.RE +.PP +\fBkill_prim_worker_indexserver_fencing_alert\fP +.RS 2 +Descr: Kill primary worker indexserver, for susChkSrv.py. +.br +Topology: ScaleOut (angi only). +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: See susChkSrv.py(7). +.br +Expect: All primary nodes fenced. +HANA primary killed and finally started as secondary. +HANA secondary becomes finally primary. +SR SFAIL and finally SOK. +One takeover. All primary nodes fenced (for action_on_lost=fence). +.br +Comment: Application failure, main cluster case. +.RE +.PP +\fBkill_prim_worker_inst_fencing_alert\fP +.RS 2 +Descr: Kill primary worker instance. +.br +Topology: ScaleOut (angi only). +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: HDB kill +.br +Expect: All primary nodes fenced. +HANA primary killed and finally started as secondary. +HANA secondary becomes finally primary. +SR SFAIL and finally SOK. +One takeover. All primary nodes fenced. +.br +Comment: Application failure, main cluster case. +.RE +.PP +\fBkill_prim_worker_node_fencing_alert\fP +.RS 2 +Descr: Kill primary worker node. +.br +Topology: ScaleOut (angi only). +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: systemctl reboot --force +.br +Expect: All primary nodes fenced. +HANA primary killed and finally started as secondary. +HANA secondary becomes finally primary. +SR SFAIL and finally SOK. +One takeover. All primary nodes fenced. +.br +Comment: Node failure, main cluster case. +.RE +.PP +\fBkill_prim_worker_pacemkr-ctrld_fencing_alert\fP +.RS 2 +Descr: Kill primary worker node´s pacemaker-controld. +.br +Topology: ScaleOut (angi only). +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: killall -9 pacemaker-controld +.br +Expect: Primary worker node fenced (for PCMK_fast_fail=yes). +HANA primary killed and finally started as secondary. +HANA secondary becomes finally primary. +SR SFAIL and finally SOK. +One takeover. All primary nodes fenced. +.br +Comment: Cluster failure. +.RE +.PP +\fBkill_secn_indexserver_fencing\fP +.RS 2 +Descr: Kill secondary indexserver, for susChkSrv.py. +.br +Topology: ScaleUp. +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: See susChkSrv.py(7). +.br +Expect: Secondary node fenced. +HANA secondary killed and finally restarted. +SR SFAIL and finally SOK. +No takeover. All secondary nodes fenced (for action_on_lost=fence). +.br +Comment: Application failure, main cluster case +.RE +.PP +\fBkill_secn_worker_indexserver_fencing_alert\fP +.RS 2 +Descr: Kill secondary worker indexserver, for susChkSrv.py. +.br +Topology: ScaleOut (angi only). +.br +Prereq: Cluster and HANA are up and running, all good. +.br +Test: See susChkSrv.py(7). +.br +Expect: Secondary nodes fenced. +HANA secondary finally restarted. +SR SFAIL and finally SOK. +No takeover. All secondary nodes fenced (for action_on_lost=fence). +.br +Comment: Application failure, main cluster case +.RE +.PP +.\" +.SH EXAMPLES +.PP +* List all shipped tests for immediate fencing +.PP +.RS 2 +# find /usr/share/SAPHanaSR-tester/json/ -name "*fenc*.json" -exec basename {} \\; | sort -u +.RE +.PP +.\" +.SH FILES +.\" +.TP +/usr/share/SAPHanaSR-tester/json/angi-ScaleUp/ +functional tests for SAPHanaSR-angi scale-up scenarios. +.TP +/usr/share/SAPHanaSR-tester/json/angi-ScaleOut/ +functional tests for SAPHanaSR-angi scale-out ERP scenarios. +.TP +/usr/bin/sct_test_* +shell scripts for un-easy tasks on the cluster nodes. +.PP +.\" +.SH REQUIREMENTS +.\" +See the REQUIREMENTS section in SAPHanaSR-tester(7) and SAPHanaSR-angi(7). +Further, HANA database and Linux cluster are configured almost according to the +SUSE setup guide for the scale-up performance-optimised scenario or the scale-out +ERP style scenario (two nodes per site, no standby). +In opposite to that guide, immediate fencing is configured. +See ocf_suse_SAPHanaController(7), susChkSrv.py(7) and SAPHanaSR-alert-fencing(8). +Of course, HANA database and Linux cluster also have certain requirements. +Please refer to the product documentation. +.PP +.\" +.SH BUGS +In case of any problem, please use your favourite SAP support process to open +a request for the component BC-OP-LNX-SUSE. +Please report any other feedback and suggestions to feedback@suse.com. +.PP +.\" +.SH SEE ALSO +\fBSAPHanaSR-tester\fP(7) , \fBSAPHanaSR-testCluster\fP(8) , +\fBSAPHanaSR-tests-syntax\fP(5) , \fBSAPHanaSR-tests-description\fP(7) , +\fBSAPHanaSR-tests-angi-ScaleOut_on-fail-fence\fP(7) , +\fBSAPHanaSR-tests-angi-ScaleUp_on-fail-fence\fP(7) , +\fBSAPHanaSR-angi\fP(7) , \fBSAPHanaSR-showAttr\fP(8) +.PP +.\" +.SH AUTHORS +F.Herschel, L.Pinne. +.PP +.\" +.SH COPYRIGHT +(c) 2024 SUSE LLC +.br +The package SAPHanaSR-tester comes with ABSOLUTELY NO WARRANTY. +.br +For details see the GNU General Public License at +http://www.gnu.org/licenses/gpl.html +.\" diff --git a/man-tester/SAPHanaSR-tests-syntax.5 b/man-tester/SAPHanaSR-tests-syntax.5 index 0e84e27a..9d617163 100644 --- a/man-tester/SAPHanaSR-tests-syntax.5 +++ b/man-tester/SAPHanaSR-tests-syntax.5 @@ -1,6 +1,6 @@ -.\" Version: 1.001 +.\" Version: 1.2 .\" -.TH SAPHanaSR-tests-syntax 5 "20 Nov 2023" "" "SAPHanaSR-angi" +.TH SAPHanaSR-tests-syntax 5 "19 Nov 2024" "" "SAPHanaSR-angi" .\" .SH NAME SAPHanaSR-tests-syntax \- Syntax for SAPHanaSR test cases and properties. @@ -10,17 +10,17 @@ SAPHanaSR-tests-syntax \- Syntax for SAPHanaSR test cases and properties. .\" SAPHanaSR-tester is a suite of tools for automating functional tests of SAP HANA system replication HA clusters. - +.PP Test cases are defined in dedicated files. Each test is separated into steps. For each step there is an expectation for SAPHanaSR attributes, which need to match. Additionally each step defines the 'next' step and an optional action to be triggered if the step status has been reached (all expectations match). See section SYNTAX below for comparators and other details. - +.PP For tests involving complex actions on the cluster nodes, predefined shell scripts are executed remotely. .\" TODO state machine. - +.PP See manual pages SAPHanaSR-tests-angi-ScaleUp(7) and SAPHanaSR-tests-angi-ScaleOut(7) for predefined test cases. .PP @@ -29,11 +29,11 @@ SAPHanaSR-tests-angi-ScaleOut(7) for predefined test cases. .\" Test cases are defined in JSON files. Each test case is described in one file. It also can reference to defaults.json for common status definitions. - +.PP TODO on first level -[ test | name | start | comment | steps ] +[ test | name | purpose | start | comment | steps ] .\" TODO comment or remark? - +.PP .TP \fBtest\fP test identifier, unique @@ -41,6 +41,9 @@ test identifier, unique \fBname\fP test description .TP +\fBpurpose\fB +list of keywords, indicating which topology, components and case is tested, see below - [ angi | classic ] [ ScaleUp | ScaleOut ] [ master | worker ] [ ... ] +.TP \fBstart\fP name of step to start the test with .TP @@ -48,13 +51,7 @@ name of step to start the test with comment, just a string .TP \fBsteps\fP -test steps, see below -.PP -\fBsteps\fP - -TODO -[ step | name | next | loop | wait | post | comment | ] - +test steps - [ step | name | next | loop | wait | post | comment | ] .TP \fBstep\fP step identifier, unique @@ -76,16 +73,89 @@ comment, just a string .TP \fBstatus\fP status definition, see below - +.TP +\fBstart\fP +name of step to start the test with +.TP +\fBcomment\fP +comment, just a string +.PP +\fB*\fP Test purpose +.\" TODO script to list/find testcases by purpose +.PP +TODO +.TP +alert +test alert agent +.TP +angi +SAPHanaSR-angi +.TP +classic +SAPHanaSR or SAPHanaSR-ScaleOut +.TP +cluster +test cluster failure +.TP +fencing +test leads to node fencing +.TP +hadr +test HANA HA/DR provider hook script +.TP +hana +test HANA failure +.TP +kill +kill something, for testing a failure +.TP +maintenance +test a maintenance procedure +.TP +master +test on HANA master nameserver node +.TP +network +test network failure +.TP +node +test node failure +.TP +primary +test failure at primary site +.TP +protective +configuration variant "protective" +.TP +ScaleOut +scale-out topology +.TP +ScaleUp +scale-up topology +.TP +secondary +test failure at secondary site +.TP +site +failure of complete site (all nodes) +.TP +split-brain +test split-brain +.TP +storage +test storage or IO stack failure +.TP +worker +test on HANA worker node .PP \fB*\fP Test step status .PP Each step contains an expectation for SAPHanaSR attributes, which need to match. The attributes are arranged along the CIB and SAPHanaSR-showAttr sections. The - +.PP [ pHost | sHost | pWorker | sWorker | pSite | sSite | pGlobal | sGlobal ] - +.PP .TP pHost, sHost, pWorker, sWorker node attributes @@ -234,9 +304,6 @@ kill secondary instance (scale-out: secondary master instance) kill_secn_worker_inst kill worker secondary instance (scale-out) .TP -kill_prim_indexserver -kill primary indexserver (scale-out: primary master indexserver) -.TP kill_secn_indexserver kill secondary indexserver (scale-out: secondary master indexserver) .TP @@ -246,6 +313,12 @@ kill primary worker indexserver (scale-out) kill_secn_worker_indexserver kill secondary worker indexserver (scale-out) .TP +kill_secn_nameserver +kill secondary nameserver (scale-out: secondary master nameserver) +.TP +kill_prim_nameserver +kill primary nameserver (scale-out: primary master nameserver) +.TP simulate_split_brain break corosync communcation .TP @@ -268,14 +341,13 @@ online_secn_worker_node online secondary worker node (scale-out) .TP script