SLES4SAP-hana-angi-scaleout-perfopt-15.adoc: fixes, added TODO

adoc/SLES4SAP-hana-angi-scaleout-perfopt-15.adoc

@@ -445,7 +445,8 @@ See also manual page susHanaSR.py(7).
 
 Find more details in the REQUIREMENTS section of manual pages
 SAPHanaSR-ScaleOut(7), ocf_suse_SAPHanaController(7), ocf_suse_SAPHanaFilesystem(7),
-susHanaSR.py(7), SAPHanaSR-manageAttr(8), susChkSrv.py(7) and susTkOver.py(7).
+susHanaSR.py(7), SAPHanaSR-manageAttr(8), susChkSrv.py(7), susTkOver.py(7) and
+SAPHanaSR-alert-fencing(8).
 
 IMPORTANT: You must implement a valid STONITH method. Without a valid STONITH
 method, the complete cluster is unsupported and will not work properly.
@@ -2226,7 +2227,7 @@ Again, add the configuration to the cluster.
 
 The most important parameters here are _SID_ ({SID}) and _InstanceNumber_ ({Inst}),
 which are self explaining in an SAP context. ACTION_ON_FAIL defines how the RA
-should react on monitor failures.
+should react on monitor failures. See also manual page SAPHanaSR-alert-fencing(8).
 Beside these parameters, the timeout values or the operations (start, monitor,
 stop) are typical values to be adjusted for your environment.
 
@@ -2301,54 +2302,6 @@ Add the configuration to the cluster.
 ----
 ==========
 
-////
-// TODO PRIO1: SAPHanaFilesystem RA
-
-
-.Configure SAPHanaFilesystem
-==========
-Enter the following to crm-saphanafil.txt
-
-[subs="specialchars,attributes"]
-----
-primitive rsc_SAPHanaCon_{refSID}_HDB{refInst} ocf:suse:SAPHanaFilesystem \
-    op start interval="0" timeout="120" \
-    op stop interval="0" timeout="120" \
-    op monitor interval="120" timeout="700" \
-    params SID="{refSID}" InstanceNumber="{refInst}"
-
-clone cln_SAPHanaFil_{refSID}_HDB{refInst} \
-    rsc_SAPHanaFil_{refSID}_HDB{refInst} \
-    meta clone-node-max="1" interleave="true"
-----
-
-The most important parameters here are {refSID} ({SID}) and {refInst}
-({Inst}), which are in the SAP context quite self explaining.
-Beside these parameters, the timeout values or the operations (start, monitor,
-stop) are typical tuneables.
-Find more details in manual page ocf_suse_SAPHanaFilesystem(7).
-
-[subs="specialchars,attributes,quotes"]
-----
-primitive rsc_SAPHanaFil_**{SID}**_HDB**{Inst}** ocf:suse:SAPHanaFilesystem \
-    op start interval="0" timeout="120" \
-    op stop interval="0" timeout="120" \
-    op monitor interval="120" timeout="120" \
-    params SID="**{SID}**" InstanceNumber="**{Inst}**"
-
-clone cln_SAPHanaFil_{SID}_HDB{Inst} rsc_SAPHanaFil_{SID}_HDB{Inst} \
-    meta clone-node-max="1" interleave="true"
-----
-
-Add the configuration to the cluster.
-
-[subs="specialchars,attributes"]
-----
-# crm configure load update crm-saphanafil.txt
-----
-==========
-////
-
 // [cols="1,2", options="header"]
 [width="100%",cols="40%,60%",options="header"]
 .Table Description of important Resource Agent parameter
@@ -2545,6 +2498,8 @@ IP address to be presented to the client systems.
 Use the command `man ocf_heartbeat_IPaddr2` for details on additional parameters.
 See also manual page SAPHanaSR-ScaleOut_basic_cluster(7).
 
+// TODO PRIO1: add SAPHanaSR-alert-fencing here or above?
+
 
 === Final steps
 
@@ -2928,8 +2883,8 @@ In your project, *avoid* the following:
 
 You can use the High Availability Web Konsole (HAWK), {saphana} Cockpit and
 different command line tools for cluster status requests. See manual pages
-crm_mon(8), cs_wait_for_idle(8), SAPHanaSR_maintenance_examples(7),
-SAPHanaSR-showAttr(8), SAPHanaSrMultiTarget.py(7) and susChkSrv.py(7).
+crm_mon(8), cs_wait_for_idle(8), SAPHanaSR-ScaleOut_maintenance_examples(7),
+SAPHanaSR-showAttr(8), susHanaSR.py(7) and susChkSrv.py(7).
 
 ==== HAWK – cluster status and more
 
@@ -2938,7 +2893,7 @@ https://<node>:7630
 
 ////
 TODO PRIO3: Discuss some disadvantages of HAWK or missing features:
-S_IDLE? cs_cluterstate or crm_simulate
+S_IDLE? cs_clusterstate or crm_simulate
 cli-? crm configure | grep cli
 failcount? -INF?
 ////