SLES4SAP-hana-angi-scaleout-perfopt-15.adoc: examples

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

@@ -1355,6 +1355,8 @@ command as _{refsidadm}_ user on the primary site.
 This script prints a human-readable table of the system replication channels and their status. The
 most interesting column is the **Replication Status**, which should be **ACTIVE**.
 
+// TODO PRIO2: variables for sid and site
+
 [subs="specialchars,attributes,quotes"]
 ----
 | Database | Host   | .. Site Name | Secondary | .. Secondary | .. **Replication**
@@ -2162,6 +2164,72 @@ which are self explaining in an SAP context.
 Beside these parameters, the timeout values or the operations (start, monitor,
 stop) are typical values to be adjusted for your environment.
 
+
+==== SAPHanaFilesystem
+
+This step is to define the resources to monitor the filesystem used by HANA, e.g.
+/hana/shared/<SID>. The RA just monitors the filesystem, but neither does mount nor
+umount it. Mounting and umounting is done by the OS thru /etc/fstab.
+
+If necessary, change the *SID* and *instance number* (bold) to appropriate
+values for your setup.
+
+.Configure SAPHanaFilesystem
+==========
+[subs="specialchars,attributes"]
+----
+{mySite1FirstNode}:~ # vi crm-saphanafil.txt
+----
+
+Enter the following to _crm-saphanafil.txt_:
+
+// TODO PRIO3: check notify="true" interleave="true" clone-node-max="1"  vs. meta clone-node-max="1" interleave="true", see man page
+[subs="attributes,quotes"]
+----
+primitive rsc_SAPHanaFil_{refSID}_HDB{refInst} ocf:suse:SAPHanaFilesystem \
+    op monitor interval="120" timeout="120" \
+    op start interval="0" timeout="10" \
+    op stop interval="0" timeout="20" \
+    params SID="**{refSID}**" InstanceNumber="**{refInst}**" ACTION_ON_FAIL="fence"
+
+clone cln_SAPHanaFil_{refSID}_HDB{refInst} rsc_SAPHanaFil_{refSID}_HDB{refInst} \
+    meta clone-node-max="1" interleave="true"
+----
+
+// !! The example title MUST NOT include a line break in the ADOC source !!
+//.In our setup we replace {refSID} by {mySID} and {refInst} by {Inst}
+//=========================
+[subs="attributes,specialchars,quotes"]
+----
+primitive rsc_SAPHanaFil\_**{SID}**_HDB**{Inst}** ocf:suse:SAPHanaFilesystem \
+    op monitor interval="120" timeout="120" \
+    op start interval="0" timeout="10" \
+    op stop interval="0" timeout="20" \
+    params SID="**{SID}**" InstanceNumber="**{Inst}**" ACTION_ON_FAIL="fence"
+
+clone cln_SAPHanaFil_**{SID}**\_HDB**{Inst}** rsc_SAPHanaFil_**{SID}**_HDB**{Inst}** \
+    meta clone-node-max="1" interleave="true"
+----
+//=========================
+
+For additional information about all parameters, use the command
+`man ocf_suse_SAPHanaFilesystem`.
+
+Again, add the configuration to the cluster.
+
+[subs="specialchars,attributes"]
+----
+# crm configure load update crm-saphanafil.txt
+----
+==========
+
+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.
+Beside these parameters, the timeout values or the operations (start, monitor,
+stop) are typical values to be adjusted for your environment.
+
+
 ==== SAPHanaController
 
 Next, define the group of resources needed, before the {saphana} instances can be