c9
imports/c9/resource-agents-sap-hana-0.162.1-2.el9_2
CentOS Sources
2 years ago
committed by
MSVSphere Packaging Team
parent
0a4731213f
commit
6d4da92123
@ -1,2 +1,2 @@
|
||||
SOURCES/ClusterLabs-resource-agents-e76b7d3a.tar.gz
|
||||
SOURCES/SAPHanaSR-2dea8fe.tar.gz
|
||||
SOURCES/SAPHanaSR-6281418.tar.gz
|
||||
|
||||
@ -1,2 +1,2 @@
|
||||
b1c1e65d690d94e080319217486f8dcd248b2a2a SOURCES/ClusterLabs-resource-agents-e76b7d3a.tar.gz
|
||||
e5ae03dcac77cbb2f5ec85d3785f048c0de0acc0 SOURCES/SAPHanaSR-2dea8fe.tar.gz
|
||||
8d25b08bed4b158d83a2884588a345374efdb500 SOURCES/SAPHanaSR-6281418.tar.gz
|
||||
|
||||
@ -1,30 +0,0 @@
|
||||
From 621c6cc4ca494834f921671a4540b7063a33648e Mon Sep 17 00:00:00 2001
|
||||
From: Frank Danapfel <frank.danapfel@redhat.com>
|
||||
Date: Fri, 12 Nov 2021 11:35:15 +0100
|
||||
Subject: [PATCH] SAPHana: remove info about HANA_CALL_TIMEOUT parameter
|
||||
|
||||
It doesn't make sense to have HANA_CALL_TIMEOUT listed as a parameter since it is hardcoded to 60s and therefore can't be changed.
|
||||
---
|
||||
heartbeat/SAPHana | 9 ---------
|
||||
1 file changed, 9 deletions(-)
|
||||
|
||||
diff --git a/heartbeat/SAPHana b/heartbeat/SAPHana
|
||||
index cd91ddf..5da587d 100755
|
||||
--- a/heartbeat/SAPHana
|
||||
+++ b/heartbeat/SAPHana
|
||||
@@ -242,15 +242,6 @@ The resource agent uses the following four interfaces provided by SAP:
|
||||
</longdesc>
|
||||
<content type="string" default="7200" />
|
||||
</parameter>
|
||||
- <parameter name="HANA_CALL_TIMEOUT" unique="0" required="0">
|
||||
- <shortdesc lang="en">Define timeout how long a call to HANA to receive information can take.</shortdesc>
|
||||
- <longdesc lang="en">Define timeout how long a call to HANA to receive information can take. This could be eg landscapeHostConfiguration.py.
|
||||
- There are some specific calls to HANA which have their own timeout values. For example the takeover command does not timeout (inf).
|
||||
- If the timeout is reached, the return code will be 124. If you increase the timeouts for HANA calls you should also adjust the operation timeouts
|
||||
- of your cluster resources.
|
||||
- </longdesc>
|
||||
- <content type="string" default="60" />
|
||||
- </parameter>
|
||||
<parameter name="DIR_EXECUTABLE" unique="0" required="0">
|
||||
<longdesc lang="en">The full qualified path where to find sapstartsrv and sapcontrol. Specify this parameter, if you have changed the SAP kernel directory location after the default SAP installation.</longdesc>
|
||||
<shortdesc lang="en">Path of sapstartsrv and sapcontrol</shortdesc>
|
||||
@ -1,30 +0,0 @@
|
||||
From 91a6a7fca636972a9604675a99946e8a8e51fd73 Mon Sep 17 00:00:00 2001
|
||||
From: Frank Danapfel <frank.danapfel@redhat.com>
|
||||
Date: Fri, 12 Nov 2021 11:36:33 +0100
|
||||
Subject: [PATCH] SAPHanaTopology: Remove info about HANA_CALL_TIMEOUT
|
||||
|
||||
It doesn't make sense to have HANA_CALL_TIMEOUT listed as a parameter since it is hardcoded to 60s and therefore can't be changed.
|
||||
---
|
||||
heartbeat/SAPHanaTopology | 9 ---------
|
||||
1 file changed, 9 deletions(-)
|
||||
|
||||
diff --git a/heartbeat/SAPHanaTopology b/heartbeat/SAPHanaTopology
|
||||
index afc645c..29819d7 100755
|
||||
--- a/heartbeat/SAPHanaTopology
|
||||
+++ b/heartbeat/SAPHanaTopology
|
||||
@@ -173,15 +173,6 @@ SAPHanaTopology scans the output table of landscapeHostConfiguration.py to ident
|
||||
<shortdesc lang="en">The SAP Instance Number</shortdesc>
|
||||
<content type="string" default="" />
|
||||
</parameter>
|
||||
- <parameter name="HANA_CALL_TIMEOUT" unique="0" required="0">
|
||||
- <shortdesc lang="en">Define timeout how long a call to HANA to receive information can take.</shortdesc>
|
||||
- <longdesc lang="en">Define timeout how long a call to HANA to receive information can take. This could be eg landscapeHostConfiguration.py.
|
||||
- There are some specific calls to HANA which have their own timeout values. For example the takeover command does not timeout (inf).
|
||||
- If the timeout is reached, the return code will be 124. If you increase the timeouts for HANA calls you should also adjust the operation timeouts
|
||||
- of your cluster resources.
|
||||
- </longdesc>
|
||||
- <content type="string" default="60" />
|
||||
- </parameter>
|
||||
<parameter name="DIR_EXECUTABLE" unique="0" required="0">
|
||||
<longdesc lang="en">Path to the SAP Hana Instance executable directory. If not set the RA tries /usr/sap/\$SID/\$InstanceName/exe.
|
||||
While InstanceName is the string of "HDB" and \$InstanceNumber for SAP Hana databases.
|
||||
@ -1,41 +0,0 @@
|
||||
From 182dbd793e9c6ce0e5a0abc7d595a864175248bb Mon Sep 17 00:00:00 2001
|
||||
From: Oyvind Albrigtsen <oalbrigt@redhat.com>
|
||||
Date: Thu, 20 Jan 2022 10:41:51 +0100
|
||||
Subject: [PATCH] SAPHana*: follow OCF standard for version and OCF version in
|
||||
metadata
|
||||
|
||||
---
|
||||
heartbeat/SAPHana | 4 ++--
|
||||
heartbeat/SAPHanaTopology | 4 ++--
|
||||
2 files changed, 4 insertions(+), 4 deletions(-)
|
||||
|
||||
diff --git a/heartbeat/SAPHana b/heartbeat/SAPHana
|
||||
index 295eff0..6527362 100755
|
||||
--- a/heartbeat/SAPHana
|
||||
+++ b/heartbeat/SAPHana
|
||||
@@ -160,8 +160,8 @@ function saphana_meta_data() {
|
||||
cat <<END
|
||||
<?xml version="1.0"?>
|
||||
<!DOCTYPE resource-agent SYSTEM "ra-api-1.dtd">
|
||||
-<resource-agent name="SAPHana">
|
||||
-<version>$SAPHanaVersion</version>
|
||||
+<resource-agent name="SAPHana" version="$SAPHanaVersion">
|
||||
+<version>1.0</version>
|
||||
|
||||
<shortdesc lang="en">Manages two SAP HANA database systems in system replication (SR).</shortdesc>
|
||||
<longdesc lang="en">
|
||||
diff --git a/heartbeat/SAPHanaTopology b/heartbeat/SAPHanaTopology
|
||||
index 3fce400..9ad2101 100755
|
||||
--- a/heartbeat/SAPHanaTopology
|
||||
+++ b/heartbeat/SAPHanaTopology
|
||||
@@ -134,8 +134,8 @@ function sht_meta_data() {
|
||||
cat <<END
|
||||
<?xml version="1.0"?>
|
||||
<!DOCTYPE resource-agent SYSTEM "ra-api-1.dtd">
|
||||
-<resource-agent name="SAPHanaTopology">
|
||||
- <version>$SAPHanaTopologyVersion</version>
|
||||
+<resource-agent name="SAPHanaTopology" version="$SAPHanaTopologyVersion">
|
||||
+ <version>1.0</version>
|
||||
<shortdesc lang="en">Analyzes SAP HANA System Replication Topology.</shortdesc>
|
||||
<longdesc lang="en">This RA analyzes the SAP HANA topology and "sends" all findings via the node status attributes to
|
||||
all nodes in the cluster. These attributes are taken by the SAPHana RA to control the SAP Hana Databases.
|
||||
Loading…
Reference in new issue