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
- collection - Update readme formatting to align with galaxy format (https://github.com/sap-linuxlab/community.sap_install/pull/1148)
19
+
- sap*preconfigure - Sync with SAP notes for RHEL 10 (https://github.com/sap-linuxlab/community.sap_install/pull/1161)
20
+
- sap_general_preconfigure - Prevent an accidental change to a lower SELinux mode (https://github.com/sap-linuxlab/community.sap_install/pull/1154)
21
+
- sap_ha_pacemaker_cluster - Add fence_aws for SLES 16 and remove Tech Debt (https://github.com/sap-linuxlab/community.sap_install/pull/1151)
22
+
- sap_hana_install - Revert wrong conditional from PR#1138 (https://github.com/sap-linuxlab/community.sap_install/pull/1147)
23
+
- sap_swpm - Sanitize conditions for 2.19 (https://github.com/sap-linuxlab/community.sap_install/pull/1159)
Copy file name to clipboardExpand all lines: README.md
+22-23Lines changed: 22 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,7 @@
7
7
This Ansible Collection executes various SAP Software installations and configuration tasks for various SAP solutions and deployment scenarios on supported Linux operating systems.
8
8
9
9
Included roles cover range of tasks:
10
+
10
11
- Preparation of Operating system and SAP installation media before installation
11
12
- Installation of SAP Database, either SAP HANA or Oracle Database
12
13
- Installation of SAP Products, like SAP S4HANA, SAP BW4HANA, SAP Netweaver, SAP Solution Manager and others.
@@ -15,28 +16,20 @@ Included roles cover range of tasks:
15
16
16
17
## Requirements
17
18
18
-
### Control Nodes
19
-
Operating system:
20
-
- Any operating system with required Python and Ansible versions.
21
-
22
-
Python: 3.11 or higher
23
-
24
-
Ansible: 9.9.x
25
-
26
-
Ansible-core: 2.16.x
27
-
28
-
**NOTE: Ansible 10 and ansible-core 2.17.x are not supported, because of breaking changes requiring higher Python version on managed nodes.**
29
-
30
-
### Managed Nodes
31
-
Operating system:
32
-
- SUSE Linux Enterprise Server for SAP applications 15 SP5+ (SLE4SAP)
33
-
- Red Hat Enterprise Linux for SAP Solutions 8.x 9.x (RHEL4SAP)
19
+
| Component | Control Node | Managed Node |
20
+
| --- | --- | --- |
21
+
| Operating System | Any OS | Red Hat Enterprise Linux for SAP Solutions 8.x, 9.x and 10.x<br>SUSE Linux Enterprise Server for SAP applications 15 SP5, 15 SP6, 15 SP7 and 16.0 |
22
+
| Python | 3.11 or higher | 3.9 or higher |
23
+
| Ansible-Core | 2.18 or higher | N/A |
24
+
| Ansible | 12 or higher | N/A |
34
25
35
-
**NOTE: Operating system needs to have access to required package repositories either directly or via subscription registration.**
26
+
> **Managed Node Registration**<br>
27
+
> Operating system needs to have access to required package repositories either directly or via subscription registration.
36
28
29
+
**Additional notes:**
37
30
38
-
Python: 3.6 or higher
39
-
31
+
-**Version Compatibility:** For a detailed mapping of supported Python versions and Ansible-Core lifecycles, refer to the official [Ansible-Core Support Matrix](https://docs.ansible.com/projects/ansible/latest/reference_appendices/release_and_maintenance.html#ansible-core-support-matrix).
32
+
-**Control Node Permissions:** Ensure the user executing the playbooks has the necessary SSH keys and sudo privileges configured for the target environment.
40
33
41
34
## Installation Instructions
42
35
@@ -73,6 +66,7 @@ See [Installing collections](https://docs.ansible.com/ansible/latest/collections
73
66
## Use Cases
74
67
75
68
### Example Scenarios
69
+
76
70
- Preparation of Operating system for SAP installation
77
71
- Preparation of SAP installation media for SAP installation
78
72
- Installation of SAP HANA (including High Availability with replication) or Oracle Database
@@ -85,7 +79,7 @@ More deployment scenarios are available in [ansible.playbooks_for_sap](https://g
85
79
All included roles can be executed independently or as part of [ansible.playbooks_for_sap](https://github.com/sap-linuxlab/ansible.playbooks_for_sap) playbooks.
86
80
87
81
| Name | Summary |
88
-
|:--- |:--- |
82
+
| --- | --- |
89
83
|[sap_anydb_install_oracle](https://github.com/sap-linuxlab/community.sap_install/tree/main/roles/sap_anydb_install_oracle)| Install Oracle DB 19.x for SAP |
90
84
|[sap_general_preconfigure](https://github.com/sap-linuxlab/community.sap_install/tree/main/roles/sap_general_preconfigure)| Configure general OS settings for SAP software |
91
85
|[sap_ha_install_hana_hsr](https://github.com/sap-linuxlab/community.sap_install/tree/main/roles/sap_ha_install_hana_hsr)| Configure and enable SAP HANA System Replication |
@@ -104,20 +98,25 @@ All included roles can be executed independently or as part of [ansible.playbook
104
98
This Ansible Collection was tested across different Operating Systems, SAP products and scenarios. You can find examples of some of them below.
105
99
106
100
Operating systems:
107
-
- SUSE Linux Enterprise Server for SAP applications 15 SP5+ (SLE4SAP)
108
-
- Red Hat Enterprise Linux for SAP Solutions 8.x 9.x (RHEL4SAP)
101
+
102
+
- Red Hat Enterprise Linux for SAP Solutions 8.x, 9.x and 10.x
103
+
- SUSE Linux Enterprise Server for SAP applications 15 SP5, 15 SP6, 15 SP7 and 16.0
109
104
110
105
Deployment scenarios:
106
+
111
107
- All scenarios included in [ansible.playbooks_for_sap](https://github.com/sap-linuxlab/ansible.playbooks_for_sap) repository
112
108
113
109
SAP Products:
110
+
114
111
- SAP S/4HANA AnyPremise (1809, 1909, 2020, 2021, 2022, 2023) with setup as Standard, Distributed, High Availability and optional Maintenance Planner or Restore System Copy
115
112
- SAP Business Suite (ECC) on HANA and SAP Business Suite (ECC) with SAP AnyDB - SAP ASE, SAP MaxDB, IBM Db2, Oracle DB
116
113
- SAP BW/4HANA (2021, 2023) with setup as Standard or Scale-Out
117
114
- SAP HANA 2.0 (SPS04+) with setup as Scale-Up, Scale-Out, High Availability
118
115
- Other SAP installation activities; such as System Rename, System Copy Export, SAP Solution Manager and SAP Web Dispatcher
119
116
120
-
**NOTE: It is not possible to test every Operating System and SAP Product combination with every release. Testing is regularly done for common scenarios: SAP HANA, SAP HANA HA, SAP S4HANA Distributed HA**
117
+
> **Testing Disclaimer**<br>
118
+
> It is not possible to test every Operating System and SAP Product combination with every release.<br>
119
+
> Testing is regularly done for common scenarios: SAP HANA, SAP HANA HA, SAP S4HANA Distributed HA**
- collection - Update readme formatting to align with galaxy format (https://github.com/sap-linuxlab/community.sap_install/pull/1148)
400
+
- sap*preconfigure - Sync with SAP notes for RHEL 10 (https://github.com/sap-linuxlab/community.sap_install/pull/1161)
401
+
- sap_general_preconfigure - Prevent an accidental change to a lower SELinux mode (https://github.com/sap-linuxlab/community.sap_install/pull/1154)
402
+
- sap_ha_pacemaker_cluster - Add fence_aws for SLES 16 and remove Tech Debt (https://github.com/sap-linuxlab/community.sap_install/pull/1151)
403
+
- sap_hana_install - Revert wrong conditional from PR#1138 (https://github.com/sap-linuxlab/community.sap_install/pull/1147)
404
+
- sap_swpm - Sanitize conditions for 2.19 (https://github.com/sap-linuxlab/community.sap_install/pull/1159)
Ansible-vault will ask to enter a vault password, which is required to decrypt the value during ansible runtime afterwards.
32
+
Ansible-vault will ask to enter a vault password, which is required to decrypt the value during ansible runtime afterwards.<br>
33
33
Consider this the "master key" for your vault-encrypted credentials.
34
34
35
35
```text
@@ -45,7 +45,7 @@ my_secret_var: !vault |
45
45
Encryption successful
46
46
```
47
47
48
-
Save the `my_secret_var` and encrypted multi-line value in your variable definitions and include the definition file as usual.
48
+
Save the `my_secret_var` and encrypted multi-line value in your variable definitions and include the definition file as usual.<br>
49
49
The variable can as well be referenced and used by other variables for more flexibility.
50
50
51
51
```yaml
@@ -62,7 +62,7 @@ rm passfile
62
62
63
63
## Run playbook which uses vault-encrypted content
64
64
65
-
As soon as a vault-encrypted value is present in your playbook, ansible will require the vault password to be entered for playbook execution.
65
+
As soon as a vault-encrypted value is present in your playbook, ansible will require the vault password to be entered for playbook execution.<br>
66
66
Add `--ask-vault` to your `ansible-playbook` command to prompt for this "master key" password and allow secure decryption.
67
67
68
68
```bash
@@ -75,7 +75,7 @@ _When encrypting multiple values that will be used together, you have to make su
75
75
76
76
You can also encrypt an entire file, e.g. containing multiple secrets.
77
77
78
-
However, if variables are defined in the file it will encrypt the variable names as well and makes it harder to identify the source definition of a referenced variable.
78
+
However, if variables are defined in the file it will encrypt the variable names as well and makes it harder to identify the source definition of a referenced variable.<br>
79
79
Also, encrypting the entire file will require ansible-vault commands to view or edit the contents of the file. A file containing individually encrypted values can be viewed and edited as any other file without uncovering the actual secret value.
80
80
81
81
`ansible-vault` will prompt for the vault password - either to be created for a new encrypted file, or to be used for decrypting existing content (for view or edit operations).
0 commit comments