You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SAP Testing Automation Framework is an open-source orchestration tool designed to validate SAP deployments on Microsoft Azure. It enables you to assess system configurations against SAP on Azure best practices and guidelines. Additionally, the framework facilitates automation for various testing scenarios, including High Availability (HA) functional testing.
12
15
13
16
> **NOTE**: This repository is currently in private preview and is intended for testing and feedback purposes. As this is an early release, it is not yet production-ready, and breaking changes can be introduced at any time.
The following SAP components are supported in a two-node Pacemaker cluster running on SUSE Linux Enterprise Server (SLES) or Red Hat Enterprise Linux (RHEL):
Copy file name to clipboardExpand all lines: docs/HIGH_AVAILABILITY.md
+61-3Lines changed: 61 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,7 @@ Currently SAP Testing Automation Framework is supported for below Linux distros
20
20
| Component | Type | Cluster Type | Storage |
21
21
|-----------|------|--------------|---------|
22
22
| SAP Central Services | ENSA1 or ENSA2 | Azure Fencing Agent | Azure Files or ANF |
23
+
| SAP Central Services | ENSA1 or ENSA2 | ISCSI (SBD device) | Azure Files or ANF |
23
24
| SAP HANA | Scale-up | Azure Fencing Agent | Azure Managed Disk or ANF |
24
25
| SAP HANA | Scale-up | ISCSI (SBD device) | Azure Managed Disk or ANF |
25
26
@@ -36,6 +37,15 @@ To run the SAP Testing Automation Framework, you must meet certain prerequisites
36
37
-[SAP HANA high availability on Azure Virtual Machine](https://learn.microsoft.com/azure/sap/workloads/sap-high-availability-guide-start).
37
38
-[SAP Netweaver high availability on Azure Virtual Machine](https://learn.microsoft.com/azure/sap/workloads/sap-high-availability-guide-start)
38
39
40
+
### Enabling Cluster Services on Boot
41
+
42
+
Before executing the tests, ensure that the cluster services are configured to start automatically during system boot. Run the following command on one of the cluster nodes to enable this setting. The `--all` option ensures that the cluster services are enabled on all nodes within the cluster.
43
+
44
+
```bash
45
+
crm cluster enable --all # for SUSE virtual machines
46
+
pcs cluster enable --all # for RedHat virtual machine
47
+
```
48
+
39
49
### Management server
40
50
41
51
The SAP Testing Automation Framework requires a jumpbox or management server with the following setup:
@@ -85,14 +95,17 @@ To set up your enviroment in management server, follow these steps:
85
95
86
96
Ensure you are logged into the Ubuntu management server that is connected to the SAP system's virtual network.
@@ -271,6 +284,51 @@ Test results and logs can be found in:
271
284
cd WORKSPACES/SYSTEM/<SYSTEM_CONFIG_NAME>/quality_assurance/
272
285
```
273
286
287
+
## Update the framework
288
+
289
+
To ensure you have the latest features and fixes, it's important to keep your fork of the SAP Testing Automation Framework up to date. You can do this by pulling the latest changes from the original repository into your fork.
290
+
291
+
### Steps to update your fork
292
+
293
+
1. **Ensure you have the upstream repository configured**:
2. **Fetch the latest changes from the upstream repository**:
304
+
305
+
```bash
306
+
git fetch upstream
307
+
```
308
+
309
+
3. **Ensure you're on your main branch**:
310
+
311
+
```bash
312
+
git checkout main
313
+
```
314
+
315
+
4. **Merge the changes from upstream into your local fork**:
316
+
317
+
```bash
318
+
git merge upstream/main
319
+
```
320
+
321
+
5. **Push the updated code to your GitHub fork**:
322
+
323
+
```bash
324
+
git push origin main
325
+
```
326
+
327
+
This process will update your fork with all the latest features, bug fixes, and improvements from the original SAP Testing Automation Framework repository.
328
+
329
+
> [!NOTE]
330
+
> If you've made local changes to your fork, you might encounter merge conflicts during step 4. In that case, you'll need to resolve these conflicts before proceeding with the push in step 5.
331
+
274
332
## Additional Resources
275
333
276
334
- [Azure SAP Documentation](https://docs.microsoft.com/azure/sap)
0 commit comments